Follow-up to #637, which brought @bounded-systems/verbspec up to publish-ready packaging (metadata, dist build, LICENSE/README, extractability test, bin-name decoupling). The package is now a clean leaf — its only dependency is the zod peer dep — and the extractability test guards that it stays one.
This issue tracks the actual physical extraction out of the monorepo. The steps are atomic (you can't do later ones without the first), so they're a single checklist rather than separate issues:
Notes
@bounded-systems/cas is in the same posture — fully packaged but still in-tree — so whatever extraction recipe we settle on here should apply to both.- The richer verbspec projections currently live in
packages/prx/src/cli/; whether they follow verbspec out is tracked separately (see the companion "projections" issue).
Context: claude.ai/code session 01PGAut6CEjiQjFMURp8UA5A
Follow-up to #637, which brought
@bounded-systems/verbspecup to publish-ready packaging (metadata, dist build, LICENSE/README, extractability test,bin-name decoupling). The package is now a clean leaf — its only dependency is thezodpeer dep — and the extractability test guards that it stays one.This issue tracks the actual physical extraction out of the monorepo. The steps are atomic (you can't do later ones without the first), so they're a single checklist rather than separate issues:
github.com/bounded-systems/verbspecand movepackages/verbspec/into it (history-preserving).@bounded-systems/verbspecentry from the roottsconfig.jsonpathsmap.workspace:*to a real version range.0.1.0to the registry (npm/JSR), then verify prx resolves the published package.Notes
@bounded-systems/casis in the same posture — fully packaged but still in-tree — so whatever extraction recipe we settle on here should apply to both.packages/prx/src/cli/; whether they follow verbspec out is tracked separately (see the companion "projections" issue).Context: claude.ai/code session 01PGAut6CEjiQjFMURp8UA5A