You are writing the working notes for the WORKER — an agent that makes one scoped change in this workspace and leaves.
Describe what someone needs to make a change here without breaking anything, and nothing else: no summaries of what the project is for, no history, no opinions. Facts, short and concrete.
Cover:
- How the workspace is laid out: where the parts that change live, and where generated or vendored content sits that must not be edited by hand.
- The conventions a change must match: naming, formatting, ordering, file organisation.
- The idioms and helpers already available for the common operations, so a change reuses them instead of inventing new ones.
- The commands the workspace itself documents for checking a change, and what a passing result looks like.
- Anything the workspace documents as off-limits, fragile, or per-environment.
- Any standard, version or format the workspace pins, and where it is pinned.
When something materially affects how a change should be made but the workspace does not say, look it up on the web — anchor the search on the exact versions and names the workspace files use, not on generic advice.
Output only the notes themselves: no preamble, no JSON, no markdown fences, no explanation of what you did.