docs: file the post-0.3.0 entries under Unreleased - #4
Conversation
The cursor-save and environment-window entries landed after the 0.3.0 tag but were appended to the released section; move them back so the next release picks them up and 0.3.0's notes match its Release page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bb7b66908
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| of the whole machine every three seconds. A change now goes to the adapters | ||
| whose declared `watchRoots` contain it, about the one directory it happened | ||
| in. Nothing checked containment before, and `mightBeSessionFile` is a rule | ||
| re-seed. A refused save re-owes its paths, and the set is taken ang checked containment before, and `mightBeSessionFile` is a rule |
There was a problem hiding this comment.
Restore the accidentally spliced changelog entries
This line splices the post-release cursor-save paragraph into the middle of the 0.3.0 routed-discovery entry: the released section still contains half of the cursor-save note, while the complete eventSchemaVersion = 2 note and the routed-discovery heading and introduction have disappeared. Consequently the edit neither fully files the new work under [Unreleased] nor preserves the 0.3.0 notes; remove the complete cursor/environment entries from 0.3.0 and restore the intact schema-version and routing entries.
AGENTS.md reference: AGENTS.md:L174-L180
Useful? React with 👍 / 👎.
Entries from 7a80b48 / 7b15188 / f2f010d / 24ea09d were appended to the already-released
## [0.3.0]section. Move them to[Unreleased]so the next release picks them up and 0.3.0's notes keep matching its published Release.AgentSessionKitInfoTestsstill pins the version to the newest released section.