This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+13 more
Summary
AI summaryIntroduces stateless long‑task diagnosis and explicit release update modes.
Full changelog
Project Tiny Context Harness 0.7.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. - Adds stateless
ty-context long-task diagnose-revisionfeedback for scope-only Authority Revision candidates while keeping Compile as the only authority-changing path. - Classifies proof strengthening, scope expansion and semantic/proof/risk changes separately, with fail-closed summaries and no candidate Progress or acceptance state.
- Splits test feedback into affected developer tests, a bounded Long-Task Trust Boundary Gate and the unchanged complete release-regression suite.
- Keeps pull-request feedback faster without removing release coverage: broad, dependency and unknown changes still widen safely, while
mainand publish retain the complete suite. - Keeps the core positioning tight: minimal repo-native project memory for AI coding agents.
- Keeps the Minimal Context boundary explicit:
AGENTS.mdis the startup router,project_context/**keeps durable recovery facts, andvalidate-contextchecks recoverability. - Makes package updates explicit through release update modes:
sync-only,upgrade-required,manual-required. - Keeps the old stage-based Tiny Context workflow out of the default package surface.
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]