Skip to content

fix(bootstrap-03): document submodule-vs-monorepo graphify install paths#11

Merged
cms-pm merged 2 commits into
mainfrom
fix/adg-bootstrap-03-submodule-graphify-path
Apr 24, 2026
Merged

fix(bootstrap-03): document submodule-vs-monorepo graphify install paths#11
cms-pm merged 2 commits into
mainfrom
fix/adg-bootstrap-03-submodule-graphify-path

Conversation

@cms-pm
Copy link
Copy Markdown
Owner

@cms-pm cms-pm commented Apr 23, 2026

Summary

  • runbooks/RELEASE_PROCESS.md: new "Graphify Install Paths" section with explicit monorepo vs submodule-consumer install commands.
  • scripts/run_graphify.sh: emit both install paths in the "graphify not on PATH" failure message.

Closes #4

Test plan

  • bash -n scripts/run_graphify.sh
  • On a system with graphify absent from PATH, invoke the wrapper; confirm the failure message lists both paths.
  • Runbook section renders correctly.

🤖 Generated with Claude Code

cms-pm and others added 2 commits April 23, 2026 00:05
…ths (#4)

Consumers were guessing the graphify source path for `pip install -e`
because neither RELEASE_PROCESS.md nor run_graphify.sh documented the
submodule layout (`.governance/ai-dev-governance/graphify`).

- RELEASE_PROCESS.md: new "Graphify Install Paths" section with explicit
  monorepo vs submodule-consumer blocks.
- run_graphify.sh: emit both paths in the "graphify not on PATH" failure
  message so consumers get actionable guidance at the point of failure.

Closes #4

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@cms-pm cms-pm merged commit 8dba74f into main Apr 24, 2026
1 of 2 checks passed
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.

ADG-BOOTSTRAP-03: graphify fallback bootstrap docs assume a top-level ./graphify

1 participant