@yagni-app/code-staging 1.2.10-staging.2101.1 → 1.2.10-staging.2105.1

package/dist/extension/pipeline/stages.d.ts

@@ -61,6 +61,13 @@ export declare const DECISIONS_READ_TOOL = "yagni_decisions_read_for_repository"
  * (`groundSessionPlan` in the backend's builder/planQuestions.ts). Each
  * question is the shape `packages/shared/src/planQuestions.ts` reads.
  */
+/**
+ * The planner's one rule for documentation (YAG-1067): it lists a
+ * documentation repository the change makes stale; the host decides from its
+ * index that the ticket is built beside the code, and never adds one the
+ * planner left out.
+ */
+export declare const DOCUMENTATION_REPOSITORY_RULE: string;
 export declare const PLAN_JSON_CONTRACT: string;
 /**
  * The one-attempt lane's session (`yagni go --headless --cloud`): plan,

package/dist/extension/pipeline/stages.js

@@ -145,6 +145,15 @@ export const DECISIONS_READ_TOOL = "yagni_decisions_read_for_repository";
  * (`groundSessionPlan` in the backend's builder/planQuestions.ts). Each
  * question is the shape `packages/shared/src/planQuestions.ts` reads.
  */
+/**
+ * The planner's one rule for documentation (YAG-1067): it lists a
+ * documentation repository the change makes stale; the host decides from its
+ * index that the ticket is built beside the code, and never adds one the
+ * planner left out.
+ */
+export const DOCUMENTATION_REPOSITORY_RULE = "When a documentation repository in Other repositories documents this one and the change alters " +
+    "behaviour its pages describe, list it in repositoriesNeeded too, with one line on the pages that " +
+    "change. It is built beside the code, not after it.";
 export const PLAN_JSON_CONTRACT = "End your answer with a fenced ```plan-json block and nothing after it:\n" +
     "```plan-json\n" +
     "{\n" +
@@ -173,7 +182,8 @@ export const PLAN_JSON_CONTRACT = "End your answer with a fenced ```plan-json bl
     "repository the change writes to, in the order they must be built and merged, this one included, each " +
     "with one line on what changes there. Only a repository the ticket's Other repositories section lists " +
     "counts; the host drops any other name. Leave it out for a change inside this repository alone, and " +
-    "never list a repository the change only reads.";
+    "never list a repository the change only reads. " +
+    DOCUMENTATION_REPOSITORY_RULE;
 /**
  * The cloud plan stage's task: the input folder the host wrote, read first,
  * then a plan grounded in the installed checkout, inside the stage's own
@@ -195,7 +205,10 @@ function cloudPlanTask(inputDir) {
         `- ${at("memo.md")}: what runs in this repository.\n` +
         `- ${at("checks.json")}: the repository's checks, and which already fail on the unchanged code.\n` +
         `- ${at("playbook.md")}: the Team's planning rules. Always follow them.\n` +
-        `- ${at("plan-line.md")}: this Team's instructions for planning.\n\n` +
+        `- ${at("plan-line.md")}: this Team's instructions for planning.\n` +
+        `- The repositories under "Read these repositories first" in ${at("ticket.md")}: clone each read-only ` +
+        "as it says, and read the pages it names before you plan; they are this team's own account of how " +
+        "the code works.\n\n" +
         "Planning is reading code, nothing else. Settle a fact by reading files, grepping, listing folders, and " +
         "reading the git history and the config. Run no tests and no type checks, build nothing, start no server, " +
         "no Docker and no database (`supabase start` included), and do not copy the repository: those are the " +
@@ -209,7 +222,8 @@ function cloudPlanTask(inputDir) {
         "When the change itself needs writes in one of those repositories (an API this repository calls, a " +
         "package it consumes), say so in the plan's repositoriesNeeded, in build order: the ticket is then " +
         "split into one ticket per repository, built in that order, and each step for another repository " +
-        "names it so the host can sort the steps.\n\n" +
+        "names it so the host can sort the steps. " +
+        `${DOCUMENTATION_REPOSITORY_RULE}\n\n` +
         `Call team_read with tool "${DECISIONS_READ_TOOL}" before you ask a person anything: a question an earlier ` +
         "decision on this repository already answers is not a question. Cite the decisions the plan relies on.\n\n" +
         "When the change shows in a page, plan a render check the build runs (open the page in the sandbox's " +

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yagni-app/code-staging",
-  "version": "1.2.10-staging.2101.1",
+  "version": "1.2.10-staging.2105.1",
   "description": "YAGNI Code: a terminal coding agent that already knows your company. One YAGNI login routes the model and grounds the agent in your team's context.",
   "license": "SEE LICENSE IN LICENSE.md",
   "author": "YAGNI, Inc. <jack@yagni.app> (https://yagni.app)",
@@ -58,5 +58,5 @@
     "turndown": "^7.2.4",
     "typebox": "^1.3.15"
   },
-  "yagniSourceSha": "e6789727a7d81a719cf1c6e3f3f6907a1f81df45"
+  "yagniSourceSha": "ed27eadceb2e3d91dfe2fd98bc2668c14ed436fe"
 }