Task: 180.C.29.11 — compare TODOS/phase-180.md,
TODOS/phase-180-reference.md, implemented code, docs, tests, release evidence,
and known gaps; surface missing ordered tasks before release instead of relying
on the reference file.
- Current audit date: 2026-07-01
- Current branch:
oshun-v1-metis - Baseline inspected before this update:
37ad892c7e - Method: derive counts from the canonical
TODOS/phase-180.md, inspect current backing files for items whose status changed since the older 2026-06-21 audit, keep uncertain or externally gated items open, and enforce the open-item mapping withevaluatePhase180ChecklistTrackerSyncFiles().
This file is the evidence artifact for 180.C.29.11, which is now checked in
the canonical checklist. It does not close the broader Stage 29 release gate:
180.C.29.08, .09, .10, and .12 remain open until the full verification,
release evidence, and product acceptance runs are performed with the required
external systems.
1. Current Headline Result#
- Totals: 454
[x], 23[ ](477 checklist items), 0 other marker styles. - Stage 21.20 is still open, but no longer a pure paper gap. The structured new-operator usability study now has a local fail-closed plan/evaluator; final completion still requires recruited operator observations and fix evidence for the top three friction points.
- Stages 23 and 24 are no longer open. The current repository contains the
Unreal production command contracts, host adapter handlers, fixtures, tests,
and hardware verification runbook for the
180.C.23and180.C.24command surfaces. - Stage 36 is still open, but no longer a pure paper gap. The locally testable Windows contracts, Authenticode readiness check, and Stage 36 evidence gate are implemented and covered by tests; final completion still requires real Windows build/signing/hardware evidence.
- Stage 26 items 26.01 and 26.02 are now CLOSED with live macOS hardware
evidence. The native SwiftPM AppKit menu-bar shell and the loopback
token-guarded host local-control surface ran live on the physical macOS rig
MAC-HOST-03(2026-07-07), and the full launchd LaunchAgent lifecycle (bootstrap, KeepAlive crash restart, supervised child restart, graceful SIGTERM stop without restart, clean bootout/uninstall) was exercised for real (evidence/180.C.26.01/,evidence/180.C.26.02/). The remaining Stage 26 items (26.06, 26.09, 26.14) still require an Apple Developer ID signing identity, signed-package install QA captured after the signing evidence, and non-developer acceptance evidence; the roll-up gate stays fail-closed. - Stages 29 and 30 now have an executable final-GA gate contract. The final verification matrix, release evidence bundle, product acceptance scenarios, conditional platform scope, and fleet closure gate are encoded locally with structured dated evidence records. Bare requirement ID summaries do not pass; final completion still requires live macOS/Windows, cloud, stream, diagnostic, and operator evidence.
- Stage 38 is still open, but no longer lacks a local retirement gate. The bridge retirement PR, zero-consumer telemetry, package cleanup, post-removal scan-scope, documentation, and approval requirements are encoded locally; final completion still requires Remote Host GA, zero consumers, actual removal, and post-removal verification.
- No currently open item is proven locally closable in this workspace. The remaining 23 open items require human usability testing, an Apple Developer ID signing identity plus signed-package install QA, a real Windows host/signing pipeline, the consolidated final release run, or post-GA bridge retirement.
- Checklist/tracker drift is now covered by an executable local gate. The
@bellona/remote-control-testingsync evaluator passes only when tracker rows remain in canonical checklist order, task text starts from the checklist task, statuses stay limited toCompleteorBlocked, checked rows carry concrete owner, changed-files, verification, and evidence cells, every open Phase 180 item has a matching blocked tracker row with concrete verification, evidence, and blocker notes, and every blocked tracker row remains unchecked in the canonical checklist.
2. Current Per-Stage Counts#
| Stage | Title | [x] |
[ ] |
|---|---|---|---|
| 180.C.01 | Phase Control, Tracker, and Ground Rules | 10 | 0 |
| 180.C.02 | Repository Audit and Architecture Decisions | 16 | 0 |
| 180.C.03 | Remote Protocol Package | 16 | 0 |
| 180.C.04 | Mock Harness and Contract Tests | 13 | 0 |
| 180.C.05 | Remote Gateway Walking Skeleton | 10 | 0 |
| 180.C.06 | Remote Host Walking Skeleton | 10 | 0 |
| 180.C.07 | Device Pairing, Auth, Policy, and Approvals | 10 | 0 |
| 180.C.08 | Audit, Observability, and Timeline Foundations | 12 | 0 |
| 180.C.09 | Blender Read-Only Adapter MVP | 10 | 0 |
| 180.C.10 | Blender Safe Mutation MVP | 10 | 0 |
| 180.C.11 | Browser CDP MVP | 12 | 0 |
| 180.C.12 | Live Stream and Minimal Control Room MVP | 16 | 0 |
| 180.C.13 | Desktop Fallback MVP | 14 | 0 |
| 180.C.14 | MCP and Cloud-Agent MVP | 26 | 0 |
| 180.C.15 | Unreal Read-Only and Safe Mutation MVP | 10 | 0 |
| 180.C.16 | Alpha Hardening and MVP Release Gate | 15 | 0 |
| 180.C.17 | Blender Production Command Coverage | 10 | 0 |
| 180.C.18 | Blender Advanced Automation and Render Coverage | 10 | 0 |
| 180.C.19 | Browser Production Automation Coverage | 10 | 0 |
| 180.C.20 | Browser Use and Optional Extension Integration | 10 | 0 |
| 180.C.21 | Control Room Production Experience | 19 | 1 |
| 180.C.22 | File, Artifact, and Cross-App Workflow Coverage | 14 | 0 |
| 180.C.23 | Unreal Production Command Coverage | 10 | 0 |
| 180.C.24 | Unreal Sequencer, Render, Build, and Diagnostics | 10 | 0 |
| 180.C.25 | Networking, Cloud Deployment, and Transport Hardening | 17 | 0 |
| 180.C.26 | macOS Host Packaging, Permissions, and Updates | 14 | 3 |
| 180.C.27 | Security, Privacy, and Governance Completion | 18 | 0 |
| 180.C.28 | Observability, Reliability, and Replay Completion | 13 | 0 |
| 180.C.29 | Final Verification, Documentation, SDKs, and Release | 12 | 4 |
| 180.C.30 | Multi-Host Fleet and Advanced Production Expansion | 11 | 1 |
| 180.C.31 | Cross-cutting UX Foundations | 10 | 0 |
| 180.C.32 | Adapter SDK and Conformance Suite | 10 | 0 |
| 180.C.33 | Timecode, Color, and Media Pipeline | 10 | 0 |
| 180.C.34 | Notifications and External Event Sinks | 10 | 0 |
| 180.C.35 | Tier-2 DCC Adapter Onboarding | 10 | 0 |
| 180.C.36 | Windows Host Support | 0 | 10 |
| 180.C.37 | Linux Host Support | 10 | 0 |
| 180.C.38 | Bridge Coexistence and Deprecation | 6 | 4 |
3. Remaining Open Items#
Blocker legend:
- HUMAN — recruited operator usability study.
- HW-MAC — physical macOS host evidence.
- SIGN — Apple Developer ID / notarization or Windows Authenticode signing.
- HW-WIN — Windows host, Windows build pipeline, and live Windows probes.
- RELEASE-RUN — consolidated final verification/evidence/acceptance run.
- GA — post-GA bridge retirement and zero-consumer proof.
- GATE — roll-up item that closes only when its dependencies close.
| Item | Blocker | Current status |
|---|---|---|
| 180.C.21.20 | HUMAN | Local usability-study gate exists; final closure still requires observing recruited new operators under pressure and fixing the top three findings with evidence. |
| 180.C.26.06 | SIGN | Local signing-readiness contract exists; Apple Developer ID signing, notarization, stapling, and verification for the host/helper/plugin/update artifacts remain gated. |
| 180.C.26.09 | HW-MAC | Local install QA scenario matrix exists; the signed-package scenarios (clean install, upgrade, update rollback) still require a real macOS run against notarized packages captured after the 180.C.26.06 signing evidence. |
| 180.C.26.14 | GATE/HW-MAC | Local Stage 26 roll-up gate exists and is required by final-GA evidence; 26.01/26.02 closed on macOS rig MAC-HOST-03, but non-developer acceptance still depends on 26.06 signing and 26.09 signed-package QA. |
| 180.C.29.08 | RELEASE-RUN | Local final-GA gate now codifies the verification matrix; deployment smoke and hardware-in-the-loop evidence are still required before closure. |
| 180.C.29.09 | RELEASE-RUN | Local final-GA gate now enumerates the GA evidence bundle; live logs, screenshots/streams, diagnostic bundles, security review, rollback, compatibility, and signoff remain gated. |
| 180.C.29.10 | RELEASE-RUN | Local final-GA gate now enumerates final product acceptance scenarios; same-LAN two-MacBook and cloud-agent sessions still require real hardware/cloud. |
| 180.C.29.12 | GATE/RELEASE-RUN | Stage 29 roll-up gate; executable local gate depends on .08 through .10. |
| 180.C.30.10 | GATE/RELEASE-RUN | Final multi-host fleet gate; executable local gate depends on end-to-end live one-or-many remote creative host evidence. |
| 180.C.36.01 | HW-WIN/SIGN | Local MSI/service lifecycle contract exists; signed MSI build/install still requires Windows. |
| 180.C.36.02 | HW-WIN | DXGI/UIAutomation/SendInput strategy contract exists; live probes still require Windows. |
| 180.C.36.03 | HW-WIN | Permission report contract exists; UAC/CFA/Smart App Control behavior still requires Windows. |
| 180.C.36.04 | HW-WIN | Chrome/Edge managed-profile launch contract exists; live browser policy/profile proof still requires Windows. |
| 180.C.36.05 | HW-WIN | Discovery candidate contract exists; real Blender/Unreal/Chrome/Edge discovery still requires Windows. |
| 180.C.36.06 | HW-WIN/SIGN | Signed update-channel contract exists; signed installer manifests and rollback drill still require Windows signing/build evidence. |
| 180.C.36.07 | HW-WIN | Shared diagnostic bundle contract exists; real installed Windows bundle collection remains gated. |
| 180.C.36.08 | HW-WIN | Role derivation and fleet-scheduler contract exists; live Windows render-node/browser-admin validation remains gated. |
| 180.C.36.09 | HW-WIN/HW-MAC | Capability parity comparator exists; real macOS-to-Windows parity run remains gated. |
| 180.C.36.10 | GATE/HW-WIN | Local Stage 36 roll-up gate rejects placeholder evidence, generic parity summaries, generic artifact IDs without concrete suffixes, stale or non-canonical timestamp evidence, placeholder/prefix-only runner or operator suffixes, wrong runner classes, and weak acceptance operators; final closure depends on real Windows parity and operator acceptance evidence. |
| 180.C.38.07 | GA | Local retirement gate exists; removal PR evidence remains premature while old bridge consumers still exist. |
| 180.C.38.08 | GA | Local post-removal scan contract exists; the scan can only pass after actual bridge removal. |
| 180.C.38.09 | GA | Local cleanup/zero-consumer gate exists; bridge package deletion is still gated on Remote Host GA and zero consumers. |
| 180.C.38.10 | GATE/GA | Local retirement roll-up gate exists; final closure still depends on .07 through .09, docs updates, and approval evidence. |
Open-item count by primary blocker:
| Primary blocker | Count |
|---|---|
| HW-WIN / Windows signing | 10 |
| GA / bridge retirement | 4 |
| HW-MAC | 1 |
| RELEASE-RUN | 3 |
| GATE / RELEASE-RUN | 2 |
| SIGN / Apple notarization | 1 |
| GATE / HW-MAC | 1 |
| HUMAN | 1 |
| Total | 23 |
4. Evidence for Recently Changed Areas#
4.1 Stages 23 and 24 — Unreal Production and Long-Running Commands#
The older audit treated stages 23 and 24 as open. The current checklist marks both stages complete, and the current tree contains backing implementation:
- Protocol command constants, schemas, fixture builders, and registry wiring:
libs/bellona/remote-protocol/src/unreal.ts,libs/bellona/remote-protocol/src/schema-registry.ts,libs/bellona/remote-protocol/src/fixtures.ts, andlibs/bellona/remote-protocol/src/unreal.test.ts. - Host adapter handlers and deterministic provider fallback paths:
apps/bellona/remote-host/src/unreal-adapter.ts,apps/bellona/remote-host/src/unreal-adapter.test.ts, andapps/bellona/remote-host/src/unreal-adapter-fixtures.test.ts. - Hardware verification requirements for the parts that cannot be fully proven
in CI:
docs/domains/bellona/extras/remote-control/unreal-hardware-verification.md.
Important limitation: this audit does not claim that the full Stage 29 hardware
acceptance matrix is done. Stage 23/24 command contracts and adapter behavior
are implemented/tested, and hardware verification notes exist, but final release
acceptance still requires the broader 180.C.29.08-.10 evidence.
4.2 Stage 36 — Windows Host Local Contracts#
The current repository adds deterministic Windows contracts for the portions of Stage 36 that can be proven on Linux:
- Implementation:
apps/bellona/remote-host/src/windows-host-support.ts. - Tests:
apps/bellona/remote-host/src/windows-host-support.test.ts. - Evidence note:
docs/domains/bellona/extras/remote-control/windows-host-local-contracts.md.
Covered local contracts include the signed MSI/Windows Service lifecycle plan,
DXGI/UIAutomation/SendInput desktop strategy, Windows permission projection
through @bellona/host-runtime, isolated Chrome/Edge CDP managed profiles,
fail-closed launch-time initialUrl rejection so Windows browser navigation
uses the normal browser.navigate policy path, Windows discovery candidates,
signed update-channel plan, shared diagnostic bundle shape/redaction, fleet role
validation, macOS/Windows capability parity comparison, Authenticode
signing-readiness validation, and a Stage 36 roll-up gate that requires
canonical UTC millisecond Windows runner artifact records with unique artifact
identifiers across all stage evidence records, artifact IDs that identify both
the checklist item and evidence slot they prove plus a concrete non-placeholder
run/artifact suffix, non-stale evidence capture times, Windows host/signing
runner prefixes with concrete suffixes for the right evidence class, a distinct
macOS host parity runner with a concrete suffix, a passing structured parity
comparator result covering the browser, desktop, and Unreal MVP command anchors,
and a final Windows acceptance operator identity with a concrete suffix captured
after every prerequisite Stage 36 evidence record. The gate also rejects signed
update rollback evidence captured before signed-MSI/service lifecycle evidence
and macOS/Windows parity evidence captured before the Windows capability records
it compares.
Stage 36 remains open because the final evidence requires a real Windows host: signed MSI install, Authenticode, Windows Service lifecycle, live DXGI and input probes, UAC/CFA/Smart App Control behavior, real application discovery, live diagnostic bundle collection, and cross-host parity runs.
4.3 Stage 26 — macOS Host Local Contracts#
The current repository now adds deterministic macOS contracts for the portions of the remaining Stage 26 work that can be proven on Linux:
- Implementation:
apps/bellona/remote-host/src/macos-host-support.ts. - Tests:
apps/bellona/remote-host/src/macos-host-support.test.ts. - Evidence note:
docs/domains/bellona/extras/remote-control/macos-host-local-contracts.md.
Covered local contracts include the menu-bar status/control model, LaunchAgent
lifecycle command plan, Developer ID/notarization readiness check with identity
shape validation, clean install/upgrade/permission-revoked/adapter-repair/
update-rollback/crash-loop/uninstall QA matrix, install QA evidence evaluator
requiring current-run canonical UTC millisecond per-scenario artifacts with
unique identifiers for every required evidence kind plus scenario/kind-scoped
artifact IDs and URIs, and contextual operator:macos-install-qa: QA
identities. The Stage 26 roll-up gate rejects placeholder booleans, generic
install-QA summaries without complete per-scenario QA records or captured before
the scenario evidence they summarize, stale or non-canonical QA runs,
non-canonical QA artifacts, generic QA operators, non-macOS host runner records,
non-developer acceptance without a non-developer operator identity or captured
before prerequisite Stage 26 evidence, stale or non-canonical timestamp
pre-contract stage evidence, empty runner/operator suffix placeholders, stage
artifacts that do not identify both their checklist item and exact evidence
slot, or artifact identifiers duplicated within or across evidence records.
Stage 26 remains open because the final evidence requires a real macOS host: native AppKit/SwiftUI menu-bar app execution, launchd registration and crash restart observation, Developer ID signing and notarization, live install QA, and a non-developer acceptance run.
4.4 Stages 29 and 30 — Final GA Release Gate Contract#
The current repository now adds a deterministic final-GA gate for the portions of the remaining Stage 29 and Stage 30 release work that can be proven on Linux:
- Implementation:
testing/bellona/remote-control/final-ga-release-gate.ts. - Tests:
testing/bellona/remote-control/tests/final-ga-release-gate.test.ts. - Evidence note:
docs/domains/bellona/extras/remote-control/final-ga-release-gate.md.
Covered local contracts include the final verification matrix for 180.C.29.08,
the release evidence artifact list for 180.C.29.09, the Stage 26 macOS host
packaging/acceptance evidence requirement, the final acceptance scenario matrix
for 180.C.29.10, the 180.C.29.12 roll-up dependency, the conditional
180.C.36/180.C.37 platform-scope gate with explicit macOS-scoped
release-note and approval evidence for any waiver, and the 180.C.30.10
one-or-many host fleet closure requirements. Automated release-log records must
include command, commit, and environment context; acceptance and fleet records
must name the required evidence kinds they cover; count-only artifact lists do
not satisfy the gate. Structured evidence must be captured on or after
2026-07-02T00:00:00.000Z. Each final-GA requirement must also have exactly one
structured evidence record, so duplicate records for the same verification,
release-evidence, acceptance, or fleet requirement keep that requirement
missing. Artifact IDs must name the final-GA record kind, requirement ID, and
concrete evidence suffix, and must be unique across the full final-GA evidence
snapshot, so one pasted log, capture, bundle, or placeholder cannot satisfy
independent verification, release-evidence, acceptance, and fleet requirements.
Environment, reviewer, operator, and fleet-run IDs must also use contextual
final-GA prefixes with concrete non-placeholder suffixes. Stage 26 macOS host
packaging/acceptance evidence must identify both the non-developer operator rig
and macOS host rig; the release evidence record must specifically name the
MAC-OP-01 operator rig and MAC-HOST-01 host rig. Conditional Windows/Linux
completion is a two-layer proof: the final-GA conditional-platform records
must pass, and the matching evaluateWindowsHostStageGate or
evaluateLinuxHostStageGate roll-up evidence must also pass before 180.C.36
or 180.C.37 can count as complete. Generic final-GA platform records therefore
cannot bypass missing Windows parity evidence or missing Linux build-node
validation. Conditional Windows/Linux scope waivers must include canonical macOS
GA release notes, target-platform scope text, current approval from an
operator:final-ga-waiver-approver: identity, residual-risk ownership from an
owner:final-ga-waiver-risk: identity, and unique supporting evidence under the
remote-control docs tree; placeholder waiver approver, risk-owner, or evidence
URL suffixes do not satisfy the gate. Final test-log release evidence must be
captured after every verification record it summarizes, operator acceptance
signoff must be captured after every final product acceptance scenario record,
and fleet closure records must be captured after the Stage 29 verification,
release evidence, and acceptance records they close over.
Stages 29 and 30 remain open because the final evidence still requires deployed cloud smoke, real same-LAN and cloud-agent sessions, stream/capture artifacts, diagnostic bundles from final runs, hardware-in-the-loop macOS/Windows evidence, and operator acceptance signoff.
4.5 Stage 37 — Linux Host Support Local Gate#
The current repository now adds a deterministic Stage 37 roll-up gate for the locally testable Linux host support contracts:
- Implementation:
apps/bellona/remote-host/src/linux-host-support.ts. - Tests:
apps/bellona/remote-host/src/linux-host-support.test.ts. - Public API:
evaluateLinuxHostStageGatefrom@bellona/remote-host.
Covered local contracts include the deb/rpm/AppImage packaging plan, Wayland/X11
capture and input strategy, PipeWire audio capture, PolicyKit/cgroup/AppArmor/
SELinux permission policy, headless Blender/Unreal/Chromium adapters, Linux
render-node role behavior, Linux diagnostic bundle production, Linux package
signing and repository distribution, cross-platform fleet participation, and the
180.C.37.10 first-class-node acceptance record. The roll-up gate also requires
separate Linux build-node validation before final acceptance can pass, because
180.C.37.10 requires Linux hosts to function as first-class render, build, and
headless-adapter nodes.
Stage 37 evidence must use canonical UTC millisecond timestamps captured on or
after 2026-07-01T00:00:00.000Z, Linux runner identities with the expected
runner class (LINUX-PKG-, LINUX-RENDER-, LINUX-SIGN-, LINUX-BUILD-, or
the broader LINUX- class where appropriate), unique item-scoped artifact IDs
with concrete non-placeholder run context, and a concrete
operator:linux-acceptance: final acceptance identity. Package signing evidence
must be newer than package distribution evidence, fleet participation evidence
must be newer than the capability records it summarizes, and final acceptance
must be newer than every prerequisite record plus build-node validation.
4.6 Stage 21.20 — Operator Usability Study Local Gate#
The current repository now adds a deterministic local gate for the structured Control Room usability study that cannot itself be performed in this Linux sandbox:
- Implementation:
testing/bellona/remote-control/operator-usability-study.ts. - Tests:
testing/bellona/remote-control/tests/operator-usability-study.test.ts. - Evidence note:
docs/domains/bellona/extras/remote-control/operator-usability-study.md.
Covered local contracts include the required new-operator participant count,
approve-under-pressure timing thresholds, policy explanation clarity thresholds,
approve/deny error-rate threshold, takeover discoverability threshold, published
report evidence, exactly one completed observation per recruited participant per
scenario, required evidence kinds and unique evidence artifacts for each
observation, published-report linkage to recruited participants and observation
evidence artifacts only after those observations satisfy the participant,
scenario, evidence-kind, freshness, and duplicate-artifact checks, canonical
180.C.21.20 report paths that cannot escape via traversal/backslash segments,
contextual participant/scenario/evidence-kind observation artifact IDs with
concrete non-placeholder suffixes, non-stale canonical UTC millisecond
observation and report timestamps, report publication after the observation
records, and unique/valid friction-point fix evidence with concrete
non-placeholder suffixes and canonical UTC millisecond verification timestamps
after the findings report for the top three friction points. The final GA gate
also now lists the study report as release evidence for 180.C.29.09.
Stage 180.C.21.20 remains open because the final evidence requires recruited
new human operators, timed observations under pressure, a published findings
report, and implemented/verified fixes for the observed top three friction
points.
4.7 Stage 38 — Bridge Retirement Local Gate#
The current repository now adds a deterministic local retirement gate for the post-GA Blender/Unreal bridge removal tasks:
- Implementation:
testing/bellona/remote-control/bridge-retirement-gate.ts. - Tests:
testing/bellona/remote-control/tests/bridge-retirement-gate.test.ts. - Evidence note:
docs/domains/bellona/extras/remote-control/bridge-retirement-gate.md.
Covered local contracts include canonical Oshun removal PR evidence for both old
bridges, bridge-specific release-note and migration links, fresh PR submission
timestamps, merged PR evidence by roll-up with merge timestamps after the
cutover block, 30 consecutive days of zero production consumers after the
2026-10-21 cutover anchor, bridge-scoped telemetry artifacts, per-command
zero-consumer telemetry for exactly every compatibility-only command with no
unknown command entries, canonical cleanup PR evidence with cleanup completion
after merged removals and zero-consumer windows, post-removal scans across apps,
libs, services, scripts, testing, and workspace metadata with no remaining
findings, documentation updates, and final retirement approval metadata from an
operator:bridge-retirement-approver: identity dated after the removal PR,
telemetry, cleanup, and post-removal scan evidence. Timestamped bridge
retirement records must use canonical UTC millisecond format before freshness or
chronology is evaluated. The evaluator also requires exactly one removal PR
record per bridge, one zero-consumer telemetry report per bridge, and one
telemetry record per compatibility command, so duplicated or conflicting
evidence cannot satisfy the gate. Bridge-specific PR URLs and telemetry sources
must be distinct, telemetry source and bridge-retirement approver suffixes must
be concrete and non-placeholder, cleanup/post-removal scan commands must use
rg/git grep, explicitly include every root workspace metadata file, target
the exact legacy bridge package and path references across the required scopes,
package cleanup removed-path and removed-package lists must be exact with no
duplicate or unrelated removals, package cleanup allowed-reference paths must be
unique docs/release-note references instead of active workspace dependencies or
traversal back into those dependencies, and stale or non-canonical PR,
telemetry-window, cleanup, post-removal scan, or final approval timestamps
cannot mask later retirement evidence.
Stage 38 remains open because final closure requires Remote Host GA, real zero-consumer telemetry, actual package removal, and post-removal verification after removal has happened.
5. Reference Coverage#
The current 180.C checklist remains a superset of the mainline
TODOS/phase-180-reference.md sections 180.0 through 180.19.
The only reference requirements without an ordered 180.C release task remain
under explicit post-GA/future-extension language:
180.20.1.7host pooling for cloud Mac instances.180.20.2.5collaborative multi-human rooms with explicit locks.180.20.2.6learned adapter-selection policies.180.20.2.7self-healing agent behavior.180.20.2.8digital twin state mirrors.180.20.2.9hardware controller integration.
These are surfaced here as post-GA backlog items rather than treated as hidden release blockers.
6. Current Local Verification Evidence#
Latest local verification performed for the current audit work:
pnpm exec vitest run --config vitest.config.ts src/unreal.test.ts --reporter=dotfromlibs/bellona/remote-protocol— 110 tests passed.pnpm nx test @bellona/remote-host -- unreal-adapter.test.ts unreal-adapter-fixtures.test.ts windows-host-support.test.ts --reporter=dot— 3 files, 102 tests passed.pnpm nx test @bellona/remote-host -- windows-host-support.test.ts --reporter=verbose— 39 tests passed.pnpm nx test @bellona/remote-host -- --reporter=dot— 68 files, 911 tests passed.pnpm nx test @bellona/remote-host -- macos-host-support.test.ts --reporter=verbose— verifies local macOS menu-bar, LaunchAgent, signing-readiness, install-QA, and Stage 26 gate contracts; 1 file / 30 tests passed.pnpm exec vitest run --config vitest.config.ts tests/final-ga-release-gate.test.ts --reporter=verbosefromtesting/bellona/remote-control— verifies local final-GA verification, evidence, acceptance, conditional platform, and fleet gate contracts; 1 file / 36 tests passed.pnpm exec vitest run --config vitest.config.ts tests/operator-usability-study.test.ts --reporter=verbosefromtesting/bellona/remote-control— verifies the local180.C.21.20operator usability study gate; 1 file / 27 tests passed.pnpm exec vitest run --config vitest.config.ts tests/bridge-retirement-gate.test.ts --reporter=verbosefromtesting/bellona/remote-control— verifies the local Stage 38 bridge retirement gate; 1 file / 34 tests passed.pnpm nx test @bellona/remote-host -- linux-host-support.test.ts linux-render-node-role.test.ts --reporter=verbose— verifies the local Stage 37 Linux host roll-up gate plus Linux render-node and build-node role/scheduling contracts; 2 files / 28 tests passed.pnpm nx test @bellona/remote-control-testing— passed after refreshing the stale snapshot fixture and updating the protocol fuzz case for the currentbrowser.profile.use_personalapproval contract.pnpm nx lint @bellona/remote-control-testing— passed.pnpm nx typecheck @bellona/remote-control-testing— passed on TypeScript 6.0.3 without CLI or inherited tsconfig deprecation overrides.pnpm verify:phase 180— now also constrains the disclosed nested third-party TypeScript 5 compiler packages so they cannot be confused with the Phase 180 Bellona compiler surface or silently expand.pnpm verify:phase 180— now also checksDEPENDENCIES.mdfor the TypeScript 6.0.3 runtime baseline so stale pre-TS6 dependency-inventory wording fails the local release gate.pnpm exec tsc --noEmit -p tsconfig.json --rootDir ../../../fromtesting/bellona/remote-control— passed. This is the direct equivalent of the Nx typecheck target on the repository's current TypeScript 6 compiler.pnpm exec tsc --noEmit -p tsconfig.lib.json --rootDir ../../../fromtesting/bellona/remote-control— passed for the library compile shape without emitting generated artifacts.pnpm nx lint @bellona/remote-host— passed with 5 pre-existing warnings in unrelated files.pnpm nx typecheck @bellona/remote-host— passed with the checked-in TypeScript 6.0.3 compiler and no CLI or inherited tsconfig deprecation override.- Changed-file Prettier, stub-indicator, and
git diff --checkchecks passed.
This is useful current evidence, but it is not a substitute for the full
180.C.29.08 final matrix.
7. Bottom Line#
The canonical checklist currently has 454/477 items complete (95.2%).
The remaining 23 items are not proven locally closable in this workspace: they require human study evidence, macOS hardware and signing, Windows hardware and signing, the consolidated release run, or post-GA bridge retirement.
Therefore the Phase 180 objective is not complete, but the current audit does not identify a silent locally actionable checklist item that remains undone. The next true completion work needs one of the external evidence paths: macOS package/signing hardware, Windows host/signing hardware, final acceptance cloud/LAN sessions, recruited operator usability testing, or GA bridge-retirement authority.