godmode-continuitylisted

# Godmode Continuity ## Outcome Produce a bounded context brief whose claims can be traced to current inspection or a validated local record, then preserve the next recovery point outside the working tree. ## Reconstruct current reality 1. Resolve project, Git-common-directory, worktree, branch, HEAD, and hashed-remote identity before trusting prior state. 2. Run `context status`; add `--scan` when filesystem drift matters. 3. Run `inventory diff` to distinguish added, changed, and removed paths from the last baseline. Do not infer file content from hashes. 4. Run `resume` after a valid baseline or `resume --refresh` when evidence is stale. 5. Classify each brief item as observed fact, declared intent, assumption, conflict, invariant, decision, incident, open check, or obligation. Treat identity drift, contradictory invariants, phantom file references, undocumented changes, unproven completion, and capacity overflow as findings—not as facts to hide. ## Preserve continuity Use the narrow record type: - `remember --kind decision|invariant|lesson|obligation` for durable knowledge. - `checklist update` for cumulative checks. - `checkpoint` for a recoverable state, next actions, active hypothesis, and evidence; `--owes "<restore>"` for a temporary change left behind (a role bump, a throwaway spec) that the scope gate names until it is closed. - `branches --record`, `version`, `db`, `sprint`, or `docs` for domain state. Record relative paths, statuses, hashes,