feat(memory): follow main runtime for distill extraction

[seoseo-ai]

Summary

• make the strict distill v1 input/output contract accept Claude, Codex, and Piri source sessions
• add an auto|off|claude|codex|piri extractor factory; auto follows the main ccc-node runtime while explicit overrides remain possible
• add isolated tool/session/context-free Claude and Piri CLI extractors, Claude bounded snapshots, provider-correct cost metering, and Claude journal triggers/sinks
• suppress the legacy Claude hook distiller only while the shared bridge pipeline is managing the session, preventing duplicate writes
• expose conversation readiness and distill extractor readiness separately in ccc-doctor

Safety

• no provider call, deployment, bridge restart, or live canary was performed
• extractor stdin is the existing bounded/redacted canonical JSON contract
• provider stdout/stderr and bodies stay out of errors; output is byte-bounded and schema/provenance validated
• CCC_MEMORY_DISTILL_PROVIDER=off disables the shared workers and journal triggers
• legacy CCC_CODEX_DISTILL_* settings and schema/type filenames remain compatibility fallbacks

Tests

• focused provider-neutral/runtime/doctor/options suite: 155 passed
• broader changed-surface suite: 223 passed + 133 subtests
• full bridge suite on Termux: 2274 passed, 12 skipped; remaining failures were pre-existing platform constraints (os.link unavailable, /tmp//data permission assumptions, local Claude CLI absent)
• claude/hooks/distill-scope.test.sh: PASS=34 FAIL=0
• provider capability matrix/schema checks: 28 passed + 133 subtests

Closes #951

[jinon86]

Approved after explicit operator authorization using the Seoseo-held jinon86 credential.