Document ops as queue runtime and admission boundary

[roccho-dev]

Purpose

Fix ops as the owner of everything after confirmed queue rows in the editor-to-queue-to-ui flow.

Scope

• Document that ops owns queue contracts, validators, worker runtime, admission gate, receipt writing, projection building, and contract-core integration.
• Document that ops does not own editor UX or browser rendering.
• Align this boundary with the existing cue-append-contract-core package.

Done

• README/docs clearly state: ops = queue runtime + admission + receipt + projection builder.
• A package map shows hq-modeling-runtime, hq-admission-gate, repo-map-projection-builder, and cue-append-contract-core responsibilities.
• Boundary check prevents ops docs from claiming UI renderer or editor ownership.

Scope-achievement declaration

This issue is complete only when all of the following are true:

• Purpose lineage: directly supports editor -> queue -> ui by owning queue-after-confirm runtime; directly supports repo separation; indirectly supports sale-ready explainability.
• Core/port/adapter: docs declare ops pure cores, ports, and adapters separately for queue, worker, receipt, admission, projection, and CUE contractcheck.
• Pure/effect split: ops pure layers perform validation, reduction, admission decision, and projection building; adapters perform file/process/repo IO only.
• False-positive exclusion: boundary checks must not reject legitimate ops ownership of runtime, admission, receipt, projection builder, or contractcheck adapter.
• False-negative exclusion: boundary checks must fail if ops claims editor UX, Vim, browser rendering, or UI state ownership.
• Authority boundary: queue/projection/preview/receipt are evidence or intent; accepted ledger exists only after explicit ops admission.
• Repo cleanliness: ops may be the thick runtime repo, but must not absorb editor or renderer responsibilities.

Non-goals

• Do not implement runtime packages in this issue.
• Do not change ui or edits.

Checks

• Boundary doc/static check passes.
• Existing ops checks keep passing.

Why this matters

This makes the execution and authority side explainable and keeps editor/UI packages thin.