pi-agent-codebase-workflows - npm Package Compare versions

Comparing version

0.6.0

0.6.1

+1

-1

package.json

		{
		"name": "pi-agent-codebase-workflows",
		"version": "0.6.0",
		"version": "0.6.1",
		"description": "Pi skills and prompt templates for structured YAML artifact workflows: safe-start, codebase-recon, safe-change, architecture review, structured-doc validation, and legacy docs migration.",
		@@ -5,0 +5,0 @@ "license": "MIT",

+1

-1

skills/safe-change/references/docs-update.md

		# Structured Artifact Update Rules

		Update only canonical YAML owner artifacts under the resolved structured docs root. Treat them as current truth, not audit history. Resolve `<docs-root>` exactly: use repo-local `<workspace_root>/docs/agent/api` only when it already exists; otherwise canonicalize `workspace_root`, strip one leading slash/backslash, replace every slash, backslash, and colon with `-`, wrap with `--`, and use `~/.pi/agent/workspaces/<workspace-fingerprint>/docs/agent/api`. Remove resolved or superseded records by default; keep `stale`/`deprecated` records only when live references or active migrations require temporary continuity. Do not create/update Markdown except root `AGENTS.md` when `agent-operating-guide.yaml` changes and harness interoperability guidance must mirror it. Owner mapping: scopes, repo-inventory, validation-baseline, project-intent, architecture, data-flow, data-model, invariants, dependency-rules, design-issues, risk-register, contracts, testing-strategy, change-guide, adr, agent-operating-guide. Use the skill Structured Artifact Write/Update Protocol: read before write, preserve stable IDs, upsert by ID/source-of-truth fields, prune unreferenced resolved/superseded records, require evidence, validate refs, use deterministic YAML formatting, and report validation. Treat missing now-required schema fields in older artifacts as repair work, not as optional omissions.
		Update only canonical YAML owner artifacts under the resolved structured docs root. Treat them as current truth, not audit history. Resolve `<docs-root>` exactly: use repo-local `<workspace_root>/docs/agent/api` only when it already exists; otherwise canonicalize `workspace_root`, strip one leading slash/backslash, replace every slash, backslash, and colon with `-`, wrap with `--`, and use `~/.pi/agent/workspaces/<workspace-fingerprint>/docs/agent/api`. Remove resolved or superseded records by default; keep `stale`/`deprecated` records only when live references or active migrations require temporary continuity. Do not create/update Markdown except root `AGENTS.md` when `agent-operating-guide.yaml` changes and harness interoperability guidance must mirror it. Cross-check: when `change-guide.yaml` checklist:final-verification or `validation-baseline.yaml` recommended_order changes, review `agent-operating-guide.yaml` `validation_expectations` for consistency; the harness file derives from agent-operating-guide, not from the checklist artifact directly. Owner mapping: scopes, repo-inventory, validation-baseline, project-intent, architecture, data-flow, data-model, invariants, dependency-rules, design-issues, risk-register, contracts, testing-strategy, change-guide, adr, agent-operating-guide. Use the skill Structured Artifact Write/Update Protocol: read before write, preserve stable IDs, upsert by ID/source-of-truth fields, prune unreferenced resolved/superseded records, require evidence, validate refs, use deterministic YAML formatting, and report validation. Treat missing now-required schema fields in older artifacts as repair work, not as optional omissions.

pi-agent-codebase-workflows - npm Package Compare versions

Improved metrics