Repository navigation
Conversation
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>
7f152b5 to
0cd90f0
Compare
jflowers
left a comment
There was a problem hiding this comment.
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).
| and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). | ||
|
|
||
| ## [Unreleased] | ||
|
|
There was a problem hiding this comment.
[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.
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
package.json, the lockfile,VERSION, the README status heading, and the version test pins.NOTICEautomatically, so the published package would have carried snake-eyes-derived code without the Apache-2.0 §4(d) attribution.!dist/**/*.map). The 34 maps pointed at../src/*.ts, which isn't published.homepage,bugs,keywords, and anexportsmap ("."→ the index barrel, plus./package.json).tests/cli.test.ts, both running against the builtdist/:npm pack --dry-run --json: NOTICE, LICENSE, README and the compiled surface are present; no.map,src/ortests/files. I checked that it fails when NOTICE is removed fromfiles.dist/main.jssession runsinitialize→discover→ all 7 analysis methods →shutdownover 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.CHANGELOG.md; README gets an npm-install section and a note on the exacttypescriptpin; AGENTS.md no longer claims v0.1.0 shipped.align-protocol-v1-2-0with--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.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
initializehandshake bytes are unchanged.Gates (from a clean
npm ci)npx biome check src/ tests/: passnpm run build: passnpx vitest run --coverage: 1,498 passed; coverage 95.06% statements, 89.86% branches, 97.91% functions, 95.05% linesConstitution 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)
[0.2.0]headingmain:npm publish --access publicgit tag -s v0.2.0, push the tag,gh release create v0.2.0 --verify-tagrelease-v0-2-0(syncs theclimain spec)release.yml🤖 Generated with Claude Code