Remove the non-authoritative plan.md phase checkbox
Make `plan.md` phase status honest by deleting the hand-maintained `- [ ]`/`- [x]`
checkbox entirely. Phase completion is currently tracked twice: once mechanically
(build/verify artifacts + seals — the only source `ana work status` and `countPhases`
actually read) and once as an agent-hand-edited markdown checkbox that **no code reads**.
The redundant copy has a cross-tree commit path that mis-fires, producing split-brain
state and a dirty working tree that can block `ana work complete --merge`.
A010's tagged test runs on the artifact branch, where the removed verify-report→plan.md staging block was a guarded no-op (!artifactPaths.includes). The test passes identically with or without the fix — it does not discriminate the change it claims to cover.
obs→ closed
Contract A010's literal target (isFileCommitted plan.md === false after save-all) only holds on a feature branch, where plan.md is filtered from primaries. On the artifact branch save-all legitimately commits plan.md as a primary artifact, so the assertion as written contradicts normal save-all behavior. The assertion should pin a branch context or assert 'no verify-report-coupled staging.'
validatePlanFormat phase detection recognizes only '- ' bullets (line.startsWith('- ')). A '* ' bullet or tab-prefixed dash would be silently uncounted. This faithfully mirrors countPhases (intentional, commented), so behavior is consistent — but it records a frozen-format fragility shared by both copies for the next engineer.
obspackages/cli/src/commands/work.ts→ acknowledge
work.ts pull defense gates on porcelain status with !trimStart().startsWith('??'). A staged-deleted ('D ') or renamed ('R ') plan.md is also treated as 'modified' and restored from HEAD. Behavior is benign (restoring a non-authoritative file is desirable), but the comment frames the guard narrowly as 'tracked-modified'.