@aacombarro89/praxis 0.1.13 → 0.1.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aacombarro89/praxis",
-  "version": "0.1.13",
+  "version": "0.1.14",
   "description": "A CLI that installs an AI methodology layer into a codebase.",
   "type": "module",
   "bin": {

package/packages/layer2/workspace/commands/workspace-upkeep.md

@@ -12,6 +12,28 @@ upkeep, keeps the hub wiki's cross-repo knowledge current, fans work out to
 cloned members in **audit mode only**, and never edits a member repo without
 the user's explicit confirmation.
 
+**Planning entry.** Enter this pass in planning mode when the rule's planning
+trigger routed here, or when `{{arguments}}` states a planning or
+implementation question rather than a general sweep. Under planning entry:
+scope step 4's fan-out to one read-only planning workstream per affected
+cloned member instead of the full roster; treat steps 2 and 3 as optional
+observations, skipped when they don't bear on the question; and collapse
+steps 5 and 6 into a single planning synthesis — constraints, validation
+commands, risks, and `file:line` evidence for the hub plan — instead of the
+consolidated upkeep report. The entire pass runs read-only in this mode: hub
+drift (step 2) and wiki staleness (step 3) are reported as proposals only,
+and no `sync`, wiki edit, or instruction edit is applied until the user is
+out of planning and confirms.
+
+**CLI resolution (all repos).** In the hub and every cloned member, run
+`praxis check` when that repo has an available `praxis` command. If `praxis` is
+unavailable, immediately fall back to `npx @aacombarro89/praxis@latest check`
+and continue the pass — a missing local command is not a reason to skip that
+repo. Use the matching `praxis sync` or
+`npx @aacombarro89/praxis@latest sync` invocation if drift needs syncing.
+Always pin the fallback to `@latest`; never use a bare
+`npx @aacombarro89/praxis`, which can silently reuse a stale cached build.
+
 1. **Read the workspace** from `praxis.yaml`'s `workspace:` section (members,
    edges, contract pages). If it is absent, say so and stop — this command is
    for a workspace hub only. Note any member whose directory isn't cloned yet;
@@ -31,15 +53,27 @@ the user's explicit confirmation.
    `{{workflow:praxis-wiki}}`'s own conventions and confirmation gate before
    creating or editing pages.
 
-4. **Member fan-out (report-first).** For each **cloned** member, produce a
+4. **Member fan-out (report-first).** For each **cloned** member — each
+   **affected** cloned member only, under planning entry — produce a
    per-member brief with `{{workflow:praxis-handoff}}` and delegate one
    workstream per member — where the tool lacks subagent spawning, execute the
-   briefs sequentially instead. Each delegate works inside that member's own
-   directory, reads that repo's own agent instructions and rules first, then
-   runs its upkeep in **audit mode**: run `praxis check` there, assess
-   instruction/wiki currency, and **return proposed edits without applying
-   them**. Also have it flag any duplicated cross-repo integration prose that
-   belongs in the hub's contract pages instead.
+   briefs sequentially instead. Every brief must name the resolved member root
+   (the hub root plus the member's declared `path`) and make the delegate's
+   first tool action use that root as its working directory; the delegate
+   confirms the root it used in its report. Each delegate reads that repo's own
+   `CLAUDE.md` and every file under `.claude/rules/` (Claude Code) or
+   `AGENTS.md` (Codex/agents-md) first, then `docs/wiki/index.md` when it
+   exists and the relevant pages those entrypoints identify, before inspecting
+   source.
+
+   When the focus is planning or an implementation question, do not stop at
+   methodology currency: state the concrete member-local question in the brief,
+   inspect the relevant implementation source and nearest tests, and return the
+   constraints, local validation commands, and unresolved risks with `file:line`
+   evidence. Keep the workstream in **audit mode**: run `praxis check` there,
+   assess instruction/wiki currency, and **return proposed edits without
+   applying them**. Also have it flag any duplicated cross-repo integration
+   prose that belongs in the hub's contract pages instead.
 
 5. **Edge-based staleness judgment.** For each member with changes since its
    relevant contract page was last touched (compare via `git log`), walk

package/packages/layer2/workspace/rules.md

@@ -13,5 +13,17 @@ member, an edge change), or on a periodic sweep, run
 `{{workflow:praxis-workspace-upkeep}}` rather than fixing hub/member drift
 piecemeal.
 
+Planning trigger: when planning a change that may cross member boundaries, or
+when the plan needs member implementation details, enter through
+`{{workflow:praxis-workspace-upkeep}}` before finalizing the hub plan. Fan out
+one read-only planning workstream per affected cloned member. Every brief names
+the resolved member root and makes the delegate's first tool action start there;
+the delegate reads that member's `CLAUDE.md` and every file under
+`.claude/rules/` (Claude Code) or `AGENTS.md` (Codex/agents-md), plus
+`docs/wiki/index.md` and relevant linked pages when present, then inspects the
+implementation source and nearest tests. Synthesize the returned constraints,
+validation commands, risks, and `file:line` evidence in the hub — never infer
+member implementation from hub prose alone.
+
 Sovereignty: never edit a member repo's files from the hub uninvited — audit,
 propose, and apply only what the user confirms.