docs: post-0.10.0 state refresh + http-client comment fix#95
Merged
stackbilt-admin merged 1 commit intomainfrom Apr 9, 2026
Merged
docs: post-0.10.0 state refresh + http-client comment fix#95stackbilt-admin merged 1 commit intomainfrom
stackbilt-admin merged 1 commit intomainfrom
Conversation
Two small drift-cleanup changes after the 0.10.0 publish: - .ai/state.adf — CURRENT was still v0.8.0 from the #50-53 era, had no mention of blast + surface or the npm publish milestone. Refreshed to reflect the current reality: 0.10.0 live on npm, #94/#90/#69 as the next queue, vendor-fix (#93) recorded in COMPLETED so the scaffold-response type-vendor context isn't lost. - packages/cli/src/http-client.ts — the ScaffoldFile doc comment said "sourced from @stackbilt/contracts" which is no longer accurate after #93. Updated to "vendored from @stackbilt/contracts" and pointed at the local types file for discoverability. No runtime behavior change. Sweep also confirmed the rest of the docs (README, CHANGELOG, PUBLISHING.md, per-package READMEs, docs/) are already 0.10.0-accurate from yesterday's pre-release docs audit.
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
1 participant
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.
Summary
Two small post-publish drift-cleanup changes:
`.ai/state.adf` — CURRENT still said v0.8.0 from the Feedback: bootstrap experience from Claude Code agent perspective #50-53 era. Refreshed to reflect 0.10.0 being live on npm, blast + surface subsystems shipped, blast: exclude .claude/worktrees/ from graph scanning (Claude Code ghost paths) #94/feat: package ecosystem — configurable dependency orchestration via charter config #90/feat: Typed Data Access & Disambiguation Policy — ontology enforcement across Stackbilt repos #69 as the active queue, and fix(cli): vendor scaffold-response types, unblock 0.10.0 publish #93 (vendor fix) in COMPLETED so the scaffold-response type-vendor rationale isn't lost to future agent context.
`packages/cli/src/http-client.ts` — the `ScaffoldFile` doc comment said "sourced from @stackbilt/contracts" which stopped being accurate after fix(cli): vendor scaffold-response types, unblock 0.10.0 publish #93 dropped that dep. Updated to "vendored from @stackbilt/contracts" and pointed at the local `./types/scaffold-contract-types` path for discoverability.
Scope
Doc-level only. No runtime behavior change. Pure text.
Sweep results
Full post-publish sweep across README.md, CHANGELOG.md, PUBLISHING.md, docs/, docs-snippets/, .ai/*.adf, and per-package READMEs. The rest of the docs are already 0.10.0-accurate thanks to yesterday's pre-release audit (commit 2525747). Only the two items above drifted.
Test plan
🤖 Generated with Claude Code