feat: production source and delivery integration (partial)

[fffonion]

Scope — partial delivery, draft

Publishes the accepted runtime source selection, setup/deployment documentation, CI corrections, and Telegram manual-compaction regression update on a new branch. This is not the final production-auth/Guardian delivery.

• RSS owns source priority, validation and error behavior; native bootstrap only supplies bounded source/config facts.
• Fixes encoded-source compatibility without changing the existing scalar and whole-map bounds.
• Corrects production setup and legacy-chat documentation.
• Preserves both CI fixes, including runner-local test scratch configuration.
• Updates the obsolete Telegram /compact test to require one exact skipped/generation reply and unchanged durable generation, history and summary rows; production behavior is unchanged.

Actual verification and review

• Runtime/source component d497d911: accepted after scoped SRC-001 closure; parent executed 48 unique tests and compiled 83 RSS/example sources.
• Documentation component c8ed41a0: accepted; parent executed 23 unique tests.
• Partial composition c02e1dab: parent executed 92 unique relevant tests, corpus 83/83, fmt, narrow Clippy with warnings denied, and clean-tree/diff checks.
• Previous partial head 85c9bf52f31370beea243cabd5d33ed85eece3f2: parent independently executed the complete Telegram target, 36/36 PASS, default features and default parallelism. Test-only scoped review is CLEAN; official/frozen/current source bytes and clean worktree were verified. Focused tests are subsets, not additional counts.
• Remote exact-head CI must still be evaluated; local Rust 1.94.1 results do not claim remote toolchain acceptance.

Open boundaries

• Guardian candidate is maintained separately and is undergoing targeted fixes for user/developer-context completeness and informed owner-only approval previews. It is not included in this head.
• Explicit operator provider-AuthHost startup binding and the final composed/package-source auth acceptance remain open.
• Real Cargo .crate generation failed because the pinned Git pd-host-function dependency lacks a registry version requirement. The verified Git source-distribution alternative is a different format; no dependency pin was replaced.
• Source-distribution DEBUG install/health smoke and four extracted-source provider/auth baseline tests were verified separately at c02e1dab; they do not prove an installed authenticated gateway request or this future final composition.
• Original Task12 classified failures and interrupted broad-run unqualified failures remain separately recorded. No claim that all repository tests pass, no assertion removal/skip to conceal failures, and no refresh/live-provider verification.

Exact-head CI result

Reviewed compatibility fix 6dcf0e83eb4a3987c52836df690a2d87ba882922 is now the published head. It adds four lexical lock scopes in unit tests and six missing transport_identity: None fixture fields, preserving assertions, production behavior and CI gates. Scoped review found no source defects.

• Original head 85c9bf52: Actions 38226151892 passed fmt and failed Rust 1.99 Clippy; tests were skipped.
• New head local worker: three compaction unit cases and 36 Telegram cases passed; six selected fixture targets compiled without execution; fmt and narrow Clippy passed on Rust 1.94.1.
• New head independent parent: 38 passed, 1 failed. gateway_binary_survives_telegram_startup_failure_and_serves_the_api read stderr to EOF without the listening address; its precise exit cause remains unresolved. Six fixture targets compiled, and fmt/narrow Clippy passed. A separate startup diagnostic emitted a listening address; it is not a replacement passing test.
• New head Rust 1.99 CI remains the required remote verification. No all-pass, baseline/transient classification, or final-goal acceptance is claimed.

Keep this PR draft until the remaining production goal and exact-head CI are resolved. No main/master merge requested.