Skip to content

Project Tiny Context Harness 0.11.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Sep 08:31
v0.11.0
a8e9105

Project Tiny Context Harness 0.11.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 project-tiny-context-harness@0.11.0 with the synchronized package assets and CLI build.
  • Keeps the install path on the renamed package: project-tiny-context-harness.
  • Adds one shared Context Catalog, an experimental read-only Router over registered and unregistered Context, full advisory Doctor/inspect diagnostics, safe unregistered scaffolds and recoverable dry-run-first register/move transactions without changing Schema v4 or default-footprint behavior.
  • Adds the sparse Design Authority bundle: root DESIGN.md remains the sole entry/revision/editable-Token owner, adoption writes the canonical body-leading bundle-v1 marker together with the manifest, marker/manifest mismatch and non-portable path spelling fail closed, the manifest owns only complete closure identity, and generated Tokens are deterministic output.
  • Extends explicit-only design-system-authoring with bootstrap, revise and reconcile; candidate selection and the later exact-diff Authority adoption confirmation remain separate decisions.
  • Gates only style-bearing design-resource-authoring work on configured Design Authority, binds formal handoffs to the complete closure and emits only a non-authoritative three-branch Authority Delta Assessment before an independently invoked DSA flow.
  • Sends revised proposals and selected resources directly into the long-task-workflow Skill's Source-bound Contract Draft loop; Source completeness and Contract mapping converge there without an internal Source-authoring stage, while source-plan-authoring remains only a retired compatibility pointer.
  • Keeps the authority boundary explicit: provider candidates and bindings are provenance, root DESIGN.md and owning project_context/** remain canonical, and neither generated Tokens nor the closure manifest become a second editable Authority.
  • 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

Assets 2
Loading