A video game where you play as a misaligned AI, deceiving and building power. An experiment in spec-driven development. cameron.tngl.io/misaligned

Wiki migration stage 4/4: absorb history (devlogs into wiki/log/) master

The last stage of spec/wiki.md's migration plan: move devlogs/ and DEVLOG.md under wiki/log/, append-only rules unchanged. - git mv on all 22 dated devlog files and DEVLOG.md (history preserved). devlogs/README.md removed — superseded by the wiki/log/README.md already written in stage 1. - Repointed every reference across AGENT.md, the root README.md, and the whole prompts/ dispatch library (never touched since it predates the migration, but its prose still needed correct paths — it gets pasted into fresh agents). Root README.md also had a stale knowledge/spec/ reference missed in stage 2 (it lives outside wiki/, so wasn't in that stage's file list) — fixed here. - tools/wiki_gate.sh: fixed a hardcoded DEVLOG.md root-path check that broke once the file moved; deliberately exempted wiki/log/*.md (except log/README.md) from the SUMMARY.md orphan-reachability requirement. Devlogs are meant to be a low-friction, append-only end-of-session habit; requiring a matching SUMMARY.md edit for every dated entry would either rot (forgotten, permanently failing the gate) or turn "write a devlog" into a two-file chore. They're browsed via wiki/log/DEVLOG.md's ledger and git log, not the hand-maintained nav tree. wiki/SUMMARY.md gains a log/DEVLOG.md entry plus a note explaining the exemption. All four migration stages (Adopt, Move, Render, Absorb history) are now landed. spec/wiki.md acceptance criteria 1, 3, 4, and 5 verified; a final full audit against every criterion (and the Status flip to IMPLEMENTED) is the remaining step. Defense: spec/wiki.md's own migration plan, stage 4. Completes the constitution's "one wiki tree ... single navigation surface" shape; the wiki/log/ exemption is a reasoned scope call (documented above and in the script) that keeps the gate's spirit (nothing invisible) without fighting the practice the append-only law depends on. NOTE: per instruction, this branch is intentionally NOT merged to main — left for review given the size of the path churn across the whole documentation tree.