coilyco-flight-deck/agentic-os

Watch

Close released AOS composition gaps for inbox#267 #763

New issue

Closed

opened 2026-07-27 04:41:52 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-27 04:41:52 +00:00

Member

Goal

Make the installed AOS package and default moving release image satisfy the cross-repository launch contract in inbox#267, then record acceptance evidence before the umbrella closes.

Verified behavior

A clean native Windows clone and current Scoop packages established this boundary:

aos and aosguard 0.100.0, Ward 0.817.0, agent-compose 0.63.0, and specgen 0.123.0 install successfully.
The AOS Go unit suite passes.
All seven supported combinations of --warded, --composed, and --guarded render successfully in release-CLI dry runs.
Unsupported Ward roles fail before launch.
A locally built AOS image completes the full composed and guarded bundle handoff to Ward when the full Forgejo issue URL is used.
The local image verifies 38 Engineer skills, projects the Codex home, attaches aosguard, and lets Ward render one read-only bundle mount under its own container lifecycle.
The standalone composed-plus-guarded path starts Codex successfully.
Current specgen rebuilds the AOS-specific binary and generated skill successfully.

Remaining gaps

The published agentic-os:release image is older than the installed AOS CLI. Its embedded aos rejects --warded, --composed, and --guarded, so the default released command fails before Ward starts.
The compact reference coilysiren/inbox#267 routes to GitHub and fails. The full Forgejo issue URL routes correctly. Ward owns tracker and clone authority, so AOS must link a Ward-owned routing fix or document and validate the explicit full-URL contract.
Canonical pre-commit validation is red. actions-run-one-line reports 14 workflow block scalars, the role-personality projection rejects the installed snapshot schema, and shellcheck sees CRLF in the image-crop helper. Forgejo Runner validation also cannot initialize reliably on native Windows.
Normal host pulls require convergence from the corrected credential-helper source before released-path retesting.

Required work

The engineer restores repository validation without weakening the hooks. Existing release work is tracked by #762, with the broken image path also related to #758.
The engineer files or links the Ward-owned compact-reference routing fix and adds cross-forge coverage.
The normal main-push pipeline publishes a current moving release image containing the integrated AOS flags, aosguard, generated skill, and compatible Ward and agent-compose inputs.
An Ops or director run observes the release pipeline and confirms the moving image and native AOS package are compatible. The engineer does not iterate against live CI.
The verifier runs the installed AOS command against the default image with the full Forgejo URL and the supported flag matrix, including at least one real standalone launch and one Ward --print launch.
The closeout evidence is linked on inbox#267 before that umbrella closes.

Acceptance

Current Scoop aos can use the default moving release image with --warded --composed --guarded.
The final Ward plan receives one verified read-only context bundle, aosguard, and the generated guarded skill.
Compact cross-forge issue input either routes correctly or fails before materialization with an explicit full-URL requirement.
All seven supported capability combinations pass release-path verification.
Unsupported combinations fail before Docker starts.
Repository validation and canonical CI pass without skipping required hooks.
The issue records the released versions and links the completion evidence to inbox#267.

## Goal Make the installed AOS package and default moving release image satisfy the cross-repository launch contract in [inbox#267](https://forgejo.coilysiren.me/coilysiren/inbox/issues/267), then record acceptance evidence before the umbrella closes. ## Verified behavior A clean native Windows clone and current Scoop packages established this boundary: * `aos` and `aosguard` 0.100.0, Ward 0.817.0, agent-compose 0.63.0, and specgen 0.123.0 install successfully. * The AOS Go unit suite passes. * All seven supported combinations of `--warded`, `--composed`, and `--guarded` render successfully in release-CLI dry runs. * Unsupported Ward roles fail before launch. * A locally built AOS image completes the full composed and guarded bundle handoff to Ward when the full Forgejo issue URL is used. * The local image verifies 38 Engineer skills, projects the Codex home, attaches `aosguard`, and lets Ward render one read-only bundle mount under its own container lifecycle. * The standalone composed-plus-guarded path starts Codex successfully. * Current specgen rebuilds the AOS-specific binary and generated skill successfully. ## Remaining gaps * The published `agentic-os:release` image is older than the installed AOS CLI. Its embedded `aos` rejects `--warded`, `--composed`, and `--guarded`, so the default released command fails before Ward starts. * The compact reference `coilysiren/inbox#267` routes to GitHub and fails. The full Forgejo issue URL routes correctly. Ward owns tracker and clone authority, so AOS must link a Ward-owned routing fix or document and validate the explicit full-URL contract. * Canonical pre-commit validation is red. `actions-run-one-line` reports 14 workflow block scalars, the role-personality projection rejects the installed snapshot schema, and shellcheck sees CRLF in the image-crop helper. Forgejo Runner validation also cannot initialize reliably on native Windows. * Normal host pulls require convergence from the corrected credential-helper source before released-path retesting. ## Required work 1. The engineer restores repository validation without weakening the hooks. Existing release work is tracked by #762, with the broken image path also related to #758. 2. The engineer files or links the Ward-owned compact-reference routing fix and adds cross-forge coverage. 3. The normal main-push pipeline publishes a current moving release image containing the integrated AOS flags, `aosguard`, generated skill, and compatible Ward and agent-compose inputs. 4. An Ops or director run observes the release pipeline and confirms the moving image and native AOS package are compatible. The engineer does not iterate against live CI. 5. The verifier runs the installed AOS command against the default image with the full Forgejo URL and the supported flag matrix, including at least one real standalone launch and one Ward `--print` launch. 6. The closeout evidence is linked on inbox#267 before that umbrella closes. ## Acceptance * Current Scoop `aos` can use the default moving release image with `--warded --composed --guarded`. * The final Ward plan receives one verified read-only context bundle, `aosguard`, and the generated guarded skill. * Compact cross-forge issue input either routes correctly or fails before materialization with an explicit full-URL requirement. * All seven supported capability combinations pass release-path verification. * Unsupported combinations fail before Docker starts. * Repository validation and canonical CI pass without skipping required hooks. * The issue records the released versions and links the completion evidence to inbox#267. ## Related * [inbox#267](https://forgejo.coilysiren.me/coilysiren/inbox/issues/267) * #758 * #762 * #747

