[JacobStephens2]

Summary

This adds a glossary term for the directory a Run is started from. The code already calls it the "launch directory" throughout, and #74 is about that directory. Origin match, Base branch and User config now refer to the new term.

+**Launch directory**:
+The directory a **Run** is started from. It must pass **Origin match**, and its
+checked-out branch is normally the **Base branch**. A Run works in its own
+worktree, never in the Launch directory.
+_Avoid_: originating workspace, launch repo

 **Origin match**:
-... the `origin` remote of the directory the factory is started from.
+... the `origin` remote of the **Launch directory**.

 **Base branch**:
-... Normally the branch checked out in the directory the factory is started from;
+... Normally the branch checked out in the **Launch directory**;

 **User config**:
-... such as the **Run notification** address and whether every Run is a **Merge run**.
+... such as the **Run notification** address, whether every Run is a **Merge run**,
+and whether a Run first brings the **Launch directory**'s checkout of the
+**Base branch** up to date with `origin`.

The User config entry describes the launch.pull setting that #74 specifies. That setting isn't implemented yet. It comes from the grilling session for #74.

Evidence

• Before: CONTEXT.md has no term for the directory a Run is started from. Two entries describe it indirectly as "the directory the factory is started from".
• After: one defined term, used by every entry that needs it. This change is documentation only, with no code changes.

Merge Danger

Door: two-way

Blast Radius: glossary

Only CONTEXT.md changes. Until #74 lands, the User config entry describes a setting that doesn't exist yet.

🤖 Generated with Claude Code