Add durable Orrery publication and graph readers to the local provider

[anth-volk]

Fixes #3

Implementation

Keep one Python distribution, microcosm-emitter, with required telemetry and an internal completed-graph publication library. Resolve the existing extraction conflicts without restoring removed package names or database fallbacks.

• Keep the generic host separate from telemetry, authentication and database imports. Load selected modules in one separate local process with independent workers, private startup configuration and bounded Unix-socket requests.
• Keep build adapters socket-only. The separate local service owns telemetry interpretation, event construction, credential redaction, persistence, authentication, graph hashing and delivery. Valid supplied stage identifiers remain unchanged.
• Preserve SQLAlchemy declarative ORM and Alembic. Upgrade the existing 20261007_01 queue to 20261008_02 for graph jobs while retaining producer sequences, event IDs and upload eligibility. Graph publication requires no telemetry run registration.
• Preserve typed graph inventories and receipts, exact file bytes, retry delays and expiring worker reservations. Graph queries allow 30 seconds; telemetry acknowledgements, readiness and close requests retain their short limits. Failed startup or unacknowledged requests never claim data was saved by a fallback.
• Add the existing Microcosm block() outcome and optional fail(error_code=...). The service closes the active stage and records a blocked run atomically, validates collector-required metadata before and after sanitization, and prevents later heartbeat or parent-exit handling from replacing a finished outcome. Microcosm remains responsible for failure classification.
• Add close_service_on_finish=False for shared-process ownership. Completion, failure and refusal finish telemetry without shutting down the graph socket; explicit outer cleanup closes the host after graph requests. Standalone cleanup remains automatic by default.
• Preserve existing permanent HTTP client-error handling when registering runs and uploading events: retain only the rejected producer's records locally, except retryable HTTP 408/429. HTTP 401 renews the short-lived credential; network and server failures remain retryable.
• Keep the separate TypeScript reader package and interfaces. Build one Python wheel/source archive for one PyPI publisher; retain separately verified npm tarball publication.

No collector/dashboard source changes, new infrastructure, credentials, schema changes for outcomes, release or deployment. This does not incorporate unmerged emitter PRs #5–#7; it ports only the existing Microcosm outcome and collector-rejection behavior required by the consumer extraction.

Verification

• Independent verification found all four approved items clean, including atomic rollback, thin-adapter boundaries, shared-process cleanup ordering and per-producer HTTP rejection handling.
• Final post-format affected client/module/delivery/subprocess/boundary tests: 135 passed on Python 3.13 and 135 passed on Python 3.14. The earlier full noncollector run passed 180 tests before the last HTTP-rejection change; it is not represented as a final full-suite run.
• Exact final wheel installed noneditably: all nine collector contract tests passed against pinned collector 280459c8d782658b3fb6098b27e9acba11af29d8 and disposable PostgreSQL 16. Coverage includes blocked metadata, caller-supplied failure codes, rejected identities and lost-ack duplicate delivery, with synthetic credentials and loopback networking only.
• One wheel/source archive and strict metadata checks passed. Clean installed host, telemetry-only, graph-only and combined-process checks, packaged migrations, blocked outcomes and coded failures passed on Python 3.13 and 3.14.
• Full Ruff lint/format, Bash syntax, actionlint and diff checks passed. CI/helper pins match; collector qualification installs the downloaded built wheel before tests. No new environment variable or secret is required.
• The unchanged TypeScript reader previously passed all 25 tests, formatting, types, build and isolated tarball imports/browser-target compilation during conflict resolution. No browser automation or visual inspection.

Publication and infrastructure status

Release validation and qualification precede approval-protected publication of the tested Python artifacts. The separate npm job waits for Python publication and publishes the tested reader tarball. Only publication jobs receive OIDC permission; CI supplies no long-lived publishing credential.

The existing GitHub pypi approval environment and release-tag restriction were previously verified. The Python pending publisher is user-confirmed; private registry settings and the npm package's initial publication/trusted-publisher configuration remain unverified. The live collector's deployed revision and hosted graph API readiness also remain unverified: the compatibility pin proves source behavior, not production deployment.

No registry bootstrap, release, package publication, hosted deployment or consumer activation occurred in this work. No queued GitHub checks are being monitored.