This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+13 more
Summary
AI summaryAdds explicit-only /design-system-authoring cold-start flow and new release update modes.
Full changelog
Project Tiny Context Harness 0.8.0 is the current public release line under the renamed npm package:
npm install -D project-tiny-context-harness@latest
npx --yes --package project-tiny-context-harness@latest ty-context init
make validate-context
Update mode: sync-only. After updating the package, run:
npx --yes --package project-tiny-context-harness@latest ty-context upgrade --check
npx --yes --package project-tiny-context-harness@latest ty-context upgrade
This release mode means no new release migration is expected. Direct sync is an allowed shortcut only when you explicitly want managed-asset refresh without upgrade diagnostics:
npx --yes --package project-tiny-context-harness@latest ty-context sync
Sync does not run migrations. Upgrade plans report safe_pending, manual_required and blocked.
Publishing a new npm version does not automatically migrate existing repositories. Users receive new upgrade behavior only when they run the newly published CLI through ty-context upgrade, ty-context sync or another @latest package invocation.
What Changed
- Publishes
[email protected]with the synchronized package assets and CLI build. - Keeps the install path on the renamed package:
project-tiny-context-harness. - Adds the explicit-only
/design-system-authoringcold-start flow for generating, selecting and adopting Open Design systems into canonical project Design Authority. - Gates only style-bearing
/design-resource-authoringwork on configured Design Authority, verifies Open Design project binding, and reconciles accepted final decisions into the initial proposal once. - Sends revised proposals and selected resources directly into
/long-task-workflow's Source-bound Contract Draft loop; Source completeness and Contract mapping converge there without an internal Source-authoring stage, while/source-plan-authoringremains only a retired compatibility pointer. - Keeps the authority boundary explicit: provider candidates and bindings are provenance, while
DESIGN.md, its one authored token source and owningproject_context/**remain canonical. - Makes package updates explicit through release update modes:
sync-only,upgrade-required,manual-required.
Boundary
This release does not claim benchmark-proven speedups, production adoption, awards, or replacement of tests, CI, review, specs or project management. It packages the smaller recovery surface: keep the memory, drop the ceremony.
Useful Links
- npm: https://www.npmjs.com/package/project-tiny-context-harness
- README: https://github.com/Seven128/project-tiny-context-harness#readme
- Fresh-agent recovery walkthrough: https://github.com/Seven128/project-tiny-context-harness/blob/main/docs/examples/fresh-agent-recovery.md
- Minimal Context sample: https://github.com/Seven128/project-tiny-context-harness/blob/main/docs/examples/minimal-context-sample.md
- Comparison guide: https://github.com/Seven128/project-tiny-context-harness/blob/main/docs/comparison.md
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Project Tiny Context Harness
All releases →Beta — feedback welcome: [email protected]