Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/backlog.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,5 +49,5 @@ derives its common backlog from [backlog-sources.json](backlog-sources.json).
| PC-41 | Release 0.2.5: Fabric Agent Adapter `v0.33.0` (contexts in the estate kits, DEC-0082; adapter FAA-41, FAA-43) | done 2026-10-15 — 0.2.5 published: PR #101 (merge `86c412f`), release run [38672767092](https://github.com/passioncode-ai/passioncode/actions/runs/38672767092), npm 0.2.5; the local install updated and its `fabric-agent-adapter` plugin is byte-identical to v0.33.0 (71 files) | [adapter v0.33.0](https://github.com/passioncode-ai/fabric-agent-adapter/releases/tag/v0.33.0) |
| PC-42 | Release 0.2.6: Fabric Agent Adapter `v0.34.0` (a lane that reads user content, DEC-0083; adapter FAA-45) | done 2026-10-15 — 0.2.6 published: PR #103 (merge `a05c926`), release run [38727644750](https://github.com/passioncode-ai/passioncode/actions/runs/38727644750), npm 0.2.6; the local install updated and its `fabric-agent-adapter` plugin is byte-identical to v0.34.0 (71 files) | [adapter v0.34.0](https://github.com/passioncode-ai/fabric-agent-adapter/releases/tag/v0.34.0) |
| PC-43 | Release 0.2.7: Fabric Agent Adapter `v0.34.1` (profile and route rules total on any JSON; adapter FAA-47) | open 2026-10-15: requested by the adapter release of FAA-47 | [adapter v0.34.1](https://github.com/passioncode-ai/fabric-agent-adapter/releases/tag/v0.34.1) |
| PC-44 | Release 0.2.8: Fabric Agent Adapter `v0.35.0` (native host hooks and verification tools) | in progress 2026-10-16: release checks and PR preparation; merge/tag waits for adapter publication confirmation | [handoff](handoffs/2026-10-16-adapter-0.35.0.md) |
| PC-44 | Release 0.2.8: Fabric Agent Adapter `v0.35.0` (native host hooks and verification tools) | done 2026-10-16: PR #106 merged as `89a050d`, tag `v0.2.8`, release workflow 38968387016 succeeded, npm 0.2.8 tarball served and integrity verified; installed native-hook acceptance belongs to the adapter integration run | [release receipt](handoffs/2026-10-16-adapter-0.35.0.md#published-release-receipt) |
| PC-45 | Reconcile the existing CLI help copy registry and declared brand surfaces | open 2026-10-16: optional brand lint found three B021 errors and five B022 warnings in unchanged files; no release-runtime regression | [evidence](handoffs/2026-10-16-adapter-0.35.0.md#checks-and-receipt) |
41 changes: 33 additions & 8 deletions docs/handoffs/2026-10-16-adapter-0.35.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,8 @@ Packed smoke integrity:
`sha512-jaCV5wo1skdt5K/D/4Gz4RMqjuqA8DiBi/vI/d8MrQDR1NW4SzY77w1Tzr986VQO9QVgUBNUyd9klkwIk6KoAw==`.
This is a local archive receipt, not an npm publication receipt. Packed smoke
uses a fake Claude CLI and does not prove host-native hook execution.
Hosted validation has not been dispatched; publication and installation are open.
At candidate preparation, hosted validation was not manually dispatched and
publication and installation were open. The final publication receipt is below.

Optional brand lint (`brand_lint.py docs/brand` from super-ux 0.59.3) returned
exit 2: three B021 stale help registry entries and five B022 unregistered strings.
Expand All @@ -68,15 +69,39 @@ automatic host-activation claim. Humanization: on, own pass, wording unchanged.
Lesson: a package pin and packed install receipt prove distribution; native host
acceptance and global installation require the adapter's separate receipts.

## Next task and wait
## Published release receipt

Source commit `084ddb9476374eb81d665bb143a1bd7c6a00e819` was pushed and verified
against the remote branch. [PR #106](https://github.com/passioncode-ai/passioncode/pull/106)
contains the reviewed release candidate and this receipt.

Wait for the integrating adapter owner to
confirm `v0.35.0` publication before merging or tagging launcher `v0.2.8`.
Watcher: the active integrating release session; fallback is this handoff.
After publication, verify the exact dependency tag, land the checked launcher
commit, run the release workflow, verify npm metadata and tarball integrity,
update the installation, and close PC-44 with receipts.
The adapter dependency gate cleared: its
[release workflow](https://github.com/passioncode-ai/fabric-agent-adapter/actions/runs/38967232797)
completed successfully and `npm view @passioncode-ai/fabric-agent-adapter@0.35.0 version`
returned `0.35.0`. The launcher PR's two final hosted `node` checks passed.

- [PR #106](https://github.com/passioncode-ai/passioncode/pull/106) merged at
`89a050d89f306d457f12b730156fa9f7ef286bd1`, 2026-10-16T21:17:30Z. The merge tree
has no diff from the checked candidate. Tag `v0.2.8` peels to that commit;
the remote tag and `origin/main` were verified before release.
- [GitHub release v0.2.8](https://github.com/passioncode-ai/passioncode/releases/tag/v0.2.8)
was published at 2026-10-16T21:18:37Z.
- [Release workflow 38968387016](https://github.com/passioncode-ai/passioncode/actions/runs/38968387016)
completed successfully: validation, GitHub release and npm publication.
- `node scripts/check-registry.mjs @passioncode-ai/passioncode 0.2.8` returned
exit 0, `served and verified`, 554785 bytes. Published archive integrity:
`sha512-c6zGTFCxW5WAmY+wrxD2FIDj/wiioNPgIRk6uwMI01Kfv5BrmzxDJ/YG88KZ0RiuiScVfJYlaeUkUqvJjP+Jwg==`.
The archive was downloaded from the canonical npm tarball URL and checked
against npm metadata; it is distinct from the earlier local packed-smoke archive.

PC-44's distribution release is complete. All guarded-file leases are released
after the receipt branch is pushed. No launcher runtime files changed after the
release gate; this follow-up records publication evidence.

## Exact next task

The integrating adapter session owns global update, native hook activation and
installed-byte acceptance. This launcher task does not claim those checks from
publication. Its published receipt has been sent to the knowledge-base integrator
for version propagation. Existing copy-registry drift remains PC-45 for the next
maintenance iteration. There is no pending launcher publication wait.
Loading