Skip to content

Commit a7d8c96

Browse files
authored
Claudinite growth: conversation extract (#747)
Second pass over the 2026-07-24 capture (session 558026a0, worked under #717), after #732 mined it for the merge-and-ci CI-poll lessons. One further keeper: a stale origin/main fabricates work-scoped conformance findings — resolveBaseRef's origin/main-first probe leaves the merge-base behind main's real tip, so commits already on main are reported as introduced by the work. A blocking squash-merge-history finding named a merge commit on a branch with zero commits of its own; git fetch erased it, after ~49s and ~10 tool calls spent disproving it. Landed beside the existing stale-canon spurious-findings bullet. Retention is unset, so nothing was pruned. Measured efficiency: 63 of the session's 74 minutes were one idle wait for an owner ack; agent-side timing was already optimal. Refs #738
1 parent 3e08017 commit a7d8c96

1 file changed

Lines changed: 11 additions & 0 deletions

File tree

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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,17 @@ below). Portable rules these instantiate live in the canon packs/skills.
130130
workaround for a check finding** (an accept, a suppression pragma): a stale
131131
canon twice produced spurious findings whose fixes had already merged
132132
(#664, #665).
133+
- **A stale `origin/main` fabricates work-scoped check findings** — the checks
134+
resolve their base to the first of `origin/main` / `origin/master` / `main` /
135+
`master` that exists (`resolveBaseRef` in
136+
`.claudinite/shared/engine/checks/helpers/repo-context.mjs`), so an unfetched
137+
remote-tracking ref leaves the merge-base behind main's real tip and commits
138+
already **on** main get reported as introduced by your work. A fresh session
139+
on a branch with *no commits of its own* was told to rebase away main's own
140+
merge commit — a blocking `squash-merge-history` finding that a single
141+
`git fetch` erased (#717). **`git fetch origin main` before believing — or
142+
acting on — a work-scoped finding**; the destructive fix it suggests is the
143+
trap, not the finding.
133144
- **The cloud Setup script runs as root starting in the repo's parent dir**,
134145
not the checkout — a bare `npm ci` there silently installs nothing;
135146
`.claudinite/shared/engine/hooks/environment-setup-command.sh` `cd`s into the checkout first

0 commit comments

Comments
 (0)