diff --git a/CHANGELOG.md b/CHANGELOG.md index ea20546..45d3b5d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -31,8 +31,10 @@ with earlier [v0.1.4](docs/releases/v0.1.4.md) and [v0.1.3](docs/releases/v0.1.3 payloads out of the handoff. - Show standard input first for optional event capture. Use an authorized private scratch path for a file-backed payload. -- Checked with the repository static checks and packaged journal tests on - Python 3.9 and 3.14. These are source and helper checks. +- Checked with repository static, journal and site tests on Python 3.9 and + 3.14. An isolated install verified both packages in Codex and Claude Code + project layouts. See the [candidate notes](docs/releases/v0.2.8.md#candidate-checks) + for the scope and remaining publication steps. ## Experimental Antigravity support label — 2026-11-17 (no package release) diff --git a/docs/project-context.md b/docs/project-context.md index c05f048..4cd48cf 100644 --- a/docs/project-context.md +++ b/docs/project-context.md @@ -19,7 +19,7 @@ and evidence IDs when those records explain a project issue. ## Current focus -The unreleased core 0.2.8 source clarifies +The [unreleased v0.2.8 candidate](releases/v0.2.8.md) clarifies [shared-context writer handoff](../skills/context-docs/SKILL.md#make-the-smallest-useful-update) and [private journal payload delivery](../skills/context-docs/references/event-journal.md#capture-during-maintenance). The event helper and adoption skill keep their existing behavior. Published diff --git a/docs/releases/README.md b/docs/releases/README.md index e5fd87d..46d1b68 100644 --- a/docs/releases/README.md +++ b/docs/releases/README.md @@ -12,6 +12,8 @@ including an isolated skills.sh refresh and full page-content verification. ## v0.2.x +- **[v0.2.8 candidate](v0.2.8.md):** core 0.2.8 and adoption 0.1.16, + with isolated package checks and the publication steps still pending. - **[v0.2.7](v0.2.7.md):** [local preparation](v0.2.7-validation.json), [publication](v0.2.7-publication.json), [qualified simplification checks](../../evals/simplification/2026-10-26/README.md) diff --git a/docs/releases/v0.2.8.md b/docs/releases/v0.2.8.md new file mode 100644 index 0000000..258175e --- /dev/null +++ b/docs/releases/v0.2.8.md @@ -0,0 +1,47 @@ +# v0.2.8 candidate + +Prepared 21 November 2026 from source `9509321`. The candidate bundles +**Context Docs 0.2.8** and **Adopt Context Docs 0.1.16**. Everyday +installation still selects the published [v0.2.7 bundle](v0.2.7.md). + +## Changes + +- When Codex and Claude Code share a context file, agree on the current + writer and hand off ownership explicitly. Identify the checkout and + affected paths, release those paths before the next writer starts, and + reread the file before editing. Keep private context and journal payloads + out of the handoff. +- Send optional journal events through standard input. When a payload + needs a file, use an authorized private scratch path outside the + checkout and journal directory. +- Keep the site badge tied to the source release status. While core 0.2.8 + is unreleased, the site identifies it as such alongside the published + v0.2.7 install instructions. + +The bundle includes the existing +[adoption skill 0.1.16](../../skills/adopt-context-docs/SKILL.md). The +[usage guide](../getting-started.md) covers installation and upgrades for +existing projects. + +## Candidate checks + +An offline, project-scoped install with `skills 1.7.4` copied +both skills into the Codex and Claude Code project directories. All +16 tracked package files matched the candidate byte for byte in each +layout. The package versions were 0.2.8 and 0.1.16. The installed journal +helper appended a synthetic stdin event and read it back in each layout. +This checks packaging, local placement, and the journal helper. + +Repository static checks, the journal and site tests, and a local site +build passed. Runtime skill discovery and model behavior during a writer +handoff remain unverified. + +## Publication and upgrades + +Keep public install instructions on the published bundle until the new +tag is available. After publication is authorized, validate the exact release +commit, coordinate the install-pin switch, and follow the +[release checklist](../../CONTRIBUTING.md#release-checklist) for the separate +skills.sh refresh and page verification. Existing users can follow the +[upgrade guide](../getting-started.md#upgrading) when they choose to install +a published update.