Cut fallow-ts 0.1.0-alpha.2 identity #40

Merged

pdurlej merged 2 commits from codex/release-identity-alpha2 into main

2026-05-18 23:21:12 +02:00

codex commented

2026-05-18 18:51:07 +02:00

Collaborator

Canary Context Pack

Product story

Prepare the alpha release identity so the next forks can build distribution, CI, and adoption work against one explicit version instead of an open-ended Unreleased state.

What changed

Bumped package.json, package-lock.json, and runtime VERSION to 0.1.0-alpha.2.
Promoted current accumulated changelog entries from Unreleased to 0.1.0-alpha.2.
Added docs/release-notes/0.1.0-alpha.2.md with honest alpha scope and limitations.
Updated README and golden outputs that include the runtime version.
Added tests/release_identity.test.mjs to keep package/runtime/lockfile/changelog/release-notes aligned.

Why it changed

Fork A owns the Release Identity context. Other alpha-release forks need a stable version target before package distribution, CI, and adoption docs finish their own PRs.

Files touched

package.json
package-lock.json
src/types.ts
CHANGELOG.md
docs/release-notes/0.1.0-alpha.2.md
README.md
tests/golden/basic-report.json
tests/golden/basic-report.txt
tests/golden/basic-agent-context.md
tests/release_identity.test.mjs

Relevant context

This is Fork A from the parallel Alpha Release Train. It intentionally avoids package distribution logic, CI workflow changes, and analyzer changes.

Runtime evidence

npm run build
npm test — 33/33 passing
npm run pack:dry-run
npm run release:smoke
node dist/cli.js analyze --root . --format json --output /tmp/fallow-ts-report.json
node dist/cli.js analyze --root examples/demo-project --format text
git diff --check

Known constraints

0.1.0-alpha.2 is a release identity cut only. Publishing remains out of scope and must repeat npm name/ownership checks immediately before publish.

Coordination notes

This PR owns version/changelog/release-notes. Forks B-D should rebase onto this before finalizing package distribution, CI, or adoption wording that mentions the version.

Explicit out-of-scope

No npm publish, no npm dry-run publish script, no CI matrix changes, no parser/resolver/finding changes, no MCP.

Requested decision

Approve merge if the version identity and release notes are scoped correctly for alpha.

Merge blockers

Version mismatch across package/runtime/lockfile/docs/goldens, overclaiming release notes, or failing golden tests.

## Canary Context Pack ### Product story Prepare the alpha release identity so the next forks can build distribution, CI, and adoption work against one explicit version instead of an open-ended `Unreleased` state. ### What changed - Bumped `package.json`, `package-lock.json`, and runtime `VERSION` to `0.1.0-alpha.2`. - Promoted current accumulated changelog entries from `Unreleased` to `0.1.0-alpha.2`. - Added `docs/release-notes/0.1.0-alpha.2.md` with honest alpha scope and limitations. - Updated README and golden outputs that include the runtime version. - Added `tests/release_identity.test.mjs` to keep package/runtime/lockfile/changelog/release-notes aligned. ### Why it changed Fork A owns the Release Identity context. Other alpha-release forks need a stable version target before package distribution, CI, and adoption docs finish their own PRs. ### Files touched - `package.json` - `package-lock.json` - `src/types.ts` - `CHANGELOG.md` - `docs/release-notes/0.1.0-alpha.2.md` - `README.md` - `tests/golden/basic-report.json` - `tests/golden/basic-report.txt` - `tests/golden/basic-agent-context.md` - `tests/release_identity.test.mjs` ### Relevant context This is Fork A from the parallel Alpha Release Train. It intentionally avoids package distribution logic, CI workflow changes, and analyzer changes. ### Runtime evidence - `npm run build` - `npm test` — 33/33 passing - `npm run pack:dry-run` - `npm run release:smoke` - `node dist/cli.js analyze --root . --format json --output /tmp/fallow-ts-report.json` - `node dist/cli.js analyze --root examples/demo-project --format text` - `git diff --check` ### Known constraints `0.1.0-alpha.2` is a release identity cut only. Publishing remains out of scope and must repeat npm name/ownership checks immediately before publish. ### Coordination notes This PR owns version/changelog/release-notes. Forks B-D should rebase onto this before finalizing package distribution, CI, or adoption wording that mentions the version. ### Explicit out-of-scope No npm publish, no npm dry-run publish script, no CI matrix changes, no parser/resolver/finding changes, no MCP. ### Requested decision Approve merge if the version identity and release notes are scoped correctly for alpha. ### Merge blockers Version mismatch across package/runtime/lockfile/docs/goldens, overclaiming release notes, or failing golden tests.

codex added 1 commit

2026-05-18 18:51:07 +02:00

Cut fallow-ts 0.1.0-alpha.2 identity

CI / test (push) Failing after 15s

Details

CI / test (pull_request) Failing after 15s

Details

1fb6e8aeb4

Promotes the accumulated alpha work from Unreleased into 0.1.0-alpha.2, aligns package/runtime/lockfile/golden version references, and adds release notes plus an invariant test for future version cuts.

Verified:

- npm run build

- npm test

- npm run pack:dry-run

- npm run release:smoke

- node dist/cli.js analyze --root . --format json --output /tmp/fallow-ts-report.json

- node dist/cli.js analyze --root examples/demo-project --format text

- git diff --check

codex requested review from claude

2026-05-18 18:51:13 +02:00

codex referenced this pull request

2026-05-18 18:54:49 +02:00

Harden npm package distribution proof #43

codex referenced this pull request

2026-05-18 23:12:29 +02:00

Make per-file IO error test deterministic #44

codex added 1 commit

2026-05-18 23:18:07 +02:00

Merge remote-tracking branch 'origin/main' into codex/release-identity-alpha2

CI / test (push) Successful in 16s