Update History

At the end of every working session, before closing. This is not optional — a missing history entry means lost context for the next session.

Add a new entry at the top of history/index.page.

For long or complex sessions, create a dedicated .page file inside a dated folder (e.g. history/2026/08-August/04-Tuesday/session-name.page) and link to it from the index.

What was built or changed — be specific about systems, files, and behaviours. Name the things that changed.

Decisions made and why — include the reasoning behind choices. This is the most valuable part. Future agents will use it to avoid undoing deliberate decisions.

Anything surprising or non-obvious — constraints discovered, bugs encountered, workarounds applied. If it surprised you, it will surprise the next reader too.

What was not done and why — if something was considered and deliberately skipped, note it. Prevents the same ground being covered again.

Do not copy code into history entries — reference files instead. Do not repeat what is already obvious from the code. Do not write step-by-step procedures — those belong in guides.