Repository navigation
docs: wave-5 receipts — S02 batch executed (A only), decisions recorded, upstream reports filed - #57
Merged
Merged
Conversation
…ed, upstream reports filed - evals/product-journeys/BATCH_2026-10-04.md: first executed batch summary (canary + 33 runs, 24/33 first-attempt, $1.81 priced / $0 real via the coding-plan key; B not run) plus the full run records. - Programme: S02 marked executed (A only); owner decisions recorded for S28 (n>=20 confirmed), S25 (service account stays id-only), S10 (79 compact targets kept). S08 PR-body/webhook surfacing approved, unbuilded. - AUDIT_OPEN: wave-5 section (production dd5b13e -> 80c9187 with verified pre-deploy backup, five waiting runs intact; shadow flags live); upstream reports marked filed (neutron#6, teploy-cli#18/#19/#20). - NEXT_SESSION.md rewritten for the next session.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Live-session receipts (2026-10-04), docs + results only — no production code changed.
S02 executed: owner approved A-only; gateway ZAI_API_KEY rotated to a coding-plan key ($0 real spend). Canary eval-20261003-2 (pass) + 33 batch runs across eval-20261003-3/-4, eval-20261004-1/-2/-3/-4: 24/33 first-attempt passes, $1.81 priced total. pj-c-same-pr ran in its own run ids after a missing same-pr repo mapping was honestly recorded as 3 NOT-RUN refusals. Summary + honest reads in evals/product-journeys/BATCH_2026-10-04.md (incl. the pj-s-question canary-pass / 0/3-batch variance signal).
Decisions recorded: S28 n>=20 confirmed; S25 service-account stays id-only; S10 79 compact targets kept; S08 PR-body/webhook surfacing approved (work item, not built here).
Filed upstream: neutron#6 (framework plain-text 404), teploy-cli#18/#19/#20 (dry-run; deploy generation + CAS; logs flags + no-deployment-vs-unreachable).
Production state (receipt in AUDIT_OPEN wave-5 section): dd5b13e -> 80c9187 after coordinated stop + verified backup; five waiting runs intact; six shadow flags live.
Claims ledger 12/12; manifest validation green.