Renn F f1b197def0 docs(conventions): dev-first framing + flag-enable + accuracy sweep ...

The conventions standard is dev-first by design — the developer receives the
architecture map + per-task constraints at spawn and owns conforming code from
the start; QA and the PR reviewer are the downstream net. Make that explicit in
the developer prompt and add a dedicated conventions section to the RAG
developer doc (it previously only mentioned the gate, reactively).

Also reconcile the docs with the hardened behavior: env-reference now shows the
flag is off by config default but on in the compose orchestrator block (left off
in the registry), mirroring toolchain matching; and the RAG standard's example
comment no longer implies a misplaced helper blocks (it warns).

2026-06-22 21:20:42 +02:00

..

conventions.md

docs(conventions): dev-first framing + flag-enable + accuracy sweep

2026-06-22 21:20:42 +02:00

python-basics.md

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see

2026-01-03 05:07:45 +01:00

python-errors.md

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see

2026-01-03 05:07:45 +01:00

python-security.md

Fixed some ggit operations and that. Still needs work. PR problem

2026-04-21 04:21:08 +02:00

testing.md

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see

2026-01-03 05:07:45 +01:00

typescript.md

NOW RAG is actually usable... might switch to gemma3:4b from glm-4.6 cloud for expenses reasons but we'll see

2026-01-03 05:07:45 +01:00