Skip to content

Release v0.2.0: version bump, packaging fixes, full-lifecycle smoke test - #27

Draft
jflowers wants to merge 8 commits into
zero-dot-force:mainfrom
jflowers:release/v0.2.0
Draft

jflowers wants to merge 8 commits into
zero-dot-force:mainfrom
jflowers:release/v0.2.0

Conversation

@jflowers

@jflowers jflowers commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Release prep for v0.2.0, the first npm publication of reading-stone. Refs #7.

OpenSpec change: openspec/changes/release-v0-2-0/ (spec committed first, in 439c14a).

Changes

  • Version 0.1.0 → 0.2.0 in package.json, the lockfile, VERSION, the README status heading, and the version test pins.
  • NOTICE now ships in the tarball. npm doesn't include NOTICE automatically, so the published package would have carried snake-eyes-derived code without the Apache-2.0 §4(d) attribution.
  • Source maps excluded (!dist/**/*.map). The 34 maps pointed at ../src/*.ts, which isn't published.
  • Registry metadata: homepage, bugs, keywords, and an exports map ("." → the index barrel, plus ./package.json).
  • New tests in tests/cli.test.ts, both running against the built dist/:
    • Tarball contents via npm pack --dry-run --json: NOTICE, LICENSE, README and the compiled surface are present; no .map, src/ or tests/ files. I checked that it fails when NOTICE is removed from files.
    • Full-lifecycle stdio smoke test: one dist/main.js session runs initialize → discover → all 7 analysis methods → shutdown over a fixture project (with tsconfig and an Istanbul artifact). Every method must return a success with non-empty rows, and the process must exit 0.
  • Docs: new CHANGELOG.md; README gets an npm-install section and a note on the exact typescript pin; AGENTS.md no longer claims v0.1.0 shipped.
  • OpenSpec: archived align-protocol-v1-2-0 with --skip-specs. Its deltas were synced into the main specs at merge and 005 has changed those specs since, so re-applying them would roll back the capability scenarios.
  • OpenSpec: archived align-assertion-types (merged in fix: align test_mapping assertion_type with Gaze's assertion-type set #28) with --skip-specs; it amended spec 004 directly and has no deltas.

No runtime, protocol or dependency changes. The initialize handshake bytes are unchanged.

Gates (from a clean npm ci)

  • npx biome check src/ tests/: pass
  • npm run build: pass
  • npx vitest run --coverage: 1,498 passed; coverage 95.06% statements, 89.86% branches, 97.91% functions, 95.05% lines

Constitution check

I Protocol Fidelity PASS · II Detection Accuracy N/A · III TypeScript-Native N/A · IV Testability PASS · V Analysis Safety PASS (details in the proposal)

Before merge

  • uf.review-council: all reviewers APPROVE (opened as a draft until then)

After merge (maintainer)

  • Set the date on the CHANGELOG [0.2.0] heading
  • Publish manually from a clean main: npm publish --access public
  • git tag -s v0.2.0, push the tag, gh release create v0.2.0 --verify-tag
  • Archive release-v0-2-0 (syncs the cli main spec)
  • Follow-up: trusted publishing + release.yml

🤖 Generated with Claude Code

jflowers and others added 8 commits November 19, 2026 16:50
Proposal, design, tasks, and cli spec delta for the v0.2.0 release:
version bump, NOTICE in the tarball, source-map exclusion, registry
metadata, full-lifecycle stdio smoke test, CHANGELOG, and archiving
align-protocol-v1-2-0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… (release-v0-2-0 2.1, 2.2, 3.1)

npm does not auto-include NOTICE, so the tarball would have shipped
snake-eyes-derived code without the Apache-2.0 §4(d) attribution.
Source maps pointed at the unshipped src/ and are now excluded. Adds
homepage, bugs, keywords, and an exports map for the index barrel,
plus a tarball-contents test pinned via npm pack --dry-run --json.

Adds the issue zero-dot-force#7 end-to-end test: one dist/main.js session runs
initialize, discover, all seven analysis methods, and shutdown over a
fixture project, requiring a success and non-empty rows from each.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…v0-2-0 4.1, 4.2)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…5.1)

Archived with --skip-specs: its deltas were pre-synced into the main
specs at merge and 005 has since advanced the capability scenarios, so
re-applying them would regress the main spec.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…dot-force#28)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@jflowers jflowers left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Council Verdict: APPROVE WITH ADVISORIES

Reviewers: divisor-adversary, divisor-architect, divisor-curator, divisor-guard
Iterations: 1

Input: upstream/main@90255c9af861dfe2648e9ca39803b6438da17846...release/v0.2.0@0cd90f0

Council approved with advisories — unresolved HIGH/CRITICAL findings require human judgment before merge.

Dispatch Provenance

Run Agent Source Requested Resolved parent Reported
598f4013 divisor-adversary advisor Muse-Spark-Open-816B-A42B-NVFP4 — Muse-Spark-Open-816B-A42B-NVFP4 (match)
9ac55396 divisor-architect advisor Muse-Spark-Open-816B-A42B-NVFP4 — Muse-Spark-Open-816B-A42B-NVFP4 (match)
6de1b2f0 divisor-curator advisor Muse-Spark-Open-816B-A42B-NVFP4 — Muse-Spark-Open-816B-A42B-NVFP4 (match)
1ed54710 divisor-guard advisor Muse-Spark-Open-816B-A42B-NVFP4 — Muse-Spark-Open-816B-A42B-NVFP4 (match)
36827656 divisor-sre advisor DeepSeek-V4.1-Flash-1017 — zai-org/glm-5-3 (model mismatch; run failed, non-voting)

Divisor Adversary (APPROVE)

No findings.

Divisor Architect (APPROVE)

No findings.

Divisor Curator (APPROVE)

No findings.

Divisor Guard (APPROVE WITH ADVISORIES)

1 LOW finding omitted (see inline comment).


This review was generated by /uf.review-council (AI-assisted).

Comment thread CHANGELOG.md
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[LOW] The 0.2.0 changelog entry omits a Spec: traceability line. The entry cites issues #2–#6 but never points at openspec/changes/release-v0-2-0/, so release → spec linkage rests on the PR body alone. A line such as Spec: openspec/changes/release-v0-2-0/ under the entry restores the audit path. Advisory only — the entry's content itself is accurate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant