You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Draft scope note:**This release note draft is pinned to the committed range **`v0.4.0..e91cacd0`**. Newer unstaged local edits were intentionally excluded from the `v0.4.1`candidate.
12
+
**Shipped scope:**Git tag **`v0.4.1`** is at **`8081ee5`** (`Release v0.4.1: incremental deploy (marketing site)`). Narrative and `release-notes:render --tag v0.4.1`use range **`v0.4.0..v0.4.1`**.
13
13
14
-
Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery path for local installs, improves MCP/CLI contract parity around entity counts, and continues the evaluation-first site refresh with clearer product positioning, install guidance, and homepage demos.
14
+
**Post-tag `dev` (not in the `v0.4.1` tag):**`5258b9f3` — `fix(site): keep record-types headline tail on one line`. Ship as **`v0.4.2`** (or cherry-pick) if that fix should ride with npm/GitHub users on the same semver.
15
+
16
+
Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery path for local installs, improves MCP/CLI contract parity around entity counts, ships FU-301 marketing-site refresh with incremental Pages deploy, syncs foundation commands into Claude Code skills, adds the `writ` submodule for WRIT benchmarking, and continues the evaluation-first site refresh with clearer product positioning, install guidance, and homepage demos.
15
17
16
18
## What changed for npm package users
17
19
@@ -45,13 +47,16 @@ Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery
45
47
46
48
## Docs site & CI / tooling
47
49
50
+
-**FU-301:** Marketing site refresh, SEO, and v0.4.1 prep docs; **incremental GitHub Pages deploy** for the marketing site (`Release v0.4.1: incremental deploy`).
48
51
- Refreshed public positioning, ICP, and release-targeting material across `docs/foundation/`, `docs/icp/`, and homepage design guidance.
49
52
- Expanded the `evaluate_positioning` skill and related reference material so release prep, positioning review, and site iteration share the same framework.
50
53
- Kept site coverage current with Playwright updates for hash navigation and other homepage regressions, plus ongoing route/SEO/localization maintenance in the frontend site layer.
51
54
52
55
## Internal changes
53
56
54
57
- Renamed the canonical release command to `/release` while keeping `/create_release` as a legacy alias, and updated synced command/rule/skill copies accordingly.
58
+
- Emit foundation commands as **Claude Code skills** (`.claude/skills/<name>/SKILL.md`), with Cursor skill sync when not sourced from foundation.
- Synced generated Cursor/Claude instruction surfaces with the updated release workflow, positioning material, and rule set.
56
61
- Added the focused test-only transport behavior in `src/cli/index.ts` to remove flaky per-command local transport startup during CLI test runs.
57
62
@@ -65,16 +70,23 @@ Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery
65
70
66
71
- The committed `v0.4.1` candidate passed the full pre-commit gate used during release prep: `tsc --noEmit`, `eslint src --ext .ts`, `npm run lint:site-copy`, `npm test`, `npm run test:e2e`, `npm run validate:coverage`, `npm run check:pw-coverage`, and `npm run validate:doc-deps`.
67
72
- Release prep also included focused reruns of the previously failing CLI correction test and the homepage hash-update Playwright test after the fixes landed.
68
-
-Before publishing the actual GitHub Release, re-render notes after the final `v0.4.1`tag exists so the compare link and commit list reflect the exact tagged commit.
73
+
-The `v0.4.1` tag exists on `8081ee5`; re-run `npm run -s release-notes:render -- --tag v0.4.1`after any tag movement before publishing or editing the GitHub Release.
Copy file name to clipboardExpand all lines: docs/releases/in_progress/v0.4.1/github_release_supplement.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
-
**Draft scope note:**This release note draft is pinned to the committed range **`v0.4.0..e91cacd0`**. Newer unstaged local edits were intentionally excluded from the `v0.4.1`candidate.
1
+
**Shipped scope:**Git tag **`v0.4.1`** is at **`8081ee5`** (`Release v0.4.1: incremental deploy (marketing site)`). Narrative and `release-notes:render --tag v0.4.1`use range **`v0.4.0..v0.4.1`**.
2
2
3
-
Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery path for local installs, improves MCP/CLI contract parity around entity counts, and continues the evaluation-first site refresh with clearer product positioning, install guidance, and homepage demos.
3
+
**Post-tag `dev` (not in the `v0.4.1` tag):**`5258b9f3` — `fix(site): keep record-types headline tail on one line`. Ship as **`v0.4.2`** (or cherry-pick) if that fix should ride with npm/GitHub users on the same semver.
4
+
5
+
Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery path for local installs, improves MCP/CLI contract parity around entity counts, ships FU-301 marketing-site refresh with incremental Pages deploy, syncs foundation commands into Claude Code skills, adds the `writ` submodule for WRIT benchmarking, and continues the evaluation-first site refresh with clearer product positioning, install guidance, and homepage demos.
4
6
5
7
## What changed for npm package users
6
8
@@ -34,13 +36,16 @@ Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery
34
36
35
37
## Docs site & CI / tooling
36
38
39
+
-**FU-301:** Marketing site refresh, SEO, and v0.4.1 prep docs; **incremental GitHub Pages deploy** for the marketing site (`Release v0.4.1: incremental deploy`).
37
40
- Refreshed public positioning, ICP, and release-targeting material across `docs/foundation/`, `docs/icp/`, and homepage design guidance.
38
41
- Expanded the `evaluate_positioning` skill and related reference material so release prep, positioning review, and site iteration share the same framework.
39
42
- Kept site coverage current with Playwright updates for hash navigation and other homepage regressions, plus ongoing route/SEO/localization maintenance in the frontend site layer.
40
43
41
44
## Internal changes
42
45
43
46
- Renamed the canonical release command to `/release` while keeping `/create_release` as a legacy alias, and updated synced command/rule/skill copies accordingly.
47
+
- Emit foundation commands as **Claude Code skills** (`.claude/skills/<name>/SKILL.md`), with Cursor skill sync when not sourced from foundation.
- Synced generated Cursor/Claude instruction surfaces with the updated release workflow, positioning material, and rule set.
45
50
- Added the focused test-only transport behavior in `src/cli/index.ts` to remove flaky per-command local transport startup during CLI test runs.
46
51
@@ -54,7 +59,7 @@ Neotoma `0.4.1` tightens the release-prep workflow, adds a safer SQLite recovery
54
59
55
60
- The committed `v0.4.1` candidate passed the full pre-commit gate used during release prep: `tsc --noEmit`, `eslint src --ext .ts`, `npm run lint:site-copy`, `npm test`, `npm run test:e2e`, `npm run validate:coverage`, `npm run check:pw-coverage`, and `npm run validate:doc-deps`.
56
61
- Release prep also included focused reruns of the previously failing CLI correction test and the homepage hash-update Playwright test after the fixes landed.
57
-
-Before publishing the actual GitHub Release, re-render notes after the final `v0.4.1`tag exists so the compare link and commit list reflect the exact tagged commit.
62
+
-The `v0.4.1` tag exists on `8081ee5`; re-run `npm run -s release-notes:render -- --tag v0.4.1`after any tag movement before publishing or editing the GitHub Release.
0 commit comments