[gael-obin]

Local hosted frontend changes could remain stale or recover with the wrong installed dependency contents. This preserves the existing controller, delivery and staging mechanisms while watching frontend sources, serializing delivery, scoping recovery, and tracking the actual successful installation separately from the retained bundle.

Classification: fix at the CLI lifecycle/build owner. The installation digest covers manifests, locks, npm configuration, tarballs and local directory package contents. Failed or interrupted installations lose their marker; reverting dependencies after failed build/retention does not reuse a stale installation. Source-only edits can reuse installed dependencies.

This is the 26-file additional delta from the locally exercised v2 controller source, over current main 43b05672. It excludes the stray .orig backup and the three setup files already in setup delivery. The selected local cohort also needs Core setup, native loopback mapping, and the linked Core watcher PR. New main's service-secret changes are preserved.

Validation retained from the exact selected cohort: real npm regression tests with/without locks, source-only reuse, failure/revert/cancellation cases; go test -race for pkg/solutionrun, cmd/run and pkg/engine; CLI build; actual persistent controller use. All 1,904 source hashes were rechecked. These are prior combined-cohort results, not a clean current-main CI pass.

Merge/release qualification remains blocked until compatible dependency pins and current combined checks are qualified. Hosted delivery work overlaps the npm build-command line and docs but does not replace installation identity/watch lifecycle. Preserve and reconcile it. Process-wide launch attribution for concurrent embedded hosts remains a documented limitation; automatic recovery is not a universal concurrency guarantee.

Shared watcher implementation: Core recovery.

Initial bootstrap CI fails because the committed Core dependency does not yet provide code.WatchTree. Adopt a qualified release containing the watcher owner change, then rerun. Local workspace testing is not a substitute for that published dependency.

CI and review follow-up

Opened for review at the author’s request. Removing draft status does not certify merge or release readiness. This follow-up inspected the published head and logs; it made no implementation changes and did not rerun tests.

Compilation fails because the committed Core dependency lacks code.WatchTree, the new NewWatcher signature, and Change.Err. Native qualification, generation, bootstrap and lint logs confirm the API mismatch; cancelled suites are unqualified. The Core watcher PR must be qualified and adopted through a compatible dependency selection before these checks can pass.

No submitted GitHub reviews, inline review comments, or conversation comments were present in the captured state. Independent publication/status audits are scoped evidence, not owner approval.

Failed jobs inspected:

• Container recovery native qualification / native (go, service-go, c77770bcfad2478a8add9890f102a92f8000586d)
• Go CLI / bootstrap-audit
• Container recovery native qualification / native (go-grpc, service-go-grpc, 84345bd4d21de20b5c9d9592458c19ef75d0afc7)
• Container recovery native qualification / native (rust, service-rust, 14ca465eb7ac78400497e8f6475b84f3f01ed587)
• Container recovery native qualification / native (nextjs, service-nextjs, 0f2173300c398be19358993770e273d929b40c23)
• Container recovery native qualification / native (python-fastapi, service-python-fastapi, 39395b622febe9630098abe82ba79ad736f00fb7)
• Docker generate qualification / generate (0)
• Go CLI / lint
• Docker generate qualification / generate (1)
• Docker generate qualification / generate (2)
• Docker generate qualification / docker-generate