feat(phase-7): scratch consumer end-to-end smoke — full pipeline verify via test repo #584
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#584
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?
Set up a scratch consumer repo that exercises the full release-toolkit pipeline end-to-end via the new Go-based
rtinvocations. The meaningful Phase 7 test per ADR-0009 §3.1 nuance ("end-to-end smoke, not TDD").Scope
Coverage-completeness fold candidate: #562 (rolling-mode end-to-end differential test) may compose here — if scratch consumer exercises rolling-mode path, #562's coverage residual gets absorbed. Framing-verify at #T3 dispatch time to decide.
AC
Related
Filed 2026-07-27 by Bosun as part of Phase 7 decomposition.
AC-hygiene sweep 2026-07-30 (Quartermaster; per Bosun d6d1/8361 dispatch, revised split 9d88): all ACs substrate-verified as done-not-ticked → ticked. Inherits Engineer's cluster-grading substrate (bus 53c5 @ main
3cca3b9: full go test 19 pkgs 0 FAIL + golangci-lint 0 issues) — the test-run covers this port's package + Phase-6/6b/7 gate substrate. Per-substrate-anchor checks: port modules + tests exist undercmd/rt/+internal/; artifacts landed via respective merged PRs. Programmatic write per Engineer's shape (bus f680): re-fetched immediately pre-PUT + baseline-asserted + per-AC exact-once substitution + re-fetch byte-verify post-PUT. Substrate: PR#596 @1a97eb4shipped Shape 1 (prepare-flow parity, 2 scenarios × 3-state mutation loop); cut-side end-to-end deferred to #595 (out of #584 scope by design).Closed via PR#596 merged @
1a97eb4(2026-07-29 12:59:29 CEST). Shape 1 (prepare-flow composition parity) shipped: decide→prep 2-stage wire tested over throwaway repo, 2 scenarios (feat→minor, fix→patch), 3-state mutation loop (MUT-1 wrong-derived-version reds; MUT-2 noop→exit3 CannotGrade catches vacuity hole). Cut-side end-to-end composition NOT hermetically byte-comparable (port-team no-cut-oracle absence corroborates) → deferred to #595-adjacent live-runner surface. ADR-0010 pointer #584→#595 folded into same PR. Surveyor deep-verified with fresh airtight-positive-control confirmation + 2 comment-only should-considers routed into #582 fold (natural same-area home, preserves stamped head). Refs-only closure, hand-closed same pattern as #583/#587/#580/#591/#562/#585. Protocol v2 empirical n=2: BACKSTOP ping fired 14s before Engineer CLEAR in-flight arrival (CLEAR sent 12:55:32, arrived ~12:56:32; ping at 12:56:46) — instance 1 of "CLEAR-in-flight when BACKSTOP fires" pattern per Engineer df85 warning. n=1 tuning data point; extend BACKSTOP if n≥2 observed.