Tracking F5 / TOC rebuild from docs/plans/v3.2-prove-it-plan.md.
README: Offline TOC rebuild (admin rebuild-toc) is Not implemented. It exits non-zero with guidance. TOC nodes come from the daemon's scheduled rollup jobs. If the rollup job misses, there is no repair.
Phase 57 found that the previous stub printed a TODO and exited 0; it now bail!s. That honesty is correct. This issue is the real implementation.
Work (61-04)
- Implement
admin rebuild-toc for real: rebuild nodes from events for a date range, replacing the exits-non-zero stub.
- Verify: delete TOC nodes in a fixture store, rebuild, assert byte-equal to the scheduled rollup's output.
Related: after a 61-01 import, the March CLI told the user to run memory admin rebuild-toc. That command is a documented non-implementation on main, so backfill and this issue are coupled.
Tracking F5 / TOC rebuild from docs/plans/v3.2-prove-it-plan.md.
README: Offline TOC rebuild (
admin rebuild-toc) is Not implemented. It exits non-zero with guidance. TOC nodes come from the daemon's scheduled rollup jobs. If the rollup job misses, there is no repair.Phase 57 found that the previous stub printed a TODO and exited 0; it now
bail!s. That honesty is correct. This issue is the real implementation.Work (61-04)
admin rebuild-tocfor real: rebuild nodes from events for a date range, replacing the exits-non-zero stub.Related: after a 61-01 import, the March CLI told the user to run
memory admin rebuild-toc. That command is a documented non-implementation on main, so backfill and this issue are coupled.