docs(cobesy): humanize proximity wording, drop em dashes

Run /humanizer on the sections added in 94aa1a3: replace the two em dashes in
the environment-gap bridge and proximity subsection with a colon and plain
sentences, and cut the slogan-y "Proximity beats completeness". Folds into the
unreleased v1.0.2.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: norandom

cobesy/references/03-cognitive-layer.md

@@ -62,9 +62,9 @@ Do not treat a motivation or environment gap as a knowledge gap. Adding content
 to a non-knowledge gap increases load and fails.
 
 An **environment gap** is the hinge between this layer and the behavioral one.
-You close it by changing what surrounds the work — defaults, triggers, removed
-obstacles, "if X then Y" implementation intentions — not by adding motivation or
-a pep talk. That same structural change is what lets a cascade run on its own
+You close it by changing what surrounds the work: defaults, triggers, removed
+obstacles, "if X then Y" implementation intentions. A pep talk does not close it.
+That same structural change is what lets a cascade run on its own
 (see `02-behavioral-layer.md`): enthusiasm fades, a changed environment does not.
 
 ### Working memory is the gatekeeper
@@ -95,10 +95,10 @@ logical argument to the Rider.
 Transfer depends on distance. If someone has to leave the workflow to look up a
 process, adoption drops and they fall back on half-remembered shortcuts. So
 deliver the compressed logic *at the point of action*: inside the agenda being
-built, next to the code being reviewed, in the checklist they already have open.
-Proximity beats completeness — a short job aid in the workflow lands better than
-a thorough doc one tab away. This is the design rule for `agenda_structure`, and
-it is the **Proximity** check in the validation gate.
+built, next to the code being reviewed, or in a checklist they already have open.
+A short job aid in the workflow beats a thorough doc one tab away. This is the
+design rule for `agenda_structure`, and it is the **Proximity** check in the
+validation gate.
 
 ---