Claudinite growth: conversation extract (#771)

One rule from the 2026-07-24/26 conversation logs, landed at two rungs of
the local ladder: the routing surface (the skill's own description) plus a
terse RULES.md bullet.

The owner preference maps "LGTM" to the canon `merge-to-main` skill, but
`git-github` is not among this repo's declared packs, so that skill is not
mounted and `Skill(merge-to-main)` returns *Unknown skill*. Every session in
the captured corpus that was told to merge made that call first:

- issue-717 log @4346s -> Unknown skill, then find + hand-read the SKILL.md.
- issue-734 log @93089s -> Unknown skill, then find + read + grep before
  finally reaching `Skill(merge-and-ci)` at 93109s (~20s, 3 wasted calls).
- issue-753 log @5284s -> Unknown skill, then find + read (~12s, 2 calls).

The gap is in the routing surface: gcec's `merge-and-ci` description never
claimed the trigger phrases the preference routes on, so the model followed
the preference to the skill it names. Fixed by having `merge-and-ci` claim
"LGTM"/"merge to main" explicitly and state that `merge-to-main` is not
mounted here, plus one RULES.md bullet for the always-injected path.

Retention is unset, so nothing was pruned and the `conversation-logs` branch
was not touched. The issue-760 log yielded nothing new (its SessionStart-hook
miss is already captured by #766).

Refs #770

Co-authored-by: Claude <noreply@anthropic.com>

Author: missingbulb

.claudinite/local/packs/gcec/RULES.md

@@ -37,6 +37,14 @@ pipeline" section below, and its scheduled tasks live under `tasks/`.
   merge-and-ci skill — **load it for any PR a session opens**, including one
   opened incidentally mid-task by an unattended run, not only for a deliberate
   merge.
+- **On "LGTM" / "merge to main", load `merge-and-ci` — `merge-to-main` is not
+  mounted in this repo.** The owner preference names the canon `merge-to-main`
+  skill, but `git-github` is not among this repo's declared packs
+  (`.claudinite-checks.json`), so `Skill(merge-to-main)` returns *Unknown
+  skill*; `merge-and-ci` is the local pack's replacement and already states this
+  repo's merge rules. Every session in the captured corpus that was told to
+  merge made this call first and then hand-read the unmounted file
+  (#717, #734, #753) — a wrong first move on every single merge.
 - **Generated files are regenerated, never hand-merged.** On a conflict take
   either side and rerun `npm run regen` (load lists + UI snapshots +
   generic-coverage baseline/report). The committed `.gitattributes` maps each

.claudinite/local/packs/gcec/skills/merge-and-ci/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: merge-and-ci
-description: Drive this repo's PR-to-merged flow cheaply — when to open the PR, how to get CI green in a Claude web session, how to poll without wasting wall time or tokens, and when to arm auto-merge instead of waiting. Use whenever a session opens, watches, or lands a PR here — including one opened incidentally mid-task by an unattended or scheduled run, and any moment you ask "is CI green yet?" — not only for a deliberate merge or an e2e/heavy/UI change.
+description: Drive this repo's PR-to-merged flow cheaply — when to open the PR, how to get CI green in a Claude web session, how to poll without wasting wall time or tokens, and when to arm auto-merge instead of waiting. This repo's entry point for the owner's merge command, so use it when the owner says "LGTM", "merge to main", or otherwise asks to merge/land the current branch — the canon `merge-to-main` skill is NOT mounted here. Also use whenever a session opens, watches, or lands a PR here — including one opened incidentally mid-task by an unattended or scheduled run, and any moment you ask "is CI green yet?" — not only for a deliberate merge or an e2e/heavy/UI change.
 ---
 
 # Merge and CI in this repo