Skip to content

Project Tiny Context Harness 0.7.3

Choose a tag to compare

@github-actions github-actions released this 21 Jul 06:39

Project Tiny Context Harness 0.7.3 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.3 with the synchronized package assets and CLI build.
  • Adds a conditional Design Authority Check before material production UI while keeping local style fixes and explicit prototypes on the lightweight path.
  • Replaces the generic starter visual system with an explicitly unconfigured DESIGN.md scaffold that indexes one authored token source/generation direction and selected design references without pretending to be a production layout target.
  • Classifies design references as exact-target, constraint or inspiration, and forbids an implementation screenshot from becoming the target it claims to match.
  • Extends ty-context doctor with advisory DESIGN.md authority status, including recognition of the legacy starter as unconfigured.
  • Aligns context_uiux_design, context_development_engineer, Source Plan authoring and Long-Task pre-Compile guidance so missing or conflicting visual authority is resolved before implementation or Authority Lock.
  • Keeps verification honest across targets: browser evidence cannot substitute for a native runtime that can fail independently.
  • Adds no visual Schema, lifecycle state, mandatory design directory, Figma dependency or universal pixel threshold; this remains a sync-only release with no user-project migration.

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