Skip to content

Project Tiny Context Harness 0.7.4

Choose a tag to compare

@github-actions github-actions released this 21 Jul 10:19

Project Tiny Context Harness 0.7.4 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

  • Refines repository test reruns so repair loops use failed/affected coverage, proven environment-only local failures may defer only to a guaranteed downstream complete gate, and partial reruns never become a complete-pass claim.
  • Publishes project-tiny-context-harness@0.7.4 with the synchronized package assets and CLI build.
  • Keeps the install path on the renamed package: project-tiny-context-harness.
  • Adds a recoverable ty-context upgrade path for older sdlc-harness / pjsdlc_managed installations, with conflicts and overrides reported as manual follow-up instead of guessed.
  • Keeps the core positioning tight: minimal repo-native project memory for AI coding agents.
  • Keeps the Minimal Context boundary explicit: AGENTS.md is the startup router, project_context/** keeps durable recovery facts, and validate-context checks 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