kiss-memory

Finish a piece of work on a kiss-ssg site — verify the build diff against the intent captured at kiss-branch-open, prove the site's knowledge base was kept up (notes for every controller, URL model and pipeline step the change touched), record and commit `AIKB/`, write the reflection into the session file, and push. Use when asked to "close the branch", "wrap this up", "we're done, ship it", "finish this change", or "write the retrospective" on a kiss-ssg site. Opens a pull request only when asked.

Capture what a piece of work on a kiss-ssg site is meant to change, before changing it — objective, checkable criteria, non-goals, impact surface — into a session file, then create or adopt the branch. Use when starting work on a kiss site, or when asked to "open a branch", "start a new feature on the site", "add a section to the site" (before writing it), "capture intent", "spec this before we build", or "plan this change". Pair it with kiss-branch-pulse mid-work and kiss-branch-close at the end.

Mid-work checkpoint on a kiss-ssg site — re-run the build check against the recorded baseline, read the page diff against the criteria captured at kiss-branch-open, log the beat and decide continue / adjust / amend / ready-to-close. Use when asked to "pulse", "check progress", "how are we doing against the brief", "am I drifting", "is this ready to close yet", or every time a slice of the change is finished. Cheap and repeatable; not a substitute for kiss-branch-close.

Tidy a kiss-ssg site's knowledge base — fold the durable lessons out of the session logs into `AIKB/site.md`, retire feedback that keeps coming back, and fix the stale, dangling and dead notes the check reports. Use when asked to "consolidate the knowledge base", "tidy the notes", "fold the session logs into site.md", "the same feedback keeps coming back", "the knowledge base feels inconsistent", "the notes are out of date", "clean up AIKB", or when kiss-branch-open or kiss-branch-close recommends it. Housekeeping between pieces of work — it never records the knowledge base and never opens or closes a branch.

Brief a developer returning to (or joining) a kiss-ssg site — what it is, how it is built, what changed lately, what was left open, what bites. Use when asked to "catch me up", "what is this site", "remind me how this site works", "I haven't touched this in months", "onboard me to this repo", "who is this site for", or when starting work in an unfamiliar project that has `node_modules/kiss-ssg` installed. Not for verifying a build (use kiss-build-check) or for starting a piece of work (use kiss-branch-open).