passepartout: v0.4.1 Design Cleanup

- Remove system-prompt-augment mechanism, introduce *standing-mandates*
- Fix false token-overhead claims in DESIGN_DECISIONS + ROADMAP
- Update security vector count 9-10 across all docs and dispatcher docstring
- Rewrite README with agent section, soften aspirational claims
- Register 10 cognitive tools in programming-tools.org with test suite
- Enforce NO-HARDCODED-CONSTANTS in .env.example
- ROADMAP: mark v0.3.x patches DONE, add LOGBOOKs, mark releases
- AGENTS.md: rewrite compact (180 to 50 lines), move refs to CONTRIBUTING
- Normalize org tangle directives to file-level PROPERTY inheritance

org/programming-standards.org

@@ -78,6 +78,17 @@ The Diagnostics skill is the self-knowledge of Passepartout. It answers
 3. Every test in ~* Test Suite~ MUST reference a specific Contract item.
 4. If you change a function's signature, you MUST update its Contract item.
 5. These files are excluded (no defuns): ~core-manifest.org~, ~setup.org~.
+6. **NO-HARDCODED-CONSTANTS**: All configurable values (thresholds, intervals,
+   paths, limits, counters) MUST be read from environment variables with a
+   documented default in ~.env.example~. No magic numbers, no hardcoded
+   string literals in function bodies for any value a user might need to
+   change. The user owns their configuration — they change it in ~.env~, not
+   in the source code. Exceptions: internal implementation details that are
+   never user-facing (hash-table sizes, buffer capacity limits, loop
+   iteration caps) may live in source. But if the value controls *behavior*
+   (how many approvals before a rule, what similarity threshold gates
+   context, how long a shell command runs before timeout), it lives
+   in ~.env~ with a fallback default.
 
 ** Engineering Lifecycle (Two-Track)