Distillation

Date: Sep 16, 2026

• 🔴 (14:19) User asserted resolveTrustedRemote must ALWAYS use the on-disk git remote value when one exists; a client-supplied x-lore-git-remote header can never override on-disk truth. In local mode without a disk remote, the client remote must be dropped entirely to prevent the stale-header “git-remote magnet” bug.
• 🔴 (14:19) User asserted full CI must always run unconditionally on every push and PR—never path-gated or filtered by changed files, and never gating unrelated PRs. Compatibility guards including bash 3.2 compatibility for the macOS install script, actionlint workflow correctness, and new guards such as a bashisms linter must be unconditional CI jobs.
• 🔴 (14:19) User asserted shared memoized arrays such as the syncedColumns PRAGMA cache must always be frozen. Rationale: a caller could otherwise corrupt all later results; freezing causes accidental mutation to throw TypeError in strict mode.
• 🔴 (14:19) User asserted migration serves as the tier lock so write access never precedes the guard, documented at supabase/README.md:70.
• 🔴 (14:19) User asserted preview/dry-run project resolution must remain read-only, non-mutating, and non-interactive even with --yes or --interactive; preview must never call ensureProject(), create rows, or reconcile lazy git remotes. Only apply mode may ensure a project.
• 🟡 (14:21) Test changes included these exact titles, in order: 1. "allows a terminal-discovered recall that preserves sparse visible output positions" was renamed to "allows a late recall that preserves sparse visible output positions"; 2. "fails closed when later visible output changes an emitted sparse position"; 3. "fails closed when a lower-index recall follows visible output"; 4. "allows deferred sparse output before a higher-index recall"; followed by a test.each([ parameterized-test declaration whose cases/title were not shown.
• 🟡 (14:22) normalizeCodexResponsesEvent is exported from packages/gateway/src/stream/openai-responses.ts:1750.