Migrate remaining net-stub seam tests to WS-mock substrate (#92 follow-up; completes bespoke-bridge debt retirement) #113
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/cellblock#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Background
Filed 2026-06-22 as follow-up to cellblock#92 (WS-mock harness substrate). Shipwright's #92 pre-thought (58a3) ratified migration-scope (A) ADDITIVE: build WS-mock substrate + land must-have versus coverage + demonstrate pattern via #91 AC7 prod-path row, but LEAVE existing net-stub seam tests (from #87/#91/#94) in place during the foundation PR. This tracker captures the remaining-migration work.
Scope
Migrate existing harness tests built on bespoke net-stub seams onto the new WS-mock substrate (post #92). Specifically:
For each: replace seam-injection with WS-mock scripting that drives the same prod-handler-paths via real flow. Retire the bespoke seams from prod code once their tests are migrated.
Substrate-discipline rationale
#92's purpose is to retire bespoke-bridge debt (n=3 worked instances: #80 HANG-route + #89 error-resolution + #94 net-stub). Foundation PR establishes the substrate + demonstrates pattern via AC7 row. This follow-up COMPLETES the retirement by migrating the remaining tests + removing the seams from prod code.
Splitting foundation + migration into separate PRs (per Shipwright's lean ratified at 4b15):
Lane + size
Shipwright lane (harness substrate work). Size unclear pending #92 implementation; depends on how many bespoke seam-tests exist + how mechanical the migration is. Likely size/M.
Acceptance criteria (refine after #92 lands)
Cross-refs
Anchor
2026-06-22 #92 pre-thought (Shipwright 58a3) + Bosun ratify of migration-scope (A) ADDITIVE. Follow-up tracker established so the retirement-completion work sits in queue cleanly rather than getting lost.