ci: promote next to main

.claude-plugin/marketplace.json

@@ -73,7 +73,7 @@
     {
       "name": "aidd-telemetry",
       "source": "./plugins/aidd-telemetry",
-      "description": "Measurement: journals every session so a unit of work can be tied to what it cost. The hooks record on plain node; its three skills reach the `aidd` CLI to turn it on, answer and check.",
+      "description": "Measurement: counts the tokens of Claude Code sessions per task, ticket, model and day, locally. The hooks ask for a task on plain node; its two skills reach the `aidd` CLI to turn it on and answer.",
       "strict": true,
       "metadata": {
         "recommended": false

.claude/rules/01-standards/1-documentation.md

@@ -0,0 +1,20 @@
+---
+paths:
+  - "**/README.md"
+  - "**/ARCHITECTURE.md"
+  - "docs/**/*.md"
+  - "**/aidd_docs/memory/**/*.md"
+  - "**/GUIDELINES.md"
+  - "**/CONTRIBUTING.md"
+---
+
+# Concise documentation
+
+- Edit durable, authored Markdown individually; exclude history, generated content and fixtures.
+- Architecture: components, boundaries, flows, invariants. README: purpose, usage, limits.
+- Use descriptive, hierarchical headings; include only relevant facts, once per document.
+- Preserve contracts, decisions, rationale, limits, procedures, linked anchors and generator markers. Keep memory safeguards self-contained; never invent performance requirements.
+- Remove filler, repetition, narrated history, dates, counters, ticket/run IDs, snapshots, temporary evidence and measured timings, ratios or comparisons.
+- Prefer diagrams for relationships and tables for roles; keep necessary prose concise. Retain required versions, constants and useful examples.
+- State actions and verification commands; link canonical sources for supporting details.
+- Read back: check section scope, preserved information, commands and links.

.claude/rules/01-standards/2-tracker-ids.md

@@ -0,0 +1,3 @@
+# Tracker IDs
+
+- No dates or ticket/run IDs in code, comments, tests, CI or docs.

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/workflows/ci.yml

@@ -32,7 +32,7 @@ jobs:
 
       # `commitDepth: 1` lints the head commit, not the subject a squash merge gives `next`,
       # which GitHub defaults to the PR title. The title goes through the same config here.
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         if: github.event_name == 'pull_request'
         with:
           node-version: "22"
@@ -171,7 +171,7 @@ jobs:
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
 
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         with:
           node-version: "22"
 
@@ -289,7 +289,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - name: Install pnpm
         run: corepack enable
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         with:
           node-version: "22"
       # No kanban install: `cli/src/` names kanban nowhere and the bundle carries none of
@@ -309,7 +309,7 @@ jobs:
       # OIDC trusted publishing (npm CLI >= 11.5.1, Node >= 22.14.0), not a token, so no
       # NPM_TOKEN secret is needed. `npm publish` and not `pnpm publish`: pnpm's OIDC support
       # is unreliable, and npm's own CLI is the reference implementation for its own feature.
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+      - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         with:
           node-version: "22"
           registry-url: "https://registry.npmjs.org"

.github/workflows/codeql.yml

@@ -30,15 +30,15 @@ jobs:
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
 
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/init@24c54180a607b1449ed407dd24f251e4e9147c8d # v4.38.3
         with:
           languages: ${{ matrix.language }}
           queries: security-and-quality
 
       - name: Autobuild
-        uses: github/codeql-action/autobuild@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/autobuild@24c54180a607b1449ed407dd24f251e4e9147c8d # v4.38.3
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@1c5b675653bb5c22dbe9b12b556ec555138e09fd # v4.38.1
+        uses: github/codeql-action/analyze@24c54180a607b1449ed407dd24f251e4e9147c8d # v4.38.3
         with:
           category: "/language:${{ matrix.language }}"

.github/workflows/star-history.yml

@@ -30,7 +30,7 @@ jobs:
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
 
       - name: Setup Node
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         with:
           node-version: "22"
 

.github/workflows/validate.yml

@@ -22,16 +22,14 @@ jobs:
       CI: "true"
       # cli-ci.yml owns these three unconditionally, so running them again buys no coverage.
       # cli-type-honesty is deliberately NOT excluded: no cli-ci.yml job runs it, making this
-      # its only CI coverage. The exclusion is also why no `cli/` install runs below — the
-      # three hooks needing cli/node_modules are the three dropped, and every hook that stays
-      # reads `cli/` as text from the repository root.
+      # its only CI coverage. Recipe validation builds the CLI and needs its separate install.
       LEFTHOOK_EXCLUDE: "cli-biome,cli-architecture,cli-typecheck"
     steps:
       - name: Checkout
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
 
       - name: Setup Node
-        uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7.0.0
+        uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
         with:
           node-version: "22"
 
@@ -42,21 +40,23 @@ jobs:
         uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
         with:
           path: ~/.local/share/pnpm/store
-          key: pnpm-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
+          key: pnpm-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml', 'cli/pnpm-lock.yaml') }}
           restore-keys: pnpm-${{ runner.os }}-
 
       - name: Install dependencies
-        run: pnpm install --frozen-lockfile --ignore-scripts
+        run: |
+          pnpm install --frozen-lockfile --ignore-scripts
+          pnpm --dir cli install --frozen-lockfile --ignore-scripts
 
       - name: Run pre-commit hooks against the full tree
         run: pnpm exec lefthook run pre-commit --all-files --force
 
       # The generator hooks `git add` their output and never fail on drift, so a stale
-      # CATALOG.md, prompts doc or README count passes the step above in silence. Against
+      # CATALOG.md or README count passes the step above in silence. Against
       # HEAD, not the index: the generators already staged, so a plain `git diff` is empty.
       - name: Fail if a generated file drifted from what pre-commit regenerated
         run: |
-          if ! git diff --exit-code HEAD -- 'plugins/*/CATALOG.md' docs/prompts-documentation.md README.md; then
+          if ! git diff --exit-code HEAD -- 'plugins/*/CATALOG.md' README.md; then
             echo "::error::A generated file is stale. Run 'pnpm exec lefthook run pre-commit --all-files --force' locally and commit the result."
             exit 1
           fi

.gitignore

@@ -34,20 +34,11 @@ coverage/
 
 # AIDD CLI's own local state (install manifest, auth): machine-local, never
 # part of the project's own tracked content. config.json is the exception:
-# it is the committed telemetry switch (see .aidd/config.json and
-# aidd_docs/tasks/2026_08/2026_08_20_telemetry-export-enable/phase-1.md),
-# tracked so a fresh clone inherits the project's decision.
+# it is the committed project switch (see .aidd/config.json), tracked so a
+# fresh clone inherits the project's decision.
 .aidd/*
 !.aidd/config.json
 
-# AIDD run-journal records: where they land once .aidd/config.json turns
-# telemetry on (see plugins/aidd-telemetry/hooks/journal.js) - this
-# directory being committed is a location, not a permission. The records it
-# holds never are.
-aidd_docs/runs/*
-!aidd_docs/runs/.gitkeep
-!aidd_docs/runs/README.md
-
 # SpecStory captures (may contain transcripts / secrets)
 .specstory/
 

README.md

@@ -193,7 +193,7 @@ Three ways in — pick one:
 | --- | --- | --- |
 | 🧭 **Guided onboarding** | `/aidd-context:00-onboard` | First time, or unsure what to run — it inspects the project and routes you. |
 | 🧠 **Project memory** | `/aidd-context:02-project-memory` | Build the project memory bank by hand. |
-| ⚙️ **Feature flow** | `/aidd-orchestrator:01-sdlc` | Autonomously ship a feature end to end (frame → deliver → check → PR). |
+| ⚙️ **Feature flow** | `/aidd-orchestrator:01-sdlc` | Ship a feature end to end, autonomous by default or supervised with `interactive` (frame → deliver → check → PR). |
 
 The full loop, and how onboarding sets it up:
 
@@ -236,7 +236,7 @@ Start with a functional need or User Story, then track it as an issue or ticket
 before planning. Shipping follows the project's own delivery process. Capture a
 learning only when it is durable enough to improve the next feature.
 
-> 🍳 **More flows** → bundled recipes: [start a project](plugins/aidd-context/skills/12-cook/assets/recipes/start-a-project.md), [ship a feature](plugins/aidd-context/skills/12-cook/assets/recipes/ship-a-feature.md), and more.
+> 🍳 **More flows** → bundled recipes: [MCP installations](plugins/aidd-context/skills/12-cook/assets/recipes/mcp-installation.md), [token optimization](plugins/aidd-context/skills/12-cook/assets/recipes/token-optimization.md), and [installing AIDDy](plugins/aidd-context/skills/12-cook/assets/recipes/install-aiddy-in-codex.md).
 
 ## 🧩 Plugins
 
@@ -266,7 +266,7 @@ Code transformation: plan, implement, assert, audit, review, test, refactor, deb
 
 ### 🌿 [aidd-vcs](plugins/aidd-vcs/README.md)
 
-`5 skills` · stable
+`6 skills` · stable
 
 Repo init, commits, pull / merge requests, release tags, issues.
 
@@ -315,9 +315,9 @@ UI / UX design — smoke-test only, not ready for use.
 
 ### 📈 [aidd-telemetry](plugins/aidd-telemetry/README.md) 🧪
 
-`3 skills` · **beta**
+`2 skills` · **beta**
 
-Answers what a piece of work cost — tokens, models, and which skill spent them. The switch is git-tracked, so it applies to everyone who clones; opt out per person with `AIDD_TELEMETRY=0`. Nothing leaves your machine.
+Counts the tokens of Claude Code sessions per task, ticket, model and day. Opt-in, and local to your machine.
 
 </td>
 <td width="33%" valign="top">
@@ -338,10 +338,10 @@ Full catalog → [`CATALOG.md`](docs/CATALOG.md).
 
 | | |
 | --- | --- |
-| 🍳 **Recipes** | Bundled how-to sheets: [start a project](plugins/aidd-context/skills/12-cook/assets/recipes/start-a-project.md), [ship a feature](plugins/aidd-context/skills/12-cook/assets/recipes/ship-a-feature.md), [MCP installations](plugins/aidd-context/skills/12-cook/assets/recipes/mcp-installation.md), [token optimization](plugins/aidd-context/skills/12-cook/assets/recipes/token-optimization.md). Project recipes created by cook live in `aidd_docs/recipes/`. |
+| 🍳 **Recipes** | Bundled how-to sheets: [MCP installations](plugins/aidd-context/skills/12-cook/assets/recipes/mcp-installation.md), [token optimization](plugins/aidd-context/skills/12-cook/assets/recipes/token-optimization.md), [install AIDDy](plugins/aidd-context/skills/12-cook/assets/recipes/install-aiddy-in-codex.md). Project recipes created by cook live in `aidd_docs/recipes/`. |
 | 🏛️ **[Architecture](docs/ARCHITECTURE.md)** | How the framework composes: plugins, skills, hooks, agents. |
 | 🧩 **[Create a plugin](docs/CREATE_PLUGIN.md)** | Build and publish your own. |
-| 🛒 **[Marketplace](docs/MARKETPLACE.md)** | Install scopes, versioning, LLM tiers. |
+| 🛒 **[Marketplace](docs/MARKETPLACE.md)** | Install scopes and versioning. |
 | ❓ **[FAQ & Troubleshooting](docs/FAQ.md)** · **[Glossary](docs/GLOSSARY.md)** | Common questions, fixes, and terms. |
 
 ## 🔒 Trust and safety

aidd_docs/README.md

@@ -104,7 +104,7 @@ AIDD is delivered as a plugin marketplace. Pick what you need; do not install ev
 | ------------ | ------------------------------------------------------------------------------------------------------------------- |
 | aidd-context | 00-onboard, 01-bootstrap, 02-project-memory, 03-context-generate, 09-mermaid, 10-learn, 11-explore                    |
 | aidd-refine  | 01-brainstorm, 02-challenge, 03-shadow-areas, 04-fact-check                                                        |
-| aidd-dev     | 01-plan, 02-implement, 03-assert, 04-audit, 05-review, 06-test, 07-refactor, 08-debug, 09-for-sure, 10-todo       |
+| aidd-dev     | 01-plan, 02-implement, 03-assert, 04-audit, 05-review, 06-test, 07-refactor, 08-debug, 09-for-sure, 10-batch       |
 | aidd-orchestrator | 00-async-dev, 01-sdlc                                                                                         |
 | aidd-vcs     | 01-commit, 02-pull-request, 03-release-tag, 04-issue-create                                                         |
 | aidd-pm      | 01-ticket-info, 02-user-stories, 03-prd, 04-spec, 05-spike, 06-product-brief, 07-epic, 08-three-amigos, 09-defect, 10-task |

aidd_docs/memory/architecture.md

@@ -33,7 +33,7 @@ flowchart LR
 | Concern decides placement, not existence | a missing capability goes to the plugin whose concern owns it; the caller delegates |
 | A skill is a router | `SKILL.md` dispatches to actions or protocols; the only place a capability is addressed by name |
 | Recipe skills discover providers at runtime | by description matching. Only agent permission lists and orchestration references name a provider |
-| Observation is its own layer | `aidd-telemetry` journals what a session did; it never reads or writes application source |
+| Observation is its own layer | `aidd-telemetry` counts what a session consumed, from the task a person declared; it never reads or writes application source |
 | A launcher runs an external binary, never embeds it | `kanban` broke that and was unwired. Detail in the CLI bank |
 
 The concern-to-plugin taxonomy is canonical in [`docs/ARCHITECTURE.md`](../../docs/ARCHITECTURE.md).
@@ -42,4 +42,4 @@ The concern-to-plugin taxonomy is canonical in [`docs/ARCHITECTURE.md`](../../do
 
 - 9 plugins ship, 3 off the curated install path: `aidd-ui` is alpha, `aidd-telemetry` beta and opt-in, `aidd-qa` new and unproven outside this repository.
 - A skill never links outside itself: the tree ships both flat and as a marketplace, so no relative path survives both.
-- Bundled hooks run Node. No `node` on `PATH`, no memory refresh and no run journal.
+- Bundled hooks run Node. No `node` on `PATH`, no memory refresh and no question about the task.

aidd_docs/memory/cli.md

@@ -7,8 +7,8 @@ The `aidd` binary, built from `cli/` and published to npm as `@ai-driven-dev/cli
 ## Commands
 
 - Eleven groups: `setup`, `framework`, `translate`, `plugin`, `marketplace`, `auth`, `sync`, `update`, `doctor`, `clean`, `telemetry`.
+- `telemetry` counts the tokens of Claude Code sessions locally: [usage contract](../product/usage-contract.md).
 - No list here. The surface moves; `aidd --help` is the only reading that stays true.
-- `telemetry`'s sink, run journal, record shapes, report axes and per-tool declarations: [`cli/aidd_docs/memory/telemetry.md`](../../cli/aidd_docs/memory/telemetry.md).
 
 ## Interface
 

aidd_docs/memory/codebase-map.md

@@ -38,7 +38,6 @@ flowchart TD
 | Binary | `cli/src/cli.ts` → `dist/cli.js`, bin name `aidd` |
 | Workflow | `plugins/<plugin>/skills/<NN>-<name>/SKILL.md` |
 | Memory refresh | `plugins/aidd-context/hooks/update_memory.js`, on `SessionStart` |
-| Run journal | `plugins/aidd-telemetry/hooks/journal.cjs`, on `SessionStart`, `Stop`, `PostToolUse` |
 
 ## Packages
 

aidd_docs/memory/coding-assertions.md

@@ -29,7 +29,7 @@ Never state in a commit message or a report anything not just observed in output
 | 1 | `pnpm exec lefthook run pre-commit` | JSON and YAML validity, `scripts/` tests, skill frontmatter and argument hints, cross-plugin orthogonality and router coherence (`scripts/check-architecture-rules.js`), context imports and reference form, markdown links, the paths the prose names and a sentence written in two documents (`scripts/check-doc-duplication.js`); `cli` lint, architecture, typecheck and type honesty when `cli/` changed. `cli` knip and the full `cli` suite are pre-push, not pre-commit — see below |
 | 2 | `pnpm exec commitlint --edit` | the message against `commitlint.config.cjs` |
 
-Same hook regenerates each plugin's `CATALOG.md`, the README counts and `docs/prompts-documentation.md`, and stages them.
+Same hook regenerates each plugin's `CATALOG.md`, and the README counts, and stages them.
 
 Every `cli` job is globbed on `cli/**`. A change under `kanban/` alone fires no local job; run `cd kanban && pnpm test` by hand. CI does cover it — `cli-ci.yml`'s `kanban-checks`, see `deployment.md`.
 
@@ -51,6 +51,8 @@ Each runs through `scripts/gate-witness.js`, which skips a gate this exact tree
 - Any pull request fires `ci.yml` and `cli-ci.yml`, whatever its base.
 - Only a pull request targeting `main` or `next` replays the pre-commit, and `validate.yml` drops `cli-biome`, `cli-architecture` and `cli-typecheck` from it.
 
+Deleting a remote branch is the one push to send with it. `git push --delete` carries no commit, and the gates still run: measured, lefthook forwards git's pre-push stdin to no command, the hook environment is byte-identical to a normal push, and a `glob` filter matches anyway. Nothing inside the hook can tell the two apart, so the full `cli` suite runs over a push that has nothing to validate.
+
 ## Behavior
 
 Done means every gate green. On failure, one agent per failing assertion — typecheck, tests, rules — not one agent for all.

aidd_docs/memory/deployment.md

@@ -9,7 +9,7 @@ Where the project runs and how it ships: CI/CD, environments, and release.
 | Workflow | Runs |
 | --- | --- |
 | `ci.yml` | commitlint on pull requests and on `main`'s tip, plus the PR title itself — the subject a squash merge uses — then release-please on `main` and the release jobs |
-| `cli-ci.yml` | the `cli` and `kanban` gates — job list in the CLI bank. No `paths:` filter, deliberately: it runs on every push and pull request, and a `changes` job decides in bash whether the rest has anything to do — `cli/**`, `kanban/**`, `scripts/__tests__/**`, `README.md`, the workflow file itself, and `plugins/aidd-telemetry/**` except its `*.md` prose. Mutations skip only for a same-repository numeric `promote/next-to-main-*` snapshot whose `cli / gate` passed in a successful `next` push and whose PR merge tree equals that snapshot with `main` already its ancestor; the resulting `main` push reuses it only for that exact two-parent promotion merge when its tree, associated merged PR, and source snapshot all match. Missing, failed, unreadable, or mismatched Git/API proof keeps normal mutation scopes. All non-mutation checks still run on the current PR merge ref or `main` commit. |
+| `cli-ci.yml` | the `cli` and `kanban` gates — job list in the CLI bank. No `paths:` filter, deliberately: it runs on every push and pull request, and a `changes` job decides in bash whether the rest has anything to do — `cli/**`, `kanban/**`, `scripts/__tests__/**`, `README.md`, the workflow file itself. Mutations skip only for a same-repository numeric `promote/next-to-main-*` snapshot whose `cli / gate` passed in a successful `next` push and whose PR merge tree equals that snapshot with `main` already its ancestor; the resulting `main` push reuses it only for that exact two-parent promotion merge when its tree, associated merged PR, and source snapshot all match. Missing, failed, unreadable, or mismatched Git/API proof keeps normal mutation scopes. All non-mutation checks still run on the current PR merge ref or `main` commit. |
 | `validate.yml` | plugin and marketplace manifests against their schemas, plus the whole pre-commit over the whole tree |
 | `codeql.yml` | code scanning |
 | `promote.yml` | opens the `next` to `main` promote PR, merge auto-merge |