v0.12.48: @newsroom.writer: Hooks are kernel code

A new article written here from a voice memo, and a brief for the session that builds a hooks site and feed. Hooks are small code with kernel reach, so they should be managed like kernel code; their size makes them the best case study for code review, fractal semantic graphs and change blast radius. A maturity model (L0 in the prompt, L1 a model decides, L2 a deterministic script, L3 managed and proven, L4 off the machine) with three questions for every hook: power, the lethal trifecta, the sandbox. The first ten hooks mapped: three this session runs, five tested in the sandbox, two proposed (an integrity hook that checks the others, and a read-only security review agent hook); 4 to 26 lines each, with the commit hook's 37-line scan as the example of hooks of hooks. A site and a feed from intent to signed release, a JSON record per hook, and billing where nobody pays to run a hook and paying buys state. Three figures. Nothing in the brief is built.