Fredagsregler: tre evidensbaserede tilfoejelser fra ugens haendelser

1. text-artifacts-require-explicit-utf8-handling (Type B): to
   produktionshaendelser, samme sygdom - smiley double-encodet via
   HTTP-streng, og en Mode B-batch der skrev mojibake i tre CLAUDE.md
   fordi PS 5.1 laeser BOM-loese .ps1 som cp1252. Reglen: raa bytes
   ved transfer, eksplicit UTF-8 ved write, tekst-transformation i
   Python, grep for maerket foer commit.

2. log-writes-must-survive-rollback (Type B): fejl-logs skrevet i
   samme transaktion forsvinder ved rollback - loggen mister praecis
   de fejl den findes for. Isoleret session (StartSession -> insert +
   commit) er moensteret. Evidens: Wareco IC web-service-log
   2026-07-02; havde tidligere kostet en udvikler det meste af en dag.

3. Skaerpelse af setup-doc-must-not-reference-unpromoted-stable-files:
   kanal-tilstand verificeres via git (ls-remote/klon), aldrig CDN;
   to sande observationer kan modsige hinanden naar verden flytter
   sig imellem dem - tidsstempl al kanal-evidens. Felt-verificeret
   af Conzept-sessionens selvkorrektion 2026-07-03.

Foerste PR foedt direkte i QualityHub.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Michael Dieringer 2026-07-03 19:03:23 +02:00
parent 3a70d10afd
commit d2e2f2adb4
3 changed files with 137 additions and 0 deletions

View file

@ -41,6 +41,13 @@ sit merged on `main` without the referenced file being available on
3. Consumers (sessions, Mode B) that hit a 404 on a documented stable path
report the gap — they never silently fetch from `main` instead. The
channel discipline outranks the convenience.
4. **Channel-state evidence comes from git, never from a CDN.** Verify with
`git ls-remote`/a fresh clone — raw-URL caches lag minutes behind, so a
404/200 observed right after a promote can be stale. Two true
observations can contradict each other when the world moves between
them: timestamp every piece of channel evidence before acting on it.
(Field-verified 2026-07-03: a session's real 404 was fixed mid-flight;
it re-verified by cloning the branch and correctly withdrew its case.)
## What NOT to do