chore: record itd-39's scope conditions as none stated

.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md

@@ -61,6 +61,10 @@ The failure mode itd-3 guards against is *unbounded scaffolding outside the repo
 - **Given** a recall keyword that matches a page in both the workspace and user scope, **when** the hook resolves the match, **then** the workspace-scope page is injected and the user-scope page is suppressed (narrower scope wins).
 - **Given** any prompt, **when** the hook runs, **then** `~/.claude/.../memory/` is never read or written by the retrieval path.
 
+## Scope Conditions
+
+None stated.
+
 ## Open Questions
 
 _None open; the three questions first left here are settled under Decisions (2026-10-11), and the technical questions the plan leaves open are in the bundle's spec._

.abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md

@@ -0,0 +1,15 @@
+---
+schema_version: 1
+id: "iss-2610311501473953"
+slug: "abcd-intent-ready-itd-39-reported-the"
+severity: "minor"
+category: "bug"
+source: "agent-observation"
+found_during: "starting the product thinker's selected builds"
+origin: researcher-authored
+production_mode: hand-written
+found_at: "internal/core/intent/ready.go"
+remedy: "Have intent ready append every record-only start check the build runs (claim_sections, hold, blocked, steps where gating) as gating rows, read from intent.StartChecksIn, so READY means the build's record checks pass."
+---
+
+abcd intent ready itd-39 reported the intent READY on 2026-10-31, listing scope_conditions as an advisory row ('no ## Scope Conditions section — the context claim is unrecorded'), and abcd build itd-39 then refused it at claim_sections for the same missing section. ReadyWithQuestions (internal/core/intent/ready.go) appends only the open-questions start check to the readiness verdict, so READY still does not mean the build will start, the defect iss-2610101610446956 fixed for open questions alone.

.abcd/work/issues/open/iss-2610311514162877-on-2026-10-31-abcd-build.md

@@ -0,0 +1,15 @@
+---
+schema_version: 1
+id: "iss-2610311514162877"
+slug: "on-2026-10-31-abcd-build"
+severity: "minor"
+category: "process"
+source: "agent-observation"
+found_during: "starting the product thinker's selected builds"
+origin: researcher-authored
+production_mode: hand-written
+found_at: "internal/core/peers/read.go"
+remedy: "Teach the safe backup in the SHELL hazard registry (before git rebase, keep the old tip as a tag or under refs/abcd/backup/, never as a local branch), and have the peers refusal say when the holding branch has no upstream and no worktree, naming it as a probable safety copy and the tag move as the way past."
+---
+
+On 2026-10-31 abcd build itd-2610170638184486 was refused at the peers check by backup/sota-open-intents-pre-rebase, a local branch an agent made as a safety copy before rebasing research/sota-open-intents onto main; it held the intent's old drafts/ copy, while main and the rebased branch held it in planned/. The peers check reads every local branch under refs/heads/ (internal/core/peers/read.go) and cannot tell a safety copy from live work, and the guard then refused the branch's deletion (git-delete-unproven) because a rebase that squashed and resolved conflicts leaves no ancestry or patch-equivalence for it to prove, so the build stayed blocked until the person allowed the delete by hand. abcd teaches no safe form of the backup: a tag, or a ref outside refs/heads/, would have kept the copy and blocked nothing.