Structured Coding 0.1.2

Documentation release. Planning documents get a default home.

Changed

The workflow named docs/plan/… and before_end_memory.md as examples and said plainly they were not prescribed. That left every project to invent a location, and put a handoff file at the repository root — the least welcome place to leave one in someone else's project.

Planning documents now default to .structured-coding/plans/<effort>/, one directory per effort:

.structured-coding/plans/infra-exp-p0/overall.md
.structured-coding/plans/infra-exp-p0/step-01-user-map.md
.structured-coding/plans/infra-exp-p0/pr-01a-proposer.md
.structured-coding/plans/infra-exp-p0/pr-01a-contract.md
.structured-coding/plans/infra-exp-p0/handoff.md

That directory already existed for the standards configuration, so the toolkit now has one home in a project rather than two, and your own docs/ tree is left alone. Grouping by effort keeps concurrent overall/step/PR hierarchies from colliding.

It is a default, not a requirement

If you already keep planning documents somewhere else, keep them there. What matters is that one location is the authority and a later session can find it. Nothing refuses to work because of where a document sits.

Commit them if later sessions or teammates need to read them, which is usually the point of writing them down.

Upgrading

Nothing to migrate. Existing plans keep working wherever they are. --check-hooks reports the installed release, now 0.1.2.

Unchanged

SKILL.md and the three preserved prompts are untouched. merge-guard is still not implemented and will not be, and the continuity compact validation debt is still open — see the 0.1.0 notes for what this toolkit deliberately does not do.