Skip to content

Claudinite growth dedup: prune two gcec rules the canon now covers - #754

Merged
missingbulb merged 1 commit into
mainfrom
claudinite/growth-dedup-d2026-07-26
Jul 26, 2026
Merged

Claudinite growth dedup: prune two gcec rules the canon now covers#754
missingbulb merged 1 commit into
mainfrom
claudinite/growth-dedup-d2026-07-26

Conversation

@missingbulb

Copy link
Copy Markdown
Owner

Scheduled grow_with_claudinite/growth-dedup run (dispatch #753). Repo-wide reconciliation of .claudinite/local/packs/ against the mounted canon at its stamp (claudinite.ref = 61b90ee).

Two bullets in the gcec pack's "Codebase gotchas" only restated a canon rule with this repo's issue numbers as illustration, so they are pruned:

Pruned local item Mounted-canon coverage
A stale origin/main fabricates work-scoped check findings (#717) .claudinite/shared/packs/git-github/skills/git-github-advanced/SKILL.md §"A conformance finding on history you didn't write may be a stale diff base — refresh before fixing": "In a fresh cloud sandbox that ref can be stale … Before acting on a finding you don't recognize, git fetch origin <default-branch> and re-run: a stale-base phantom disappears, and whatever survives against the current base is real — fix that."
The cloud Setup script runs as root starting in the repo's parent dir (#186/#196) .claudinite/shared/packs/basics/skills/engineering-practices/SKILL.md: "A cloud/root setup script may start in the repo's parent directory, not the checkout — a bare npm ci / build there finds no manifest and silently does nothing … Make the setup script cd into the checkout before running anything." (and the canon's own engine/hooks/environment-setup-command.sh already does the cd).

Kept deliberately (each says more than the canon's general rule, per the task's keep-test): the squash/(#N) + green-CI-twice merge rule, the generated-file set under npm run regen, the one-time rerere / merge.ours.driver bullet (it also records that the sandbox provisions them and that the fallback is benign), the canon-stamp-staleness gotcha (#664/#665 — no canon line states "check the stamp before committing a workaround"), the capture policy's repo-specific routing, and the local test-offline-list-sync check (no canon check enforces it).

Verification: check_the_world.mjs — 0 blocking (11 pre-existing advisories, unchanged); npm run test:offline — 315 tests, 0 fail.

Human approval gate: this task's declared outcome ceiling is open-pr; the agent does not merge it.

Refs #753

🤖 Generated with Claude Code

https://claude.ai/code/session_016wQrMfm6bY6CCWbbFvRxUL


Generated by Claude Code

Both pruned bullets restate a canon rule using this repo's issue numbers as
illustration, and the mounted canon (stamp 61b90ee) states each directly:

- "A stale origin/main fabricates work-scoped check findings" (#717) — covered by
  .claudinite/shared/packs/git-github/skills/git-github-advanced/SKILL.md
  §"A conformance finding on history you didn't write may be a stale diff base —
  refresh before fixing".
- "The cloud Setup script runs as root starting in the repo's parent dir"
  (#186/#196) — covered by
  .claudinite/shared/packs/basics/skills/engineering-practices/SKILL.md: "A
  cloud/root setup script may start in the repo's *parent* directory, not the
  checkout ... Make the setup script cd into the checkout before running anything."

Refs #753

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@missingbulb
missingbulb merged commit d2e3957 into main Jul 26, 2026
1 check passed
@missingbulb
missingbulb deleted the claudinite/growth-dedup-d2026-07-26 branch July 26, 2026 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants