Summary

Adds an escalation tier so the daemon converges whale-scale raw-authority components (aggregate payload over the ordinary 64MiB fast-path envelope) instead of leaving them permanently resource-blocked. Live witness: codex:019f49d8 (788 raws, 6.33GB) has zero index presence because every ordinary daemon pass logs "resource-blocked ... exceed replay limit" and moves on, forever.

Problem

_RAW_MATERIALIZATION_DAEMON_BLOB_LIMIT_BYTES (64MiB, daemon/cli.py:89) exists to bound writer-hold transaction length and parse memory during the daemon's ordinary raw→index convergence pass. It works correctly as a fast-path limit, but a component that exceeds it has no escalation path — the daemon owns raw→index convergence end to end, so a permanent manual/offline requirement for oversized components is a policy bug (operator ruling, automagic-invariants doctrine).

The two concerns the limit protects already have productized answers elsewhere in the codebase: stream-record parse dispatch (is_stream_record_provider, already routes Codex/Claude Code/Beads/Hermes through parse_stream_payload), the RawParsePrefetchCache inflight-byte budget, a dedicated whale-residency parsed-tree spill tier (_ParsedSessionSpill, polylogue-odm1), and commit-batched replay (raw_authority_commit_batch_size, PR #3248). The resource-block gate itself is purely an admission check on max_payload_bytes — nothing else in the pipeline needed to change.

Solution

Escalation tier, not a blanket limit raise:

1. Ordinary fast-path limit unchanged. The 64MiB envelope still governs every regular daemon pass.
2. Quiescence-triggered whale pass (polylogue/daemon/cli.py): _periodic_raw_materialization_convergence now tracks whether the ordinary trickle conveyor reached genuine quiescence this tick (no remaining candidates, or no progress — never on bulk-rebuild-in-flight or browser-capture-spool-pending breaks, which are deferrals for unrelated reasons). On quiescence, _maybe_run_raw_materialization_whale_pass looks up one resource-blocked, entirely stream-safe component via a new read-only selector and runs a dedicated pass for it, scoped by raw_artifact_id at a widened envelope (raw_authority_whale_payload_bytes, default 8 GiB), through the same writer coordinator. Emits raw_materialization_whale_pass_started/_completed daemon events. Gated by daemon_whale_raw_materialization (on by default — the whole point is the daemon self-heals codex:019f49d8 without an operator flipping a switch).
3. Non-stream-safe components stay blocked, distinctly. polylogue/storage/repair.py adds _raw_materialization_component_stream_safe (all members) and raw_materialization_whale_pass_candidate (fairness-ordered, read-only mode=ro, reuses the existing component/fairness machinery — never selects a component with any non-stream-safe member). New raw_materialization_non_stream_safe_oversized_count metric complements the existing raw_materialization_stream_oversized_count. polylogue/sources/revision_backfill.py's record_resource_blocked_revision_census now records whether the blocked component is stream-safe, so the durable per-raw census detail text says "escalation-eligible: stream-safe, awaiting a bounded daemon whale pass" vs "escalation-blocked: non-stream-safe, requires manual/offline convergence" — without touching the admission fingerprint identity (re-admission-on-wider-envelope invariant preserved).
4. Product boundary. polylogue/product/raw_authority.py's repair_materialization/new whale_pass_candidate wrappers thread raw_artifact_id through to storage, keeping the daemon off polylogue.storage.repair internals for this call.
5. Config surface. raw_authority_whale_payload_bytes (escalation envelope) and daemon_whale_raw_materialization (on/off switch) added to the config inventory, TOML/env layering, and docs/configuration.md.

Alternatives rejected

• Raising the ordinary 64MiB limit globally — bead explicitly rules this out ("escalation tier, not a blanket limit raise"); it would remove the writer-hold/parse-memory bound for every pass, not just whale components.
• Building new streaming/memory-bounding machinery — unnecessary; the codebase already has it (see Problem section), so the fix is pure orchestration (when to widen the envelope, for what, gated how).

Verification

devtools test tests/unit/storage/test_repair.py tests/unit/daemon/test_daemon_cli.py \
  tests/unit/sources/test_revision_backfill.py tests/unit/core/test_config_inventory.py \
  tests/unit/core/test_config.py tests/unit/core/test_config_resolution_regression.py
# 382 passed, 1 pre-existing unrelated failure
# (test_bulk_rebuild_routing_resumable_transaction_drives_pass_even_below_threshold,
#  reproduced identically on unmodified master via `git stash`)

devtools verify --quick
# format/lint/mypy/render-all-check/topology/layering/closure-matrix/manifests/
# ci-workflows/doc-commands/docs-coverage/test-infra-currency/test-clock-hygiene/
# pytest-timeout-overrides/degrade-loudly all green

Anti-vacuity (mutated production code, confirmed red, reverted, confirmed green again):

• Deleting the daemon's quiescence-triggered whale-pass call (if quiescent and not ...: await _maybe_run_raw_materialization_whale_pass()) breaks test_periodic_raw_materialization_convergence_schedules_whale_pass_on_quiescence and test_periodic_raw_materialization_convergence_skips_whale_pass_mid_burst.
• Forcing raw_materialization_whale_pass_candidate to always return None breaks test_raw_materialization_whale_pass_candidate_selects_stream_safe_blocked_component and test_raw_materialization_whale_pass_converges_blocked_component_to_resolved_head.

New regression tests build a synthetic multi-raw "whale" fixture (tests/infra/revision_backfill_benchmark.build_revision_chain_corpus — a growing-file revision chain, the exact shape of the live codex:019f49d8 witness) exceeding a lowered test envelope, and prove: the ordinary pass blocks it; the whale pass converges it to a resolved head (sessions row materialized in index.db); commit-batch size genuinely controls writer-hold granularity (test_raw_materialization_whale_pass_commit_batches_bounded); and a non-stream-safe oversized component gets the distinct typed census reason (test_raw_materialization_ordinary_pass_census_detail_distinguishes_escalation_eligibility).

Not run: full devtools verify (broad local gate) — the touched-file targeted run above plus --quick cover the changed surface; a full run was not required for this scope. Live-archive verification of codex:019f49d8 itself is out of scope for this PR (would touch the live archive, which agent work must never do) — it is the deploy-time acceptance witness per the bead.

AC matrix (polylogue-t93b)

Ref polylogue-t93b