chore: dogfood init — add CI adoption files to the repo#35
Open
bntvllnt wants to merge 1 commit into
Open
Conversation
Generated by `codebase-intelligence@canary init` (the feature from #34). The repo now instructs its own AI agents to query CI before grep/read. - AGENTS.md, CLAUDE.md: managed instruction block appended - GEMINI.md, CONVENTIONS.md, .cursor/rules/, .github/copilot-instructions.md: new - docs/agent files only — no src change, does not trigger a canary publish
bntvllnt
commented
May 30, 2026
Owner
Author
bntvllnt
left a comment
There was a problem hiding this comment.
Review — 0 findings (0 blocking, 0 warn)
BLOCKING
None.
WARN
None.
VERIFIED CLEAN
- Reviewed all changed files at head
e352f773707d74246b11cd970a1e80a8917b69c1:.cursor/rules/codebase-intelligence.mdc,.github/copilot-instructions.md,AGENTS.md,CLAUDE.md,CONVENTIONS.md,GEMINI.md. - The PR is bounded to repo/agent instruction adoption files only; no
src/**, package metadata, release, or runtime behavior changes are included. - The inserted managed blocks match the single source of truth in
src/install/index.ts#renderBlock, preserve existingAGENTS.md/CLAUDE.mdcontent, and use valid CLI commands present insrc/cli.ts. - The additions align with the VLLNT Platform dogfood objective: this repo now consumes the
initadoption layer it ships, without adding internal/private operational details. - Manual approval recommended. Per reviewer policy, I am not submitting an autonomous APPROVE.
VALIDATION
- Live PR state re-fetched immediately before review: open, non-draft, base
main, heade352f773707d74246b11cd970a1e80a8917b69c1,mergeStateStatus=CLEAN,mergeable=MERGEABLE, no prior reviews/comments observed. - GitHub checks observed:
Quality Gates (18)pass;Quality Gates (22)pass. - Ran locally after
pnpm install --frozen-lockfile:git diff --check origin/main...HEAD— passpnpm lint— passpnpm typecheck— passpnpm build— passpnpm test— pass: 17 files, 310 passed, 3 todo
- Ran built CLI smoke/idempotency check:
node dist/cli.js init <temp-repo> --no-skill --jsoncreated/updated the six target files on first run, reported all six unchanged on second run, preserved pre-existingAGENTS.mdcontent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dogfoods the
initcommand shipped in #34, verified against the published canary2.3.0-canary.8cfac95.Running
codebase-intelligence@canary init .on this repo generated the agent-adoption files. The repo now practices what it ships — AI agents working here are told to query codebase-intelligence before grep/read.Files
AGENTS.md,CLAUDE.md— managed instruction block appended (existing content untouched)GEMINI.md,CONVENTIONS.md,.cursor/rules/codebase-intelligence.mdc,.github/copilot-instructions.md— newPure additions (151 insertions, 0 deletions). Docs/agent files only — no
src/**change, so this does not trigger a canary publish on merge.Verification
initfrom the published canary: 6 files written, pre-existing content preserved, re-run fully idempotent, skill install confirmed (temp HOME). End-to-end pipeline (merge → OIDC canary publish → npx @canary → init) works.