Distillation

Date: Sep 16, 2026

• 🔴 (22:32) User stated the server restarted and directed resumption of the existing immutable-projection exhaustive-validation session with completed work preserved.
• 🔴 (22:32) User requested completion using an exact aggregate or deterministic shards, with substantive PASS/FAIL results covering identity, hash, and isolation.
• 🔴 (22:32) User directed use of local lore recall/UI if context is missing.
• 🔴 (22:32) User requires validation outcomes to be substantive and “never warning-only.”
• 🔴 (22:32) User prohibited edits, VCS operations, server operations, and production-database operations for this task.
• 🔴 (22:37) User stated that Jujutsu (jj) operations “never fails on conflict”; conflicts are recorded in the resulting commit and must be identified with jj st and resolved later.
• 🟡 (22:37) Jujutsu guidance supplied: when .jj/ exists, use jj rather than git for mutations; never use interactive flags; always pass -m "msg" for descriptions/commits; verify mutations with jj st and jj log; prefer stable change IDs over commit IDs; never rebase or describe immutable commits; use jj undo, jj op log, or jj op restore <op-id> for recovery.
• 🟡 (22:37) Jujutsu guidance supplied: the working copy is commit @; edits automatically amend @; @- is its parent and @-- its grandparent; bookmarks do not automatically advance; operation history replaces reflog.
• 🟡 (22:37) Jujutsu conflict workflow supplied: after rebase, new, or squash, run jj st; inspect and manually resolve conflict markers, including %%%%%%% diff from:, +++++++, and >>>>>>>; do not use interactive jj resolve; jj st shows when conflicts clear.
• 🟡 (22:37) Jujutsu commit styles supplied: Style A uses jj commit -m "feat: ..." and leaves committed content in @- with a new empty @; Style B, recommended for refinement, uses jj describe -m "feat: ..." before editing and leaves @ as-is without running jj new at the end.
• 🟡 (22:37) Jujutsu review-update alternatives supplied: rewrite history with jj edit <change-id>, apply the fix, jj new, and jj git push; or preserve review history additively with jj new <bookmark>, apply the fix, jj commit -m "address review", jj bookmark set <bookmark> -r @-, and jj git push -b <bookmark>.
• 🟡 (22:37) Jujutsu revset distinction supplied: x..y means set difference, while x::y means a DAG path; they are not interchangeable.