context_harness_upgradelisted

# Context Harness Upgrade ## Package-Managed Boundary This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_harness_upgrade` Skill directly. This Skill handles Harness package upgrade and migration orchestration only. It does not author product facts, refactor business code, replace project tests or prove application quality. ## Purpose When the user asks to upgrade Tiny Context / Project Tiny Context Harness in an existing project, run the canonical `upgrade` path, handle only migration-scoped follow-up, and leave durable project semantics to the project Context and user-owned code. A `sync-only` release means no new migration is expected; it does not change the default upgrade entry for explicit upgrade requests. ## Workflow 1. Read the project routing and Context entry points before changing files: - `AGENTS.md` - `project_context/global.md` - `project_context/architecture.md` - `project_context/context.toml` 2. Inspect the working tree with `git status --short`. Do not revert unrelated user changes. 3. Prefer project wrappers when present: - `make ty-context-sync` - `make ty-context-upgrade` - `make ty-context-doctor` - `make validate-context` 4. If no wrapper exists, use the package CLI explicitly: - `npx --yes --package project-tiny-context-harness@latest ty-context sync` - `npx --yes --package project-tiny-context-harness@latest ty-context upgrade --check` - `npx --yes -