Context
A deep technical audit of the Autonomous Miner System (AMS, packages/gittensory-miner + apps/gittensory-miner-ui + apps/gittensory-miner-extension) found real, substantiated gaps in robustness, observability, performance, feature completeness, testing, and self-host packaging — distinct from Miner Wave 3's governor/loop/calibration safety mechanics, and distinct from Miner Wave 5's "any repo, any customer" hosted generalization. AMS has genuine working functionality today (discovery, a real CLI, local append-only ledgers), but several fully-built and fully-tested modules are never wired into anything a user can actually run, documentation has drifted from what the code does, and the package sits entirely outside the 99%-patch-coverage bar the rest of the codebase is held to.
This milestone exists so that hardening work has its own honestly-scoped home rather than stretching Wave 3's "Governor, Loop & Calibration" title to cover unrelated territory.
Scope summary
- Robustness & crash safety (9): signal handling, stuck-queue recovery, retry/backoff, pagination, schema versioning, wiring already-tested modules into the CLI, ledger integrity checks.
- Observability (7): a real logging abstraction,
--json-respecting error paths, surfaced rate-limit telemetry, a wired Prometheus renderer, a metrics/tracing surface, cron/alerting guidance, a push surface for the event ledger.
- Performance (5): conditional-GET caching, persisted policy-verdict caching, rate-limit-aware throttling, committed benchmarks, de-duplicating the miner-ui's portfolio view against the CLI's own richer dashboard.
- Feature completeness — core loop (5): dry-run mode, claim-conflict resolution wiring, a calibration-report join, WIP-cap wiring, a governor pause/resume surface.
- Miner UI (7): a daemon/launcher, a real Overview page, fixing the portfolio-view regression, surfacing ledger data, live refresh, real actions, and auth.
- Browser extension (5): live fetch instead of manual paste, resolving the localhost-reachability gap, removing a dead field, adding icons, adding storage validation.
- Testing (6): bringing the package and its UI/extension under a real coverage gate, giving the extension real CI wiring, concurrency tests, a crash-recovery test, more true end-to-end tests.
- Self-host packaging (7): accurate deployment docs, schema-versioning tooling, backup/restore guidance, config validation in
doctor, publishing operational files with the npm package, an operational runbook, an accurate README.
How to use this issue
These 51 items are largely independent of each other and can be worked in any order — unlike Rent-a-Loop or ORB Cloud Readiness, there's no strict phase sequencing here. A handful have soft dependencies noted in their own Boundaries section (e.g. the crash-recovery test depends on the stuck-queue fix existing first).
Re-triage note (post-renumber)
This milestone was renumbered from Wave 5 to Wave 4 and re-triaged for contributor eligibility — most of the 51 items below are now open to contributors (label + assignee changes only; no scope changes). A handful stay maintainer-only where the work touches claim-conflict/anti-farming surfaces or the autonomous loop's own control-flow. A companion batch of 47 new gap-closing issues (MCP exposure, Claude/Codex self-host operational parity, dashboard/observability parity, expanded test coverage) has also been added to this milestone — see #5200 for that batch.
Context
A deep technical audit of the Autonomous Miner System (AMS,
packages/gittensory-miner+apps/gittensory-miner-ui+apps/gittensory-miner-extension) found real, substantiated gaps in robustness, observability, performance, feature completeness, testing, and self-host packaging — distinct from Miner Wave 3's governor/loop/calibration safety mechanics, and distinct from Miner Wave 5's "any repo, any customer" hosted generalization. AMS has genuine working functionality today (discovery, a real CLI, local append-only ledgers), but several fully-built and fully-tested modules are never wired into anything a user can actually run, documentation has drifted from what the code does, and the package sits entirely outside the 99%-patch-coverage bar the rest of the codebase is held to.This milestone exists so that hardening work has its own honestly-scoped home rather than stretching Wave 3's "Governor, Loop & Calibration" title to cover unrelated territory.
Scope summary
--json-respecting error paths, surfaced rate-limit telemetry, a wired Prometheus renderer, a metrics/tracing surface, cron/alerting guidance, a push surface for the event ledger.doctor, publishing operational files with the npm package, an operational runbook, an accurate README.How to use this issue
These 51 items are largely independent of each other and can be worked in any order — unlike Rent-a-Loop or ORB Cloud Readiness, there's no strict phase sequencing here. A handful have soft dependencies noted in their own Boundaries section (e.g. the crash-recovery test depends on the stuck-queue fix existing first).
Re-triage note (post-renumber)
This milestone was renumbered from Wave 5 to Wave 4 and re-triaged for contributor eligibility — most of the 51 items below are now open to contributors (label + assignee changes only; no scope changes). A handful stay maintainer-only where the work touches claim-conflict/anti-farming surfaces or the autonomous loop's own control-flow. A companion batch of 47 new gap-closing issues (MCP exposure, Claude/Codex self-host operational parity, dashboard/observability parity, expanded test coverage) has also been added to this milestone — see #5200 for that batch.