docs(sf): disambiguate ADR-011 in sf-db.ts schema comments too

Same fix as df095b406 / f1fc8cc86, applied to the schema-comment
references in sf-db.ts (column comments + migration comments). Future
maintainers reading SQL definitions like:

  is_sketch INTEGER NOT NULL DEFAULT 0, -- ADR-011: 1 = slice is a sketch

would otherwise look up SF's local ADR-011 ("Swarm Chat") and find
nothing about sketches. Now reads "gsd-2 ADR-011" so the source-of-
truth is unambiguous.

Comment-only diff. The 5 remaining "(gsd-2)" parenthetical references
already disambiguate clearly enough; left intact to avoid churn.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mikael Hugo 2026-05-02 23:09:34 +02:00
parent f1fc8cc86b
commit f5dabf1857

View file

@ -375,8 +375,8 @@ function initSchema(db: DbAdapter, fileBacked: boolean): void {
planning_meeting_json TEXT NOT NULL DEFAULT '',
sequence INTEGER DEFAULT 0, -- Ordering hint: tools may set this to control execution order
replan_triggered_at TEXT DEFAULT NULL,
is_sketch INTEGER NOT NULL DEFAULT 0, -- ADR-011: 1 = slice is a sketch awaiting refine-slice
sketch_scope TEXT NOT NULL DEFAULT '', -- ADR-011: 2-3 sentence scope hint from plan-milestone
is_sketch INTEGER NOT NULL DEFAULT 0, -- gsd-2 ADR-011: 1 = slice is a sketch awaiting refine-slice
sketch_scope TEXT NOT NULL DEFAULT '', -- gsd-2 ADR-011: 2-3 sentence scope hint from plan-milestone
PRIMARY KEY (milestone_id, id),
FOREIGN KEY (milestone_id) REFERENCES milestones(id)
)
@ -412,7 +412,7 @@ function initSchema(db: DbAdapter, fileBacked: boolean): void {
sequence INTEGER DEFAULT 0, -- Ordering hint: tools may set this to control execution order
escalation_pending INTEGER NOT NULL DEFAULT 0, -- ADR-011 P2 (gsd-2): pause-on-escalation flag
escalation_awaiting_review INTEGER NOT NULL DEFAULT 0, -- ADR-011 P2 (gsd-2): continueWithDefault=true marker (no pause)
escalation_override_applied INTEGER NOT NULL DEFAULT 0, -- ADR-011 P2: 1 once carry-forward injected into a downstream prompt
escalation_override_applied INTEGER NOT NULL DEFAULT 0, -- gsd-2 ADR-011 P2: 1 once carry-forward injected into a downstream prompt
escalation_artifact_path TEXT DEFAULT NULL, -- ADR-011 P2 (gsd-2): path to T##-ESCALATION.json
PRIMARY KEY (milestone_id, slice_id, id),
FOREIGN KEY (milestone_id, slice_id) REFERENCES slices(milestone_id, id)
@ -1452,7 +1452,7 @@ function migrateSchema(db: DbAdapter): void {
}
if (currentVersion < 22) {
// ADR-011: progressive planning. is_sketch=1 means the slice is a 2-3
// gsd-2 ADR-011: progressive planning. is_sketch=1 means the slice is a 2-3
// sentence sketch awaiting refine-slice expansion; refine fills in the
// real plan and clears the flag. sketch_scope holds the milestone
// planner's stored scope hint that refine treats as a hard boundary.
@ -1530,7 +1530,7 @@ function migrateSchema(db: DbAdapter): void {
}
if (currentVersion < 25) {
// ADR-011 P2 carry-forward: when an escalation is resolved, the user's
// gsd-2 ADR-011 P2 carry-forward: when an escalation is resolved, the user's
// choice should be visible to the next execute-task agent in the same
// slice. escalation_override_applied=0 marks "resolved but not yet
// injected into a downstream prompt"; the prompt builder calls
@ -2167,9 +2167,9 @@ export function insertSlice(s: {
demo?: string;
sequence?: number;
planning?: Partial<SlicePlanningRecord>;
/** ADR-011: 3-valued — true marks sketch, false marks non-sketch, undefined leaves the row's existing flag intact. */
/** gsd-2 ADR-011: 3-valued — true marks sketch, false marks non-sketch, undefined leaves the row's existing flag intact. */
isSketch?: boolean;
/** ADR-011: 23 sentence scope hint. Same 3-valued semantics as isSketch. */
/** gsd-2 ADR-011: 23 sentence scope hint. Same 3-valued semantics as isSketch. */
sketchScope?: string;
}): void {
if (!currentDb) throw new SFError(SF_STALE_STATE, "sf-db: No database open");