fix: missing optional Web modules must not abort agent startup

karsten commented

2026-11-13 02:32:25 +00:00

Owner

Peter had stale explicit frontend paths in BOTH settings.gatewayPlugins.webui.module and plugins[]. Removing the retired bundle exposed a fatal import on startup. Missing OPTIONAL Web entrypoints must disable only Web, retain config and continue other channels. Startup checks only absence of the configured entrypoint, not transitive imports or module activation/security errors. Live replacement requests and unrelated plugins remain strict. General plugin host receives explicit optional Web identity for custom paths and recognizes documented Web entrypoints. No config rewrite, arbitrary module fallback or permission downgrade.

Real CLI regression reaches readiness with BOTH stale configured paths; other-channel work continues. Existing Web module missing security dependency still fails closed. Build + full 2089 passed /1 skip /0 failures after integrating main #379; independent supplied-diff APPROVE. Peter restored to previous verified baseline meanwhile; current selected source is frontend-free but old baseline still supplies the stale configured module. New artifact removes that accidental dependency without reintroducing the frontend.

Fleet activation and restart continuation proof follow green CI. No installed-host full test gate.

Peter had stale explicit frontend paths in BOTH settings.gatewayPlugins.webui.module and plugins[]. Removing the retired bundle exposed a fatal import on startup. Missing OPTIONAL Web entrypoints must disable only Web, retain config and continue other channels. Startup checks only absence of the configured entrypoint, not transitive imports or module activation/security errors. Live replacement requests and unrelated plugins remain strict. General plugin host receives explicit optional Web identity for custom paths and recognizes documented Web entrypoints. No config rewrite, arbitrary module fallback or permission downgrade. Real CLI regression reaches readiness with BOTH stale configured paths; other-channel work continues. Existing Web module missing security dependency still fails closed. Build + full **2089 passed /1 skip /0 failures** after integrating main #379; independent supplied-diff APPROVE. Peter restored to previous verified baseline meanwhile; current selected source is frontend-free but old baseline still supplies the stale configured module. New artifact removes that accidental dependency without reintroducing the frontend. Fleet activation and restart continuation proof follow green CI. No installed-host full test gate.

karsten added 2 commits

2026-11-13 02:32:26 +00:00

fix: keep agent startup available when optional Web modules are absent 652dd92db0

Merge remote-tracking branch 'origin/main' into fix/optional-webui-missing-startup

decision-interface-ci / full-validation (pull_request) Successful in 2m35s

Details

489fd8e984

karsten merged commit 433dcb72c6 into main

2026-11-13 02:36:20 +00:00

karsten referenced this pull request from a commit

2026-11-13 02:36:21 +00:00

Merge pull request 'fix: missing optional Web modules must not abort agent startup' (#381) from fix/optional-webui-missing-startup into main

karsten commented

2026-11-13 04:29:38 +00:00

Author

Owner

Fleet activation is now actually verified for all13 active agents at ef740f5e34 (published container0.1.273, sha256:a728a04b09e84d92b02573465fce507c10314ac4c0bb99f5cc9ad43f71d22f28): five native +Grace/Minerva/Che/Kakashi/Minato through authenticated running APIs, Moist/Odo/Randy through actual /proc Node entrypoint resolving to immutable package CLI and same-root build metadata. All8 Kubernetes Deployments ready1/1; intentionally inactive broker remains0. Normal GitOps owner PRs; no task/state/config ledger surgery.

Behavioral evidence remains separate from version readiness: retained Shikamaru Matrix task automatically advanced7→11 with SDK tool receipts, uncancelled native worker overlap27.7196s, explicit stop still stopped/depth0/no pending after final restart. On final #387 revision, new live API probe run_b4c89ab6b2d243dc8ce17784bb5818f6 stores real parent final output including both accepted worker UUIDs, not started-status text; both read-only workers completed.

Persistent evidence index: /home/karsten/.local/share/hayate-lifecycle-work/FLEET-273-VERIFICATION.md; snapshot fleet-recovery-snapshot-1794543898.json. This proves fleet code activation and stated live cases, NOT that every retained task on every agent is presently runnable or that semantic/manual/legacy holds may be lifted.

Fleet activation is now actually verified for all13 active agents at ef740f5e345c (published container0.1.273, sha256:a728a04b09e84d92b02573465fce507c10314ac4c0bb99f5cc9ad43f71d22f28): five native +Grace/Minerva/Che/Kakashi/Minato through authenticated running APIs, Moist/Odo/Randy through actual /proc Node entrypoint resolving to immutable package CLI and same-root build metadata. All8 Kubernetes Deployments ready1/1; intentionally inactive broker remains0. Normal GitOps owner PRs; no task/state/config ledger surgery. Behavioral evidence remains separate from version readiness: retained Shikamaru Matrix task automatically advanced7→11 with SDK tool receipts, uncancelled native worker overlap27.7196s, explicit stop still stopped/depth0/no pending after final restart. On final #387 revision, new live API probe run_b4c89ab6b2d243dc8ce17784bb5818f6 stores real parent final output including both accepted worker UUIDs, not started-status text; both read-only workers completed. Persistent evidence index: /home/karsten/.local/share/hayate-lifecycle-work/FLEET-273-VERIFICATION.md; snapshot fleet-recovery-snapshot-1794543898.json. This proves fleet code activation and stated live cases, NOT that every retained task on every agent is presently runnable or that semantic/manual/legacy holds may be lifted.

Rows
Columns

fix: missing optional Web modules must not abort agent startup #381