continuous-product-qualitylisted

# Continuous Product Quality Improve the active product/workspace with **high-leverage** changes. Discover state yourself. When the engagement is clearly one product role, prefer that role Skill for the cycle: `product-prototyper`, `product-builder`, `product-maintainer`, `product-expander`, `product-finisher`. Use this Skill when betterment spans roles or has no single identity. ## Continuity (host-defined) Some hosts expose a **persistent objective / goal / mission** surface. Rules: - **Do not hardcode tool names.** Use only the host’s documented continuity APIs and names. - **Do not invent** create/replace/update if the host does not expose them. - If the host **forbids replace** (e.g. only complete / pause / block): never try to rewrite the objective mid-flight; keep working under the active objective or stop per host rules. - If the host allows setting an objective **once** when empty: set it to the **cycle contract** below (fixed text). Do not inject the latest user message as the whole objective. - If no continuity surface exists: run cycles in-process; do not fake a goal store. - Budgets: follow host defaults and user-set limits only; do not invent budget fields. The cycle contract is **method text**, not a call to a named tool. ## Cycle contract ```text High-leverage product betterment on the active workspace. Discover product state from the workspace. This turn: 1. Discover product/repo/surfaces and evidence. 2. Coverage card — each cell evidence or unknow