feat(v-onboard): add Operations/Deployment coverage dimension to /v:onboard#4
Open
khymerao wants to merge 7 commits into
Open
feat(v-onboard): add Operations/Deployment coverage dimension to /v:onboard#4khymerao wants to merge 7 commits into
khymerao wants to merge 7 commits into
Conversation
…s + rule dispatch)
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.
What
Adds an explicit Operations / Deployment coverage dimension to the
/v:onboardpipeline. When a repo has CI/CD, container, or deploy files, onboarding now produces a citeddocs/superpowers/architecture/operations.mdinstead of silently dropping that layer from the generated knowledge base.Additive & gated —
operations.mdis only generated when ops files are present and the maintainer confirms it at the existing HUMAN GATE; an unattended/auto-approve run includes it with no new code path.Why
packalready includesdocker/**,.github/workflows/*, Terraform, and deploy scripts, so the raw material reached EXTRACT — but DETECT never inventoried it, EXTRACT had no claim type for it, and the arch doc set was fixed atarchitecture.md/business-logic.md/tech-context.md. Net effect: Docker topology, CI/CD, production domain, and runbooks were silently skipped — becoming confident partial truth downstream. This closes that blind spot.How it works
detect-opssubcommand (mirrorsdetect-ui) inventories three categories — CI/CD (.github/workflows/*,.gitlab-ci.yml,.circleci/config.yml,Jenkinsfile, …), containers/infra (Dockerfile*,docker-compose*/compose.*,*.tf/*.tfvars, k8s heuristics), and deploy/PaaS (Procfile,fly.toml,vercel.json,deploy*.sh, …). Returns{present, ci_cd[], containers[], deploy[]}; CLI printsops/no-opsor--json.type(operations) targetingoperations.md; load-bearing rules still bite (deploy-secret path, prod/branch gate, fail-closed CI check).typeis free-form toverify-citations, so no schema change.operations.mdas its own explicit per-artifact confirm; declining drops it. k8s detection is an honest filename/dir heuristic, flagged as such.Contents
scripts/compound-v-onboard.py—detect_ops()+_ops_category()+detect-opsCLI + selftest (walks the filesystem excludingVENDOR_DIRS, so the non-git--selftesttrees detect too)skills/compound-v/onboarding.md— DETECT bullet, EXTRACT type,operations.mddoc section, §6 gate confirm, §7 write surface, refresh notedocs/superpowers/specs/2026-06-30-v-onboard-design.md— artifacts-table row + conditional-fourth prosedocs/superpowers/{specs,plans}/2026-07-17-*Conventions / gates (verified locally)
python3 scripts/compound-v-onboard.py --selftest— 69/69 checks pass (64 pre-existing + 5 newdetect_ops)detect-ops --jsonverified on this repo (detects its own.github/workflows/*);no-opson a bare treeverify-citations/ claims-schema change; no new runtime deps, hooks, or scriptsscripts/lint-frontmatter.pynot run — nopyyamlin the local env; N/A regardless (diff touches no frontmatter)