docs(sf): escalation.ts header lists carry-forward + memory persistence

The header listed "artifact I/O, detection, flag flips, resolution" but
not the carry-forward injection (claimOverrideForInjection /
formatOverrideBlock) or the memory persistence calls now embedded in
both writeEscalationArtifact (continueWithDefault path, b9bff3762
sibling) and resolveEscalation (00c13bc5a). These are load-bearing
behaviors a contributor should know up front.

Also folded the "SF's local ADR-011 is 'Swarm Chat'" disambiguation
note into the header (matches the convention the rest of the
disambiguation sweep set).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mikael Hugo 2026-05-03 00:22:54 +02:00
parent ec4dab450b
commit 22109cee6a

View file

@ -1,8 +1,15 @@
// SF Extension — ADR-011 Phase 2 Mid-Execution Escalation (gsd-2 ADR)
// SF Extension — gsd-2 ADR-011 Phase 2 Mid-Execution Escalation
//
// Owns: artifact I/O (read/build/write), detection, producer-side flag flips,
// and user-facing resolution. The reject-blocker choice from gsd-2 is
// deferred — needs a blocker_source column SF doesn't yet have.
// Owns: artifact I/O (read/build/write), detection, producer-side flag
// flips, user-facing resolution, carry-forward injection (claim/format),
// and memory persistence — every successful escalation flow (resolve,
// auto-accept, continueWithDefault) deposits a "[escalation:T##] ..."
// memory in the architecture category so the choice + rationale flows
// into downstream prompts via getRelevantMemoriesRanked.
//
// SF's local ADR-011 is "Swarm Chat and Debate Mode" — unrelated.
// The reject-blocker choice from gsd-2 is deferred — needs a
// blocker_source column SF doesn't yet have.
import { existsSync, mkdirSync, readFileSync } from "node:fs";
import { dirname, join } from "node:path";