harness_package_designlisted

# Harness Package Design Authoring Maintain this repository as the source workspace for Project Tiny Context Harness. The product keeps `project_context/**` as the smallest durable project fact source, supplies the automatically applicable default Workflow Contract, and optionally supplies one Single-Goal Long-Task authority path. Harness maintains Context and workflow mechanisms; project code, tests, runtime evidence, CI and human acceptance prove product quality. This authoring Skill is repository-local. Never copy `.codex/skills/authoring/**` into consumer package assets. A rule that belongs in every consumer must reach its actual managed source, package asset, public guidance, Context and tests through the normal source-sync path. ## Always establish 1. Follow root `AGENTS.md`; read core Context, the default area and triggered owning Context before deciding the change. 2. Separate current implementation truth from intended product truth. Index the real owner, managed source, generated/install surface, package asset, public docs, tests, migration and release impact. Do not patch only the first failing copy. 3. Before the first implementation edit, surface the repository-bound Architecture Deliberation required by the default Workflow Contract and choose exactly one `Context Delta: none|required`. Durable mechanism or distribution meaning is normally `required` and reaches owning Context before code. 4. Preserve Minimal Context: no stage artifact chain, second Authority