Issues

[G3] Accounting fixes unlocked by shared evidence: Codex per-request turns (#504), subagent project rollups and harness split (#506), `sessions list` token column

group-3

sourcing-migration

#563

· willwashburn opened

on Sep 19, 2026

[G3] Cutover: relayhistory becomes the default and only source; delete the harness readers, walkers, cursors and fs watcher; ship as a major release

group-3

sourcing-migration

#562

· willwashburn opened

on Sep 19, 2026

[G2] Identity and fingerprint compatibility, cursor migration, and `state rebuild` from the relayhistory store

group-2

sourcing-migration

#561

· willwashburn opened

on Sep 19, 2026

[G3] Harness expansion through relayhistory: Cursor and Grok in burn (SourceKind, pricing, TOOL_ALIASES, overhead mapping, fidelity policy) and collector-backlog transfer

group-3

sourcing-migration

#560

· willwashburn opened

on Sep 19, 2026

[G2] Node SDK and MCP packaging with the relayhistory backend: single native addon, `IngestOptions.source`, platform matrix, bundle smoke test

group-2

sourcing-migration

#559

· willwashburn opened

on Sep 19, 2026

[G2] Watch mode, `--hook claude`, pending stamps and gap warnings over the relayhistory backend

group-2

sourcing-migration

#558

· willwashburn opened

on Sep 19, 2026

[G2] RelayHistoryBackend: depend on the `ai-hist` crate, map `SessionEvidence` onto burn's record types behind the backend seam (feature-flagged, off by default)

group-2

sourcing-migration

#557

· willwashburn opened

on Sep 19, 2026

[G1] Remove vestigial ingest surface before the swap: opencode-stream cursor, legacy harnesses/ adapters, stale reader docs

group-1

sourcing-migration

#556

· willwashburn opened

on Sep 19, 2026

[G1] Characterization lock: ledger golden snapshots for the full fixture corpus and a `burn state parity` ledger differ

group-1

sourcing-migration

#555

· willwashburn opened

on Sep 19, 2026

[G1] Introduce a SessionSourceBackend seam in ingest so the built-in readers can be swapped for relayhistory

group-1

sourcing-migration

#554

· willwashburn opened

on Sep 19, 2026

Epic: burn stops parsing harness logs and depends on relayhistory for all session data

epic

sourcing-migration

#553

· willwashburn opened

on Sep 19, 2026

docs: add a Troubleshooting note to the README

factory

#540

· kjgbot opened

on Sep 15, 2026

Navigation Menu

All issues

[G3] Accounting fixes unlocked by shared evidence: Codex per-request turns (#504), subagent project rollups and harness split (#506), `sessions list` token column

[G3] Cutover: relayhistory becomes the default and only source; delete the harness readers, walkers, cursors and fs watcher; ship as a major release

[G2] Identity and fingerprint compatibility, cursor migration, and `state rebuild` from the relayhistory store

[G3] Harness expansion through relayhistory: Cursor and Grok in burn (SourceKind, pricing, TOOL_ALIASES, overhead mapping, fidelity policy) and collector-backlog transfer

[G2] Node SDK and MCP packaging with the relayhistory backend: single native addon, `IngestOptions.source`, platform matrix, bundle smoke test

[G2] Watch mode, `--hook claude`, pending stamps and gap warnings over the relayhistory backend

[G2] RelayHistoryBackend: depend on the `ai-hist` crate, map `SessionEvidence` onto burn's record types behind the backend seam (feature-flagged, off by default)

[G1] Remove vestigial ingest surface before the swap: opencode-stream cursor, legacy harnesses/ adapters, stale reader docs

[G1] Characterization lock: ledger golden snapshots for the full fixture corpus and a `burn state parity` ledger differ

[G1] Introduce a SessionSourceBackend seam in ingest so the built-in readers can be swapped for relayhistory

Epic: burn stops parsing harness logs and depends on relayhistory for all session data

docs: add a Troubleshooting note to the README

Search results