[self-repair:69aab9ad2b73] [orchestrator-defect] Review CLI flags explicitly scoped slice files as forbidden

[srnichols]

Class

orchestrator-defect

Symptom

forge_diff on the hardened RMG-0328 parent reports apps/api/src/modules/items/tests/price-audit-coverage.guard.test.ts as FORBIDDEN, although that exact path is declared in Slice 1 Scope and the contract requires strengthening it. RMG-0168 similarly reports schema.prisma and its three invitation-preference TypeScript files as forbidden although Slice 1 explicitly lists them. forge_analyze consequently assigns 0/25 coverage and 75/100 total for the price plan. The cause inside the parser has not been diagnosed. Direct git comparison against the frozen source base and checked execution allowlists confirms exactly the approved three and five source files, excluding the separately recorded runtime-only .forge.json delta.

Workaround Applied

Treat these heuristic scores as inconclusive. Independently compare all committed, staged, unstaged and untracked source changes against the exact first-slice scope, verify the runtime-only configuration remains excluded from publication, and compare host SHA-256 values with tested private-volume files. Preserve the tool's reported failures rather than claiming it passed. No upstream source edits were made during this review.

Files

• pforge.ps1

[srnichols]

Fixed in f2b7021e. In both shells, pforge diff / forge_diff and pforge analyze now end the Forbidden Actions and In Scope sections at the next heading, so later slice scopes are no longer reported as FORBIDDEN.

Available on planning/main now. It reaches projects with the next release, through pforge self-update or pforge update.

[srnichols]

Released in v3.27.0. Projects pick it up with pforge self-update (see the release's upgrade notes for Git Bash).