Skip to content

test: phase 2 wave 3 — registry-derived expectations (F-21) + built-in-scoped parity (F-06) - #148

Merged
pacphi merged 1 commit into
developfrom
feat/phase-2-wave-3-test-derivations
Aug 15, 2026
Merged

test: phase 2 wave 3 — registry-derived expectations (F-21) + built-in-scoped parity (F-06)#148
pacphi merged 1 commit into
developfrom
feat/phase-2-wave-3-test-derivations

Conversation

@pacphi

Copy link
Copy Markdown
Owner

Nine test files stop hand-typing host sets and default maps: expectations derive from the registry's own capability queries, scoped to built-ins where that is the assertion's meaning. Deliberate literals that remain are policy pins or fixture inputs, commented as such. The component-directory parity invariant is now stated built-in-scoped, exempting future externally-admitted adapters until the wave-4 contract graduates them. Zero production changes; per-file test counts identical (154/154).

🤖 Generated with Claude Code

…t-in-scoped
Phase 2 Wave 3 (F-21, F-06): host-set and default-map pins across nine test
files now derive from managedHostIds()/routableHostIds()/primaryHostIds()/
defaultHostMap() — scoped to built-ins where the assertion is about built-ins
— so registering a host updates expectations exactly once. Deliberate
literals that survive are policy pins (DEFAULT_PRIMARY_HOST) or fixture
inputs, each commented. The component-directory parity invariant is stated
built-in-scoped; externally-admitted adapters are exempt until the wave-4
contract graduates them. No production code changed; suite counts identical.
@pacphi
pacphi merged commit 8374b8e into developAug 15, 2026
11 checks passed
@pacphi
pacphi deleted the feat/phase-2-wave-3-test-derivations branch August 15, 2026 22:31
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@pacphi