diff --git a/.agents-docs/AGENTS-code-style.md b/.agents-docs/AGENTS-code-style.md index 32d7a1e..a066245 100644 --- a/.agents-docs/AGENTS-code-style.md +++ b/.agents-docs/AGENTS-code-style.md @@ -13,7 +13,7 @@ ## Gotchas / Pitfalls -- **Version sync:** When adding a new version to `CHANGELOG.md`, also update `version.json` and `package.json` (root) to match. `README.md` and `docs/index.html` (footer `Version X.Y.Z`) also carry the version. `version.json` is copied into every skill's `references/web-console/` (the console's Help shows it), so after a bump run `npm run build:skills` or `npm test` (`--verify-skills`) fails. The installer displays the version from `version.json` in its header. All three files (`CHANGELOG.md`, `version.json`, `package.json`) must always show the same version number. +- **Version sync:** When adding a new version to `CHANGELOG.md`, also update `version.json` and `package.json` (root) to match. `README.md` (the `Version X.Y.Z` line near the top) also carries the version, and `version.json`'s `releaseDate` moves with it. `version.json` is copied into every skill's `references/web-console/` (the console's Help shows it), so after a bump run `npm run build:skills` or `npm test` (`--verify-skills`) fails. The installer displays the version from `version.json` in its header. All three files (`CHANGELOG.md`, `version.json`, `package.json`) must always show the same version number. - **CHANGELOG ordering:** Entries in `CHANGELOG.md` must be in reverse-chronological order โ€” newest version at the top, oldest at the bottom. New entries are always inserted immediately after the file header. - **CHANGELOG house format is not Keep a Changelog:** version headings are `## vX.Y.Z` โ€” with a `v` prefix and **no date**. The release date is recorded only in `version.json`'s `releaseDate`. Category headings carry emoji: `### โœจ Added`, `### ๐Ÿ”ง Changed`, `### ๐Ÿ› Fixed`, `### ๐Ÿ’ฅ Breaking`, `### ๐Ÿ—‘๏ธ Removed`, `### ๐Ÿ“š Documentation`. Older entries contain one-off variants (`๐ŸŽ Added`, `๐Ÿ“ฆ Updated`, `๐Ÿ“ Documentation`, `๐ŸŽ๏ธ Improved`, `๐Ÿงช Testing`) โ€” do not introduce new ones. The `.claude/skills/plan2code-changelog/` skill automates version selection and formatting; use it rather than hand-rolling an entry. - **PowerShell mangles the CHANGELOG emoji:** `Get-Content` / `Select-String` render the `###` heading emoji as `?` under the default Windows console encoding, so a heading audit done that way reports garbage. Read `CHANGELOG.md` with a file-read or grep tool instead. diff --git a/AGENTS.md b/AGENTS.md index 372c61d..9756d6a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -103,3 +103,4 @@ When you make a mistake, get corrected, or discover something about this codebas - Before deleting a test file that upstream split or removed, diff plan2code's copy against the rebranded upstream base and port the plan2code-only tests: v2.7.0's split of the web console suite would otherwise have dropped seven hardening tests (now in `scripts/test-web-console-hardening.mjs`). - Register a new skill in `install.js` `SOURCE_PROMPTS` before running its `scripts/test-script-.mjs`: importing `scripts/skill-script-helpers.mjs` rebuilds `skills/` and prunes any skill folder `install.js` does not list, so the script under test vanishes. - When you move a dashboard card, update every test that pins `SKILL_CATALOG` order (`scripts/test-web-console-source.mjs` and `scripts/test-web-console-git.mjs`): the Handoff move once updated only one and left `npm test` red. +- When a `CHANGELOG.md` heading gets a version number, set the same number in `version.json` (with its `releaseDate`), the root `package.json` and README's `Version X.Y.Z` line in the same change, then run `npm run build:skills`. The changelog skill only touches `package.json`: v2.9.0 nearly shipped with `version.json` at 2.8.1, and README's line sat at 2.6.0 for three releases. diff --git a/CHANGELOG.md b/CHANGELOG.md index 224f84f..bcf9bd1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ All notable changes to Plan2Code will be documented in this file. -## Unreleased +## v2.9.0 ### โœจ Added diff --git a/README.md b/README.md index 292d84d..2867e44 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ the next engineer all start from the same specs. One command opens it, every step is a card, and the terminal is always there if you prefer it. -Version 2.6.0 ยท MIT ยท ๐Ÿ“– [plan2code.jparkerweb.com](https://plan2code.jparkerweb.com) +Version 2.9.0 ยท MIT ยท ๐Ÿ“– [plan2code.jparkerweb.com](https://plan2code.jparkerweb.com) --- diff --git a/package.json b/package.json index 1874ca8..1b517ea 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "plan2code", - "version": "2.8.1", + "version": "2.9.0", "private": true, "bin": { "plan2code-install": "./install.js" diff --git a/version.json b/version.json index 4a6432f..a2b7b5b 100644 --- a/version.json +++ b/version.json @@ -1,6 +1,6 @@ { "name": "Plan2Code", - "version": "2.8.1", + "version": "2.9.0", "description": "A structured 4-step workflow methodology for AI-assisted software development", "keywords": [ "ai", @@ -17,6 +17,6 @@ "url": "https://github.com/jparkerweb/plan2code" }, "homepage": "https://github.com/jparkerweb/plan2code", - "releaseDate": "2026-10-14", + "releaseDate": "2026-10-17", "mode": "utility" }