@felixdotgo/aidlc-kit 0.0.1 → 0.1.0

package/docs/testing-and-release.md

@@ -1,5 +1,7 @@
 # Testing and release
 
+Loop changes should run the focused client assignment, graph, Git, remote-state, and `loop-*.test` fixtures, then lifecycle gate/conformance tests and package smoke. Verify in-conversation gate stop, later client resume, concurrent worker claims, lease expiry, exact-session recovery, Git scope checks, remote reviewer approval, and run bounds before aggregate `npm test` and `npm run lint`. Fleet persistence needs PostgreSQL integration coverage as well as in-memory/SQLite fixtures.
+
 Use the smallest relevant verification while developing, then complete the repository checks before a release review.
 
 ## Standard verification
@@ -25,6 +27,45 @@ node --test dist/test/unit/installer.test.js
 
 Choose the test closest to the changed boundary. For example, use installer tests for package inventory or documentation assertions, upgrade tests for migration semantics, and lifecycle-runtime tests when touching installed scripts. Continuation changes must also run `continuation-guard`, multi-item lifecycle runtime, context, and local/MCP lifecycle conformance coverage.
 
+## Loop, Docker, and PostgreSQL verification
+
+Loop orchestration tests are part of `npm test`. The ones that exercise real container isolation gate on fixture images plus environment flags; build the fixtures once with a local Docker daemon:
+
+```sh
+docker build -q -t aidlc-worker-isolation-test:local test/fixtures/docker/worker-isolation
+docker build -q -t aidlc-worker-multiturn-test:local test/fixtures/docker/worker-multiturn
+docker build -q -t aidlc-worker-fleet-e2e-test:local test/fixtures/docker/worker-fleet-e2e
+
+AIDLC_TEST_DOCKER=1 \
+AIDLC_TEST_WORKER_IMAGE=aidlc-worker-isolation-test:local \
+AIDLC_TEST_MULTITURN_IMAGE=aidlc-worker-multiturn-test:local \
+AIDLC_TEST_DOCKER_IMAGE=aidlc-worker-isolation-test:local \
+AIDLC_WORKER_DOCKER_IMAGE=aidlc-worker-fleet-e2e-test:local \
+npm test
+```
+
+- `AIDLC_TEST_DOCKER=1` builds and runs the adversarial lead-boundary container: the isolated lead must not write source or see lifecycle state, the Docker socket, host HOME, or reviewer credentials.
+- `AIDLC_TEST_WORKER_IMAGE` and `AIDLC_TEST_DOCKER_IMAGE` run the isolated Docker worker through the local batch dispatcher and the fleet Git handoff.
+- `AIDLC_TEST_MULTITURN_IMAGE` runs the multi-turn session HOME fixture against the turn limit.
+- `AIDLC_WORKER_DOCKER_IMAGE` is required on Linux for the real fleet end-to-end test (coordinator dispatch, isolated worker, Git integration, canonical completion, and G2 publication). Without it that test fails closed instead of skipping.
+
+Each fixture image contains only a fake provider CLI that emits the Codex JSONL protocol; no real Codex, Claude Code, or OpenCode credentials or accounts are used, and the fake refuses to run when it can see `.git`, lifecycle state, or the Docker socket.
+
+Without these variables the Docker-gated tests skip, so a plain `npm test` is not loop-isolation verification.
+
+PostgreSQL fleet coverage runs against a real database and is not part of `npm test`:
+
+```sh
+docker run -d --rm --name aidlc-pg-test -e POSTGRES_PASSWORD=test -p 127.0.0.1:5433:5432 postgres:16-alpine
+docker exec aidlc-pg-test pg_isready -U postgres # repeat until ready
+TEST_POSTGRES_URL=postgres://postgres:test@127.0.0.1:5433/postgres \
+  node --test services/aidlc-coordination/test/*.test.mjs
+docker stop aidlc-pg-test
+```
+
+Without `TEST_POSTGRES_URL` the PostgreSQL tests skip with SQLite coverage still running; run the coordination service suites separately whenever `services/aidlc-coordination/` changes.
+
+
 ## Package smoke test
 
 Release verification must exercise the tarball rather than the source tree. From the repository root, build and pack locally, extract the archive, then run the extracted CLI against a clean temporary consumer project.
