@papi-ai/server
Advanced tools
+1
-1
| { | ||
| "name": "@papi-ai/server", | ||
| "version": "0.7.62", | ||
| "version": "0.7.63", | ||
| "description": "PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects", | ||
@@ -5,0 +5,0 @@ "license": "Elastic-2.0", |
@@ -41,2 +41,3 @@ # AGENTS.md | ||
| - **Commit per task within grouped branches** — traceable git history. | ||
| - **Integration + gate before release when a cycle fans to more than 4 module branches.** A wide cycle has no single point where all branches are proven together, so a collision between two branches only surfaces at release. When a cycle has more than 4 module branches, before `release`: (1) cut an integration branch off your main branch, (2) merge every cycle module branch into it, (3) run your full local gate/test suite on the integrated result, (4) resolve any cross-branch collisions there, (5) release from the integrated branch. This is a habit, not automation — release does not block on branch count. | ||
| - **Never use `build_execute` with `light=true` on shared branches.** Light mode commits directly to the current branch without creating a PR. When a shared branch is squash-merged, those commits are collapsed — any CLAUDE.md or documentation changes are stripped. Use light mode only on isolated single-task branches where no squash-merge will occur. | ||
@@ -43,0 +44,0 @@ |
Sorry, the diff of this file is too big to display
Sorry, the diff of this file is too big to display
1733434
0.7%36168
0.72%