The site was rewritten across every structural page to reflect the post-flavor framework. Pre-Cowork content — the three-flavor split, the cross-platform language, the file-attachment workflow — was retired. The framework users meet on the site is the framework they get.

The blog category that hosts framework writeups, decision narratives, and lessons-learned dispatches now has a fixed name. The lock keeps the editorial posture from drifting under future themes; readers can subscribe knowing what they’re subscribing to.

The file every CRAFT session reads on boot now has a written contract: required sections, optional sections, behavioral-directive encoding rules, generation and maintenance guidelines. Sessions that follow the spec open with the same ground state across projects.

LOCK now means “preserve bytes” by default. Any narrow modification to a LOCKED artifact requires a revision-delta block stating what changed, why, the BLESS source, and the scope bound. Silent edits are forbidden under any circumstance — readers can audit prior LOCKED state byte-for-byte.

Personal access tokens are issued per session, used inside the session, and scrubbed before the session closes. Tokens never persist in mounted folders, environment files, or git config. The discipline turns a recurring leak vector into a bounded, auditable event.

Recipes now carry a lifecycle stage that signals maturity: Experimental, Tested, Official, Deprecated. Stage transitions are explicit; combination rules govern which stages can compose together. AI sessions can read the stage and adjust trust accordingly without inspecting recipe bodies for hints.