[Brian Krabach (bkrabach)]

Proposed change

Add bundles/work-amp-dev.md: Work plus Foundation's portable amp-dev capability, not Anchors + Work. It composes Work's own root and amplifier-foundation@main#subdirectory=behaviors/amp-dev.yaml, retaining Work's loop/context defaults, provider neutrality and operating instruction.

Migration and trade-offs

• behaviors/work-local.yaml is now transcript-only and preserves both host runtimes. Existing consumers that relied on it to select managed context must use bundles/work-session.yaml or select a context manager in their complete root.
• bundles/work-session.yaml owns both loop-live and context-managed defaults. Applications may override them.
• Both Work roots explicitly load shared @work:context/system.md; the instruction was moved without changing its body.
• Work-first include order retains project/personal/Work skill precedence. List-valued configurations accumulate parent-first; the order is deliberate, not a byte-identical ordering claim.
• Bundle/module sources remain maintained @main references. Tested commits below are receipts, not pins. Runtime implementations remain in their module repositories; no application dependency or credentials were added.

Versions are bumped for the runtime-boundary migration: Work root 0.4.0, work-session 0.2.0, work-local 0.3.0; the new work-amp-dev root is 0.1.0.

Upstream publication gate satisfied

Foundation PR #439 is merged as ab87882027bc5cb3aa74a6f6de539560b2e4d264. Its complete tree matches reviewed candidate 7213f82; seven enumerated Anchors/amp-dev runtime-resource paths match CLI-qualified candidate 319a6dc. All six native post-merge CI jobs passed in run 37360793685 before this Work branch was published.

Foundation's squash preserves required linear history. This Work PR was subsequently merged after its own exact-head CI qualification and review of the outcomes.

Merged outcome

Merged by normal, head-fenced squash as 50deb9ebb4b9407401c45e624940effc93cfb107. No administrator bypass was available or necessary. The entire merged tree equals CI-tested candidate af8a257; the feature branch is retained.

Post-merge run 37363490243 passed on that exact merge commit: 93 passed, zero skipped in 56.03s. All composition-job steps passed. Its retained package evidence again identifies Foundation's Python library at ab87882 and core 2.0.1. All observed checks and triggered workflows for this commit completed successfully; no separate Dependency Graph run was observed. The package-versus-bundle provenance distinction below and validation-recipe FAIL/incomplete outcomes remain unchanged.

Observed verification

• Work candidate e9317ce2a9aa338d762f42e4346a47894bc1a07a: 93 passed, zero skipped in 48.43s, Linux Python 3.13 / core 2.0.1, using Foundation's Python library from a worktree at merge commit ab87882 via PYTHONPATH.
• A separate fresh registry resolved the exact maintained public GitHub Foundation behavior to merge commit ab87882, without candidate, mirror or local include overrides. Git hashes for seven runtime-resource paths matched the official CLI-qualified candidate. Application source-store/install overrides were removed only for qualification processes.
• Strict composition verifies Work runtime/provider/instruction preservation, four domain-capability agents with no Anchors runtime agents, namespace/expert resolution, skill precedence and app-owned runtime/provider overrides.
• Production prompt construction verifies Work's instruction and ecosystem context once, with expert spawn-only references. Module activation is mocked in that test; it is not a new provider run.
• Earlier isolated consuming-host acceptance used Work 0292a04 and Foundation 98f4f82: actual root response/expert spawn, authenticated trusted HTTPS, installed-resource provenance and browser conversation reload passed. Work's later changes are documentation only; those remain historical receipts rather than a new live run.
• The upstream official CLI gate independently passed 17 bounded checks for Foundation's flat and compatibility Anchors roots. No live model acceptance was replayed for documentation-only follow-ups.

The final prepublication follow-up af8a257a9809c5f3cdc6e7302fae99e9b93fe9f0 changes only docs/EXECUTION-VALIDATION.md relative to qualified candidate e9317ce, appending public-source qualification without rewriting historical results.

Exact-head PR CI

Run 37362645195 completed successfully on exact head af8a257a9809c5f3cdc6e7302fae99e9b93fe9f0: 93 passed, zero skipped in 54.38s. All composition-job steps passed, including LibreOffice installation, latest-source resolution, locked dependency installation and source-evidence upload.

The retained package-resolution artifact and installation log identify Foundation's Python library at ab87882027bc5cb3aa74a6f6de539560b2e4d264 and core 2.0.1, matching local qualification. This artifact captures Python package provenance, not the bundle graph. CI does not separately retain the Foundation bundle checkout SHA: its identity is inferred from successful unoverridden composition and public Foundation main remaining at the qualified revision during and after CI. The separate fresh-registry qualification above directly captured that bundle revision. These evidence levels are not interchangeable.

Two independent outcome reviews supported merging this exact head after fresh head/base/rule/check readback. Work required no administrator bypass; its merge used the normal head-fenced squash path. The original implementation 0292a04, documentation candidate e9317ce, and final head af8a257 remain historical lineage, not claimed ancestors of the squash commit. Post-merge CI subsequently passed, and both independent closure reviews supported reporting publication complete within the recorded verification limits. Validation-recipe FAIL/incomplete outcomes below are unchanged.

Validation-recipe limits

Full bundle and agent validation recipes were invoked on both repositories. Work has zero local agents (N/A, not coverage of composed external agents); its bundle analysis did not return a final report and cancellation was requested without a confirmed terminal record. Foundation's corrected bundle recipe reached FAIL, retaining context-budget and stale-source-resolution errors; composition timed out and build tools were unavailable. Its agent report synthesis was cancelled.

These results are retained and are not converted to PASS by deterministic tests or CI. No claim of complete host-release acceptance, Windows ACL qualification, or every validation recipe passing is made. See execution validation for candidate-specific evidence and limits.

Privacy and resource boundaries

No credentials, user settings, private transcripts, resource IDs, LAN addresses or raw live artifacts are included. No cleanup or unrelated upstream work is included.