Files
stack/docs/plans/reviews/2026-09-07_foundation-inspector-integration-test-boundary.md
jason.woltje 8ebddd6f93 feat(foundation): offline synthetic scope/permission inspector (FI-FILBERT-8 APPROVED r6)
Rocko-authored, Filbert-reviewed inspector (r6 manifest
a4a44930...) with full review/build/verdict evidence under
docs/plans/reviews. 43/0 selftests, oracle zero-disagreement,
foundation checker PASS. Owner A9 acceptance recorded separately.
2026-09-07 14:06:35 -05:00

42 lines
2.6 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Inspector integration verification boundary — measured planning gate
Coordinator: darkwing. Date: 2026-09-07.
Status: source inspection, not test execution or a waiver of required coverage.
## Measured boundaries
- scripts/test-task.sh:408458 contains real marker and session/fork launches via
run-task.sh when docker info succeeds. Missing Docker skips these cases; that is
incomplete coverage, not a full green integration gate.
- scripts/test-release.sh:1015 backs up/restores RELEASE; :4752 deliberately
changes/removes it. Run only in a disposable repository copy, never the frozen
shared source. :5899 exercises activation/rollback against synthetic data when
Docker is available. Activation is health-gated; do not assume this is a purely
static test or harmless just because the release pointer is synthetic.
- scripts/test-conductor.sh:4051 clones into its temporary sandbox; later commands
stage/commit/reset there. Those fixture mutations are different from staging the
shared index, but require an explicitly permitted disposable Git test context.
An archive without Git history alone is insufficient for this suite.
## Required verification plan before full approval
1. Verify the corrected candidate and reviewed contract hashes before execution.
2. Prepare a disposable repository/test context with the necessary baseline history
and exact candidate bytes. No shared checkout, RELEASE mutation or index use.
3. Select a verification mode explicitly: complete suites with separately authorized
Docker/provider/session effects and runtime-only auth, or accurately limited
non-live coverage. Do not label skips, substitutes or stubs as the full suites.
4. If complete live-provider testing is authorized, constrain it to synthetic tasks,
temporary data/config/session roots, bounded requests and existing pinned images.
No production pointer, actual work/session adoption, credential-content reading,
provider-account mutation, image installation or separate fleet intervention.
Obtain the necessary explicit permission before executing these branches.
5. Record executed/skipped/failed cases and independent versus writer receipts.
The code reviewer must see the scope and exact candidate tested.
No new authorization is issued by this document. Current code fixes can proceed
independently under FI-ROCKO-6. At the 2026-09-07 14:28 UTC check, the declared r4
build report had not returned. Do not poll private panes or retry the delivered task.
Owner/test-scope direction and Rocko's exact corrected candidate are the concrete
conditions needed to finish the corresponding remaining gates.