agent-doc-system 1.1.0 → 1.3.0

package/skills/agent-doc-system/references/create-migrate.md

@@ -33,16 +33,32 @@ agentdoc validate && agentdoc compile && agentdoc check
 
 `init` writes `agentdoc/agentdoc.config.yaml`, the central descriptor files
 (`domains.yaml`, `systems.yaml`, `apis.yaml`, `resources.yaml`),
-`agentdoc/journeys.yaml`, the documentation hierarchy under `docs/`, the
-observations README, and a CI workflow. It writes **project data only** — it
+`agentdoc/journeys.yaml`, the documentation hierarchy, the observations
+README, and a CI workflow. The documentation hierarchy goes to the configured
+`docs.product`, `docs.architecture`, `docs.constraints` and `docs.adrDir` when
+a configuration already exists, and to `agentdoc/docs/` when none does
+(authored AgentDoc material lives in `agentdoc/`, generated output in
+`.agentdoc/`; `docs/` stays the product's own documentation). To keep the
+skeleton in `docs/`, declare `docs.*` in `agentdoc/agentdoc.config.yaml`
+first. It writes **project data only** — it
 never copies the agentdoc implementation into the repository.
 
 In `agentdoc.config.yaml`:
 
 - Set `namespace`, fix `discovery.componentDescriptors` to match the real
-  layout, and enable the adapters for the technologies present. `adapters: []`
-  is a valid but useless starting point: with no adapter, a component
-  descriptor is an unsupported claim and compilation fails on purpose.
+  layout, and enable the adapters for the technologies present. `init`
+  pre-selects the language and deployment adapters whose manifests it finds:
+  `node`, `go`, `rust` and `python`, plus `dockerfile` and `wrangler`. It also
+  adds `database`, `openapi`, `events` and `github-actions`. Add the rest
+  (`pnpm`, `turborepo`, `typescript`, `protobuf`, `graphql`, `ansible`, …) when
+  the repository uses them. `adapters: []` is a valid but useless starting
+  point: with no adapter, a component descriptor is an unsupported claim and
+  compilation fails on purpose.
+- An existing catalog does not gain new adapters on upgrade. After upgrading
+  the CLI, compare `adapters:` with the technologies present, for example a
+  repository with `Cargo.toml` or `pyproject.toml` units and no `rust` /
+  `python` entry. Then run `agentdoc audit`: newly visible units appear as
+  `AGENTDOC_COVERAGE_ZERO` until they have a descriptor.
 - Three example authority rules are written **commented out**. Uncomment only
   the ones you can justify, with the rationale in your own words. An authority
   rule is a governance decision; the scaffolder does not make it for you.

package/templates/ci.yml

@@ -17,7 +17,7 @@ jobs:
         with: { node-version: '24' }
       - name: Install the agentdoc CLI
         # Unpinned tracks main. For CI reproducibility pin a tag or commit:
-        #   github:lbframe/agent-doc-system#v1.1.0
+        #   github:lbframe/agent-doc-system#v1.3.0
         # A compiler upgrade intentionally invalidates committed graphs.
         run: npm install -g github:lbframe/agent-doc-system
       - name: Validate and compile