forgedock 1.1.1 → 1.1.3

package/docs/CODEX.md

@@ -8,7 +8,7 @@ Shared source:
 - `commands/**/*.md` remains the workflow spec for both runtimes
 
 Claude wrapper:
-- `install.sh` symlinks command files into `~/.claude/commands`
+- `install.sh` symlinks command files into the current project directory by default; pass `--global` to install into `~/.claude/commands/` for all projects
 
 Codex wrapper:
 - `install-codex.sh` generates namespaced skills in `~/.codex/skills`
@@ -84,6 +84,41 @@ trust_level = "trusted"
 
 The installer does not modify global trust settings automatically.
 
+## Conformance Verification
+
+The Codex adapter produces and consumes the same FORGE annotation wire format as the Claude Code path. `scripts/conformance-check.mjs` validates annotation output from any producer (Claude Code, Codex, Cursor, or fixtures) against the FORGE Annotation Protocol v1.0 (`docs/spec/forge-protocol-v1.md`).
+
+### Running the check
+
+Pipe real or fixture-captured Codex-adapter-produced FORGE comments into the script:
+
+```bash
+# Validate a fixture file containing FORGE annotation blocks
+node scripts/conformance-check.mjs docs/spec/fixtures/codex-adapter-annotations.md
+
+# Validate live annotations from a merged PR (replace 1234 with the PR number)
+gh api repos/RapierCraftStudios/ForgeDock/issues/1234/comments \
+  --jq '[.[].body]' \
+  | node scripts/conformance-check.mjs -
+
+# Validate all comments on recent merged PRs (last 10)
+gh pr list -R RapierCraftStudios/ForgeDock --state merged --limit 10 --json number \
+  --jq '.[].number' | while read pr; do
+    gh api "repos/RapierCraftStudios/ForgeDock/issues/$pr/comments" \
+      --jq '[.[].body]'
+done | node scripts/conformance-check.mjs -
+```
+
+Exit code 0 = all annotations conform. Exit code 1 = violations found (see output for details). Unrecognized annotation types are tolerated per spec §7.2 (WARN, not FAIL). An annotation explicitly marked `:PARTIAL` is also reported as a WARN, not a failure — only a fully missing/interrupted completion sentinel fails the exit code. (The reference `validate()` in `@forgedock/protocol` still reports `valid: false` for PARTIAL annotations per §3.2 — that strict signal is for library consumers deciding whether data is safe to treat as complete, not for this CLI's pass/fail gate.)
+
+### Re-running when the adapter changes
+
+Run the conformance check any time `.agents/skills/` adapter files are modified or after a new release of the spec. Conformance gaps found must be documented as follow-up GitHub issues (findings become issues per repo convention), not silently patched inline.
+
+### Verified implementation claim
+
+The Codex adapter path (`.agents/skills/*/SKILL.md` + `commands/*.md`) is a proven second implementation of the FORGE Annotation Protocol. Both the Claude Code path and the Codex adapter path produce annotations that pass `scripts/conformance-check.mjs`. See `docs/spec/forge-protocol-v1.md` Section 11 for the vendor-neutrality acknowledgement.
+
 ## Usage Notes
 
 - Use the installed `forge` skill as the overview/router entrypoint.

package/docs/CONFIG.md

@@ -334,7 +334,7 @@ review:
 
 Path configuration for the devdocs knowledge tree. Pipeline agents (work-on, review-pr, etc.) read these files as **authoritative project knowledge** before acting.
 
-Run `npx forgedock docs init` to scaffold the tree from ForgeDock's seed templates into the configured path.
+Create the devdocs tree by copying the seed templates from `devdocs/templates/` (in this repo) into your configured path, or scaffold it manually by creating `devdocs/project/architecture.md`, `devdocs/agent/using-forgedock.md`, and an optional `devdocs/index.yaml`.
 
 ```yaml
 devdocs:
@@ -345,9 +345,9 @@ devdocs:
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
 | `path` | string (relative path) | No | Path to the devdocs tree, relative to project root. Default: `devdocs`. |
-| `index_path` | string (relative or absolute path) | No | Path to the selective loading index file. Default: `{path}/index.yaml`. When the index file exists at this path, agents read it first (~400 tokens) and load only docs whose domain matches the current issue's labels. When absent, agents fall back to loading all docs with `applies_to: work-on` (backward compatible). Scaffold the index with `npx forgedock docs init`. |
+| `index_path` | string (relative or absolute path) | No | Path to the selective loading index file. Default: `{path}/index.yaml`. When the index file exists at this path, agents read it first (~400 tokens) and load only docs whose domain matches the current issue's labels. When absent, agents fall back to loading all docs with `applies_to: work-on` (backward compatible). Create the index manually or copy the seed template from `devdocs/templates/`. |
 
-**Commands that use this section**: `docs init`, `work-on/build/context` (Phase C-1), `work-on/build/architect` (Phase A0)
+**Commands that use this section**: `work-on/build/context` (Phase C-1), `work-on/build/architect` (Phase A0)
 
 ### Selective Loading (index.yaml)
 
@@ -366,14 +366,11 @@ When `devdocs/index.yaml` exists, agents use **domain-filtered selective loading
 
 **Backward compatibility**: If `index.yaml` is absent, behavior is unchanged — all docs with `applies_to: work-on` are loaded. No migration required for existing devdocs trees.
 
-Scaffold the index with:
-```bash
-npx forgedock docs init
-```
+Scaffold the index manually by creating `devdocs/index.yaml` (or copy the seed template from `devdocs/templates/` in the ForgeDock repo).
 
 ### Migration from `review.context`
 
-If you previously stored project context in `forge.yaml → review.context`, move that content into the appropriate devdocs file after running `npx forgedock docs init`:
+If you previously stored project context in `forge.yaml → review.context`, move that content into the appropriate devdocs file:
 
 | `review.context` content | Target devdocs file |
 |--------------------------|---------------------|