fix(repair): remove router Git writer pressure

[vincentkoc]

Related: #738

What Problem This Solves

Fixes an issue where every distinct @clawsweeper command entered the serialized state-repository writer even when routing completed in seconds and no repair job changed. During the incident, one router finished command processing in about 20 seconds, then waited over 22 minutes at writer queue position 33 before cancellation.

Why This Change Was Made

Distinct maintainer commands remain independent and lossless. The durable processed-command ledger continues through the append/materializer path; the invocation-only latest scan report is no longer Git-published; and jobs/ enters the Git writer only when a command actually changed durable repair work. The materializer retires the old tracked latest report on its next router batch.

User Impact

Routine status and re-review commands no longer contend for the state Git writer after routing, while commands that genuinely create or update repair jobs retain durable publication.

Evidence

• Live failure evidence: run 30010373110 routed successfully, then stalled in the state writer until cancellation.
• 75 focused tests passed.
• Main and repair TypeScript builds passed.
• Targeted formatting, lint, git diff --check, and structured autoreview passed with no actionable findings.
• No SQLite schema or append protocol change.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: fix(repair): remove router Git writer pressure This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: fix(repair): remove router Git writer pressure This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[vincentkoc]

Addressing the ClawSweeper rank-up move: the release-owned changelog edit is removed, focused workflow/materializer coverage exercises both unchanged and changed jobs/ paths, and fresh autoreview is clean (0.87). I am not creating a synthetic repair job in production solely to prove the changed-jobs branch while publication is critical. After merge I will verify the next no-change router run bypasses the Git writer and inspect the next real job-changing command for durable jobs/ publication.

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: fix(repair): remove router Git writer pressure This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.