Repository navigation
test(roster): RT-16 Reconcile durable runs, retries, journals and published history #430
Description
RT-16: Reconcile durable runs, retries, journals and published history
Campaign: eve-post-development-20261011
DEFERRED - do not execute. Development must be reviewed/integrated before the final candidate is frozen and Ray authorizes the round.
| Field | Declaration |
|---|---|
| Work item | Acceptance scenario RT-16; not a runnable implementation issue |
| Board | Roster Test; Backlog |
| Priority / mode | P0 / Offline |
| Candidate SHA / manifest | Pending post-development freeze; old fingerprints do not identify this round |
| Attempts / result / evidence | 0 / Not run / Not run for this campaign |
| Owner / estimate | Operator approval required; not staffed; estimate pending corpus and environment |
Matrix: #414
Project: https://github.com/users/R4yHarris/projects/3
Spec: FEATURE_SPEC section 5.6: Feedback and learning; honor sections 3 and 7.
Baseline: pending final reviewed/integrated candidate SHA and frozen configuration; never reuse an old uncommitted fingerprint.
Mode: Offline | Priority: P0 | Initial result: Not run | Evidence stage: Not run
Outcome
Demonstrate the named operational behavior with attributable evidence, or record a failure, blocker or unresolved spec decision without claiming success.
Prerequisites
- No scenario prerequisites; execution still requires the safety approvals below.
Operator procedure
- Freeze revision/time bounds and inventory repository-relevant legacy history, machine history, seat JSONL, operational logs, archived reports and Git AI-Run records.
- Build an evidence-only reconciliation by run ID, durable seat occurrence and published SHA/session; identify ambiguous legacy labels without assigning fabricated invocations.
- Test started/completed/failure/cancellation, planning-only pause and unverified stub, repeated snapshots and merge-commit attribution duplicates.
Acceptance checks
- Report task count, invocation count, seat occurrences and merged deliveries separately; absent terminal evidence stays unknown.
- Explicit history-store selection prevents the default legacy reader from silently hiding machine records; identity transitions are explained, never reassigned without evidence.
- Repeated snapshots and duplicated merge trailers do not inflate unique delivery counts; retry occurrences preserve distinct outcomes.
- Response-backed model/tokens override inherited declarations; missing usage stays unknown and observed zero stays zero.
- Retain verification/review evidence and starting commit anchors when present; do not backfill absent historical measurements.
Evidence and result
Use the matrix observation template. Append one redacted observation per actual attempt/case. Do not replace failed attempts with a later pass. Include run/seat IDs, exact interface, actual verification/review and human rating only when observed. Fixture results must be labeled fixture, not live operational evidence.
Fresh campaign starts at Not run. Previous comments, observations and evaluations are retained as historical evidence; they are not new-round results. Only observations tied to this candidate and campaign count. All required cases need new evidence and human review before Result becomes Pass. Unavailable prerequisites are recorded as fresh Blocked observations, not inherited old outcomes.
Safety and non-goals
This is TEST work, not a build task. No product/source/policy/workflow/vendor edits are requested; do not execute this issue as an implementation slice. Use disposable approved fixtures and separately approved bounded model tasks. No actual credentials, prompt/source bodies or transcripts may be posted.
No model calls, spend, publication, process termination or destructive cleanup are authorized by issue creation. Obtain explicit operator approval before those operations. Keep this issue only in Roster Test. Cross-link a separate Roster Build issue for any discovered defect; keep test failure evidence here and rerun after the fix.
Workflow and release gate
Backlog -> Ready only after dependencies, candidate freeze, disposable scope and budgets are approved. In progress means actual authorized execution; In review means evidence is awaiting independent/human review. Done/Pass requires all original required cases and genuine human acceptance, not a subset of green fixtures. A defect creates a separately scoped Roster Build issue; retain its failing observation here.
Plain-text Ask example
Explain how to inspect an interrupted Roster run and reconcile its journal with actual execution and publication evidence without inventing a successful completion. Output it in a new "recovery-guide" directory
Use: Illustrative entry point only. This scenario remains deferred; the original operator procedure and acceptance cases are still required.
A prompt alone does not verify this scenario. Operator-controlled fixtures, actual evidence and genuine human review remain mandatory. Never execute a TEST issue as a product implementation issue.
Activity
r4yharris-agent-coder commentedon Oct 10, 2026
Fresh RT-16 observation
Fresh campaign eve-matrix-9f80afa-20261010; candidate 9f80afa, contracts 61b97b3e93e670a675c0301cce5412c73404d179. Windows, Node v20.20.2. Original matrix protocol #414; previous 28044dd observations are not carried forward.
Full existing suite: ROSTER_TEST_JOBS=2; npm exec --yes --package=node@20 -- node scripts\run-tests.mjs. Exit 0; 171 files, 1593 tests, 1586 passed, 0 failed, 7 skipped; 784.0s wall. Nine 60-second file-budget warnings retained. This is fresh fixture/regression evidence, NOT whole-scenario operational acceptance, idle benchmark or human AI-Eval. Missing platforms, actual TTY, multi-model corpus and publication variants are not replaced with fixtures.
Evidence stage denotes the highest evidenced subcase only; it does not certify every required gate. Human evaluation/reviewer: absent. No TEST issue was sent wholesale to roster run; no policy/workflow/vendor edits, saved-default changes, deployments or disposable-product publication. Board: https://github.com/users/R4yHarris/projects/3
Spec: FEATURE_SPEC 5.6, honoring sections 3 and 7.
Whole-scenario disposition: Blocked.
History/provenance/metrics fixtures and fresh delivery stats pass; full time-bounded cross-store/Git reconciliation and actual merge dedup not demonstrated.
Fresh known lock failure is cross-linked to existing Build defect #441; Node20 code-planning failure is cross-linked to #454. Corrected live observations: one docs delivery/reviewer pass after automatic continuation, one code failure before coder; 1/2 reviewed yield, 0/2 first-pass yield, no human acceptance. Initial four experiment runtime/input mistakes and unavailable usage/exception evidence are retained, not relabeled as successful deliveries. See the new campaign summary on #414 for exact live outcomes and the complete 24-row disposition.
[-]TEST RT-16: Reconcile durable runs, retries, journals and published history[/-][+]test(roster): RT-16 Reconcile durable runs, retries, journals and published history[/+]r4yharris-agent-coder commentedon Oct 13, 2026
Authorized offline history/provenance subset
Candidate a9af3e6 / contracts0050ada.
Windows Node20.20.2; prior scoped offline-batch authorization.
Exact command:
node --test --test-reporter=tap tests\history-query.test.mjs tests\history-robustness.test.mjs tests\local-runs.provenance.test.mjs tests\builtin.provenance.test.mjs
40 tests PASS, zero failures/skips/cancellations, 114055.2167ms, exit0.
Four files, 38 top-level tests plus nested tests. Log retained as
authorized-history-reconciliation-subset-20261013.log. No live inference,
credential handoff, consumer publication or historical data deletion.
Scripted transport drives builtin seat fixtures; Git operations are confined
to disposable fixture repositories, not human publication.
Fixture evidence includes actual local checkout deletion/reclone and linked
worktree cleanup with unchanged machine record bytes, origin identity
separation, explicit history-store selection/read-only queries, malformed
record visibility, response-backed served model/observed zero tokens and
unknown stub usage rather than inherited metrics. No claim that these four
files establish every repeated-snapshot/merge-trailer deduplication case.
RT-16 still needs frozen time bounds, actual repository-relevant legacy/journal/
published inventory and evidence-only distinct task/invocation/seat/delivery
reconciliation plus genuine acceptance. No full operator scenario Pass/Done,
campaign freeze or AI-Eval. Related RT-23 reclone control is fixture evidence
only; migration/rollback and human memory promotion remain outstanding.
Spec5.6/5.8 respects3/7; no product/policy/workflow/dependency changes.
r4yharris-agent-coder commentedon Oct 13, 2026
Actual read-only history inventory, separate from fixtures
Candidate/ref a9af3e6, contracts0050ada,
Windows Node20.20.2. Time bounds 2026-10-11T00:00:00Z through
2026-10-13T22:17:22.891Z for durable stores; Git attribution end
2026-10-13T22:19:07.709Z (commit time, NOT model execution time).
Explicit current origin-derived repository identity only; historical identities
are not guessed/reassigned. Read-only existing reader/exporter/learning helpers;
no recover/append/repair/lock takeover, model call or history cleanup.
Machine session events: planner8/coder4/reviewer2/unknown2.
Served-model counts: glm-5.3-flash7, Qwen/Qwen3.8-27B-FP8 7, unknown2;
requested qwen3.8-27b13/unknown3. Two prompt and two completion usage fields
absent/unknown; zero observed-zero fields. No aggregate bill constructed.
Committed log-file bytes unchanged across each read; zero store-wide skipped
records. This is reader stability evidence, NOT freezing future active writers.
Local journal schema evidence: excellence3/delivery10/recorded delivery review
verdict1/bounded attempt0/local evaluation rows0. Inventory v2 corrects v1's
wrong top-level verification/review-field query; v1 was not published as evidence.
No absent measurements backfilled. Journal timestamps not assumed.
Persisted redacted JSON reports: roster-history-inventory-20261013.json and
roster-journal-inventory-20261013-v2.json in session files. No raw prompts,
source bodies, auth, journals or commit messages exposed here.
Remaining RT-16: retained consumer/worktree seat JSONL, archived operational
logs and independently verified published-PR subjects, identity transitions,
actual task/invocation/seat/delivery crosswalk and genuine human acceptance.
This bounded actual inventory is NOT the full deferred operator round,
scenario Pass/Done, pilot acceptance or difficulty promotion. Spec5.6/5.8
respects3/7. App resume still independently blockedHTTP422/Adminnull; no bypass.
r4yharris-agent-coder commentedon Oct 14, 2026
Board reconciliation 2026-10-14: Status In progress, Evidence stage Attempted; full RT-16 Result remains Not run.
Previously posted actual redacted machine/legacy history and corrected local-journal inventory remain evidence. Authorized Node20 history selector at a9af3e6: history-query, history-robustness, local-runs.provenance, builtin.provenance; 40/40 pass, zero skips, 114055.2167ms.
135 AI-Run Git rows are not 135 deliveries: 64 merge rows repeat paired nonmerge attribution. No invented invocation counts, summed billing or human evaluations. This is a subset/inventory, not completed full operator reconciliation.