coilyco-ops commented

2026-07-28 09:46:12 +00:00

Author

Member

2026-07-28 engineer checkpoint

The repository-owned implementation landed in commit ad06b3bb and the standalone CLI release completed as aos-v0.103.0.

Verified evidence

The canonical CI, AOS test, lint, build, and full pre-commit surfaces passed.
The promoted release branch built the expected commit-scoped draft dev-base image.
The draft image contains the new embedded AOS MCP inventory and tailnet forwarding support.
A real standalone composed Engineer launch against that draft projected 15 MCP servers and completed a read-only schema lookup through the tailnet proxy.
The current moving agentic-os:release image remains older. The installed aos-v0.103.0 host launcher passes the new internal --mcp-inventory flag, which the embedded release-image binary rejects before the harness starts.

Operator action

An Ops or director run must dispatch the documented manual release.yml workflow on the release ref with its normal defaults. The operator must then pull the moving agentic-os:release alias and repeat the standalone composed MCP schema lookup without an --image override.

Expected evidence: the moving release image accepts the internal MCP inventory flags, reports the projected MCP inventory, and completes the tailnet-backed read-only lookup. The engineer stops here because the remaining step is a live image promotion.

## 2026-07-28 engineer checkpoint The repository-owned implementation landed in commit `ad06b3bb` and the standalone CLI release completed as `aos-v0.103.0`. ### Verified evidence * The canonical CI, AOS test, lint, build, and full pre-commit surfaces passed. * The promoted `release` branch built the expected commit-scoped draft dev-base image. * The draft image contains the new embedded AOS MCP inventory and tailnet forwarding support. * A real standalone composed Engineer launch against that draft projected 15 MCP servers and completed a read-only schema lookup through the tailnet proxy. * The current moving `agentic-os:release` image remains older. The installed `aos-v0.103.0` host launcher passes the new internal `--mcp-inventory` flag, which the embedded release-image binary rejects before the harness starts. ### Operator action An Ops or director run must dispatch the documented manual `release.yml` workflow on the `release` ref with its normal defaults. The operator must then pull the moving `agentic-os:release` alias and repeat the standalone composed MCP schema lookup without an `--image` override. Expected evidence: the moving release image accepts the internal MCP inventory flags, reports the projected MCP inventory, and completes the tailnet-backed read-only lookup. The engineer stops here because the remaining step is a live image promotion.

coilyco-ops added the

autonomy

live-collab

label

2026-07-28 09:46:14 +00:00

coilyco-ops commented

2026-07-28 09:56:55 +00:00

Author

Member

2026-07-28 Ops promotion result

The documented manual release workflow completed successfully and published v0.259.0 from commit ad06b3bb.

After-state

The moving agentic-os:release arm64 manifest matches the previously verified commit-scoped draft.
A fresh pull of agentic-os:release contains the new embedded MCP inventory support.
The installed aos-v0.103.0 launcher and the moving release image are compatible.
A default standalone composed Engineer launch, with no image override, projected 15 MCP servers and completed a read-only schema lookup through the tailnet proxy.

The image-promotion checkpoint is complete. The issue remains open for its separate cross-forge routing and full capability-matrix acceptance items.

## 2026-07-28 Ops promotion result The documented manual release workflow completed successfully and published `v0.259.0` from commit `ad06b3bb`. ### After-state * The moving `agentic-os:release` arm64 manifest matches the previously verified commit-scoped draft. * A fresh pull of `agentic-os:release` contains the new embedded MCP inventory support. * The installed `aos-v0.103.0` launcher and the moving release image are compatible. * A default standalone composed Engineer launch, with no image override, projected 15 MCP servers and completed a read-only schema lookup through the tailnet proxy. The image-promotion checkpoint is complete. The issue remains open for its separate cross-forge routing and full capability-matrix acceptance items.

coilyco-ops referenced this issue

2026-07-29 03:24:00 +00:00

Adapt AOS to Ward's role and KDL removal #778

coilyco-ops added the

priority

label

2026-07-29 03:45:21 +00:00

coilyco-ops added

priority

and removed

priority

labels