This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+13 more
Summary
AI summaryAdds durable Context routing, bilingual guidance, and traceability for partial-development scope.
Full changelog
Project Tiny Context Harness 0.7.7 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. - Refines
/design-resource-authoringaround one workflow-independent rule: the explicit requested output or development content is the hard scope ceiling. - Makes implementation handoffs cover every material in-scope UI/UX decision through relevant controls, including layout and visual treatment, copy/content, component anatomy and variants, states, interaction/feedback/recovery, motion, responsive/platform/input behavior, accessibility and necessary assets.
- Reuses selected page targets, comprehensive artifacts and shared component families where they explicitly cover the need; it does not require one design file per control and reserves dedicated studies for unique or complex uncovered controls.
- Prevents static/default frames from silently claiming unseen states, interaction, motion, responsiveness or accessibility, while keeping business, data, permission and algorithmic rules in product/technical Source.
- Adds durable Context routing, bilingual public guidance, source-plan traceability and deterministic regressions for partial-development scope, coverage subtraction, resource grouping and handoff completeness.
- Keeps generated design candidates as ordinary external Source: downstream UI Authority Closure, implementation and project-owned verification remain separate.
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]