Skip to content

Project Tiny Context Harness 0.7.9

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jul 13:32
v0.7.9
6859676

Project Tiny Context Harness 0.7.9 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.7.9 with the synchronized package assets and CLI build.
  • Keeps the install path on the renamed package: project-tiny-context-harness.
  • Requires every implementation delivery to surface one repository-bound, risk-proportional Architecture Deliberation before implementation, including owner/extension-point, future-change, technical-debt and project-check conclusions.
  • Adds one current-candidate Architecture Conformance closure after project verification: default work carries it inside Contract Conformance, while Long-Task carries it only inside Final Gate so the same delivery never runs two architecture closures.
  • Keeps Contract Conformance and Context drift directional: the former checks Source/Context-to-implementation alignment; the latter checks whether implementation or new decisions made durable Context stale.
  • Fails new or worsened debt unless the project owns an explicit bounded exception, while avoiding automatic scope expansion into unrelated legacy debt.
  • Indexes the mechanism purpose, honest limits, debt policy, evidence boundary and future update invariants in PROJECT_SPEC.md and project_context/** without adding an architecture artifact, Contract field, Authority, Gate or workflow state.
  • Strengthens Long-Task mechanism admission so introduction cost participates in ROI and a merely positive but marginal benefit is insufficient.
  • 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