@@ -57,17 +98,19 @@ node dist/dev/evaluator/cli.js list
 node dist/dev/evaluator/cli.js run --runner local-simulated
 ```
 
-Runners exchange JSON, and reports capture transport, transcript, normalised events, usage, and diagnostics. Real Codex or Claude runs can consume credentials and model budget; they are not required for ordinary development verification.
+Runners exchange JSON, and reports capture transport, transcript, normalised events, usage, and diagnostics. Real Codex, Claude Code, or OpenCode runs can consume credentials and model budget; they are not required for ordinary development verification.
+
+The pinned `opencode-gpt6` runner uses adapter `opencode` with model `opencode-go/gpt-6-luna`, version `opencode-2.2.0`, protocol version `2`, real evidence, and a 300000 ms timeout. It runs `opencode run --format json --standalone --auto` once per turn, resumes with `--session`, and writes `opencode.json` containing `{"mcp": {}}` into each scenario workspace so project MCP servers do not leak into the evaluation. OpenCode resolves its project directory from the inherited `PWD`, not the spawned process working directory, so the runner and the loop driver pin `PWD` to the workspace; without that pin, commands would silently run in the invoking repository. OpenCode has no environment-credential mode, so the runner reuses the local Console authentication; the residual risk is that user plugins or agents can still load. That isolation is workspace configuration, not a security boundary.
 
-The release-eligible suite includes `build-multi-item-continuation`, which starts with three canonical build items and requires one agent run to complete all of them, record verification/review evidence, and stop only at a ready G2. This complements unit guards by exercising the model-facing continuation contract.
+The release-eligible `aidlc-official-agentic` suite is version `2.5.0`. Its `supported-adapters` scenario asks the agent to explain that the workflow supports Codex, Claude Code, and OpenCode without executing remote code or shell strings. The suite also includes `build-multi-item-continuation`, which starts with three canonical build items and requires one agent run to complete all of them, record verification/review evidence, and stop only at a ready G2. This complements unit guards by exercising the model-facing continuation contract.
 
-The release checker validates required evidence according to the configured adapter policy. This repository's script uses the Codex-only policy:
+The release checker validates required evidence according to the configured adapter policy. This repository's script uses the OpenCode-only policy:
 
 ```sh
 npm run release:check
 ```
 
-It reads local evaluation evidence from `.agents/project/release-eval.json` and fails closed if required evidence or integrity thresholds are missing.
+The script passes `--adapters opencode`, while `dev/evaluator/release.ts` keeps its `["codex","claude"]` default for compatibility so downstream users and existing policies are unaffected. It reads local evaluation evidence from `.agents/project/release-eval.json` and fails closed if required evidence or integrity thresholds are missing. Re-adding Codex or Claude to this repository's policy requires fresh real evidence for those adapters, not a policy-only edit.
 
 ## Release readiness
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@felixdotgo/aidlc-kit",
-  "version": "0.0.1",
+  "version": "0.1.0",
   "description": "Install a local, agent-adapted AI-DLC workflow into a project.",
   "keywords": [
     "ai-dlc",
@@ -37,7 +37,7 @@
     "build": "node scripts/build-assets.mjs && tsc -p tsconfig.json",
     "test": "npm run build && node --test dist/test/unit/*.test.js",
     "lint": "tsc --noEmit -p tsconfig.json",
-    "release:check": "node dist/dev/evaluator/release-check.js .agents/project/release-eval.json --adapters codex",
+    "release:check": "node dist/dev/evaluator/release-check.js .agents/project/release-eval.json --adapters opencode",
     "prepublishOnly": "npm test && npm run lint && npm run release:check"
   },
   "engines": {