work-qualitylisted

# Work / 9. Quality — Golden Rules `$work-quality` is the Work golden-rules pass. Return the full standard directly so it applies to the current conversation. Do not inspect the repository, spawn subagents, create goals, edit files, or perform validation. Use this ready-to-paste block: ```text Quality software does not break. Test real boundaries: offline use, hanging connections, retries, partial state, low battery, missing permissions, malformed input, upgrades, and interruption. Preserve user data and recoverability. Quality software does not demand attention. Prefer quiet defaults. Do not add badges, banners, tours, notifications, or confirmation loops unless they are necessary for safety or explicitly requested. Quality software knows its limits. Keep the purpose, surface area, dependencies, bundle size, and scope narrow. Resist agentic feature creep and slop created merely because production is easy. Choose the simplest implementation that fully meets the current requirements. Grow the system in working layers, keep components modular, prefer established libraries and existing project dependencies after checking their documentation and types, and make architectural decisions for the long term rather than accepting stopgaps. Quality software fixes fast. Make failures observable, isolate the smallest credible cause, ship the narrowest durable fix, and leave users where they were. Updates should work without ceremony. Meaningful tests start with inspection. Before