release: 0.16.0 - #120
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.16.0 — the field-test round. Four issues found by re-running the full 7-phase deepseek-harness analysis through the published 0.15.0 binary (#111–#114), fixed in #115–#119. Version bumped in all four pinned surfaces (package.json, package-lock.json, server.json ×2, scaffold-version.yaml); release-metadata tests green (341/341).
Local verification
npm test: 341 pass / 0 failnpm run build: cleannode scripts/smoke-mcp.mjs --tarball codecartographer-pi-0.16.0.tgz: 9/9 okSurface verification (per CONTRIBUTING — actual returns, not checkboxes)
Full round-trip through the MCP SDK stdio client against the packed 0.16.0 tarball (init → validate → complete → status → amend → status → guide), exercising every change in this release:
Reading the evidence against the four issues:
DECISIONS.md heading check — heading line index: 86; row under it: D001 | …— the heading is a real line with the appended row beneath it.Dashboard refreshed: .codecarto/dashboard.htmlon bothcodecarto_completeandcodecarto_amend.codecarto_guide topic=libraryserves the new topic.codecarto_statusrenders the full routing — skills line,1 open question(s) and 0 post-pipeline item(s) remain — apply resolutions with codecarto_amend…with live counts, dashboard/usage line — and after the amendment closes the question, the amend line drops from both stored state and the text view.After merge: tag
v0.16.0on the merge commit → CI publishes (npm + MCP Registry + GitHub Release) → verify by re-downloading the published tarball.🤖 Generated with Claude Code