EPICON C 379 INFRA federation scan 20 optimizations v1

epicon_id: EPICON_C-379_INFRA_federation-scan-20-optimizations_v1
ledger_id: kaizencycle
scope: docs
mode: normal
issued_at: 2026-07-21T15:00:00Z
expires_at: 2026-10-19T15:00:00Z
justification:
  VALUES INVOKED: integrity, transparency, witness-fidelity
  REASONING: A report is a claim, not a verification (Witness Table doctrine, C-373).
    Standing memory listed identity-login and cron-frequency as active incidents;
    live evidence shows both resolved. Continuing to treat them as open wastes cycle
    attention. Reserve-block canon lag (must use deduplicated count, not seals_count),
    PR template sprawl, and wallet DB misconfiguration were under-tracked or misclassified.
    This PR publishes the witnessed scan and 20-item optimization backlog as the
    canonical C-379 opening record; implementation follows in scoped follow-up PRs.
  ANCHORS:
    - docs/epicon/cycles/C-379/FEDERATION_SCAN_WITNESS_TABLE.md
    - docs/epicon/cycles/C-379/OPTIMIZATIONS_C-379_20-items.md
    - mobius-identity-service.onrender.com/health (db_ok true, 2026-07-21T15:00Z)
    - mobius-civic-ai-terminal/vercel.json (cron */30 normalization)
    - canon/reserve-blocks/MANIFEST.json (194 blocks, 2026-07-12)
  BOUNDARIES: Does not re-litigate C-370/C-371 Q2/Q3 dual-quorum reconciliation.
    Does not apply Track R receipts. Does not mutate production KV. Planning artifact
    only — items 4-20 implemented in follow-up PRs.
  COUNTERFACTUAL: If wallet /health remains degraded after DATABASE_URL fix and warm
    retry, item 6 stays Tier 2 incident and blocks closeout of mic-wallet open_flags.
counterfactuals:
  - If tests fail on follow-up implementation PRs, do not merge those items
  - If MII drops below 0.95 on a follow-up change, revert that change independently
  - If re-scan shows identity db_ok false, reopen item 1 as incident not closeout