# v0.9.0 local acceptance — 2026-09-08

This records the local implementation checkpoint on `codex/v0.9.0-agent-onboarding-doctor` as of 2026-09-08.
At that checkpoint the candidate was unreleased, with fresh Agent-host activation and Linux CI pending.
See the release follow-up below for the subsequent release scope.

## Verified

| Environment/check | Result |
| --- | --- |
| macOS arm64, Node 24.19.0 | Build; 200/200 unit tests; 12/12 real-listener smoke tests |
| macOS arm64, Node 22.17.0 | Build through smoke; 200/200 unit tests; 12/12 real-listener smoke tests |
| macOS arm64, Node 18.20.0 | 26/26 doctor tests and extracted-package lifecycle verification |
| Codex and Claude Code skill validation | Official Skill Creator validator passed, using PyYAML in an isolated temporary uv cache |
| npm consumer artifact | Version/help/doctor, all three copied adapters, health-gated detached startup, logs, service view, whois, cross-owner guards, dry-run preview and guarded stop passed |
| Package guide links | 37 local links checked in the extracted package; required doctor modules and adapter assets included |

The package consumer check ran under Node 24.19.0 and Node 18.20.0. Run it from this checkout with:

```bash
node scripts/verify-package.mjs /path/to/extracted/package
```

All mutable state, service projects and listeners were created for the tests. The doctor smoke asserts
registry bytes, modes, mtime and lock entries are unchanged and the live fixture still responds.
Unit coverage distinguishes unknown liveness from a confirmed dead run, exact stale age, concurrent file
replacement, missing/denied/timed-out/truncated scans, Linux PID-less sockets, skipped runtime clients,
privacy, project filtering and unsupported doctor options. Linux parser fixtures are not Linux runtime CI.

The existing Node engine requirement remains `>=18.17`. New implementation APIs are available on that
line; the installed Node 18 runtime tested here is 18.20.0, not the exact 18.17.0 floor.

## Host activation still to verify

| Host inspected | Observed version | Acceptance status |
| --- | --- | --- |
| Local Codex CLI | 0.45.0 | New-session skill discovery and environment continuity not tested |
| Local Claude Code CLI | 2.1.258 | New-session skill discovery and environment continuity not tested |
| Local Cursor launcher | 3.18.9, arm64 | Agent UI rule activation and conversation continuity not tested |

These versions come from each installed executable's version output. No agent-host model session was
launched for this acceptance run. Copying templates and running their CLI workflow does **not** prove
that each host loads the template or follows its instructions. Do not mark M3's activation gate complete
until a fresh session in each intended host provides actual loading and two-tool-call identity evidence.

The Claude automatic session-substitution bridge is not shipped. Claude/Cursor adapters preserve an
existing explicit owner and accurately document project-level fallback; no guessed host variables or
session hooks were added. Codex retains the existing automatic-ID resolver.

## Remaining release gates

- Fresh Codex, Claude Code and Cursor activation checks described above.
- Ubuntu/Linux build, full tests and smoke on Node 22 and 24 through the existing CI matrix.
- Release authorization, main CI, tag, npm OIDC/provenance and GitHub Release verification.

No remote branch push, tag, npm publication, GitHub Release, global package upgrade or Agent installation
was performed as part of local implementation. The acceptance report records local results, not a release.

## Release follow-up — 2026-09-20

The user requested publication of v0.9.0. The release retains the fresh-host activation limitation:
Codex, Claude Code and Cursor instruction loading and cross-tool-call identity have not been verified
in new host sessions. The shipped assets are manual onboarding templates; their presence and the
tested CLI lifecycle are not evidence of host activation. This limitation is also in the changelog.

Local build, 200 unit tests and 12 smoke tests passed again on macOS with Node 24.19.0. Release execution
must still pass the main Ubuntu/macOS × Node 22/24 CI matrix, followed by the tag-triggered npm OIDC
workflow and registry/provenance checks. Final execution evidence belongs to the
[v0.9.0 release](https://github.com/worsher/portmarshal/releases/tag/v0.9.0) and its linked workflow runs.
