agentdeck-sdk 5.0.3__tar.gz → 5.2.0__tar.gz

agentdeck_sdk-5.2.0/.agents/skills/release/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: release
+description: Cut an agentdeck release  -  bump version, update CHANGELOG, merge dev to main, and tag vX.Y.Z.
+---
+
+# Release agentdeck
+
+Follow the release process strictly. All work starts on `dev`; `main` is release-only,
+and `dev` is the repository's default branch.
+
+## Two PRs, two issues
+
+A release needs two labeled `chore` issues and two PRs, not one of each.
+
+| PR | base | issue | closing keyword |
+|---|---|---|---|
+| bump | `dev` | its own labeled `chore` issue | `Closes #N`, works: `dev` is default |
+| promotion | `main` | its own labeled `chore` issue | `Refs #N` only, close by hand: `main` is not default, so GitHub never creates the closing reference |
+
+`git push origin dev` is rejected directly ("push declined due to repository rule violations").
+The bump goes through its own PR into `dev`.
+
+## Release Steps
+
+1. **Version:** Confirm SemVer bump (`pyproject.toml` and `CHANGELOG.md`).
+2. **Preflight:** Verify clean working tree, non-empty `[Unreleased]` section, and `make check`
+   is 100% green. Run it unpiped (`make check`, not `make check | tail`) so its own exit code is
+   what you read; a pipe reports the last command's status, not the gate's.
+3. **Bump PR into `dev`:**
+   - Update `version` in `pyproject.toml`.
+   - Move Unreleased entries to `## [X.Y.Z] - YYYY-MM-DD` in `CHANGELOG.md` with compare links.
+   - Run `python scripts/generate_docs_reference.py` once, then verify
+     `python scripts/generate_docs_reference.py --check`.
+   - Commit: `chore(release): vX.Y.Z`. Open the PR against the labeled bump issue
+     (`Closes #N`), wait for every required check, merge.
+4. **Promotion PR, `dev` to `main`:** Open it against the labeled promotion issue (`Refs #N`).
+   `Issue hygiene`, `slop`, and `Check affected documentation` skip themselves on a `main`-based
+   PR: each already ran the real per-PR version of itself against `dev` at merge time, and this
+   diff is the whole release cycle re-evaluated, not a new change. Wait for `check` and
+   `Build documentation`, then merge and close the promotion issue by hand.
+5. **Tag:** `git tag vX.Y.Z && git push origin vX.Y.Z`. `release.yml` publishes to PyPI on this
+   push; there is no undo once the tag lands.
+6. **Deploy:** In the `prod/` worktree (detached on a tag on purpose, so the public only sees
+   something released), run `./deploy-prod.sh vX.Y.Z`. It rebuilds `docs-site`, restarts
+   `agentdeck-docs-static.service`, and health-checks `127.0.0.1:4321`.
+7. **Report:** Return the GitHub release URL.
+
+## Ground Rules
+- Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.claude/agents/deck-dev.md

@@ -9,10 +9,12 @@ You implement one agentdeck GitHub issue end-to-end in an isolated worktree and
 
 **Objective: implement the issue with the smallest coherent change.** Order of preference: reuse an existing abstraction, modify one, consolidate/delete, and only then create. Your PR will be evaluated on: reuse of existing abstractions, consistency with `docs/patterns/`, minimal new concepts, minimal public surface, no narrating comments, no structural regression.
 
-**First action:** invoke the `ship-pr` skill and follow it. Every stage, the design gate, the self-review questions and the coverage question, the gate commands, live there. Do not rely on description-based auto-triggering here; call it explicitly.
+**First action:** read `.claude/skills/ship-pr/SKILL.md` and its `references/`, and follow it. Every stage, the design gate, the self-review questions and the coverage question, the gate commands, live there. The `Skill` tool is not invocable from a subagent; read the file directly rather than calling it.
 
 **Progress:** name each stage (Understand / Design / Implement / Self-review / Gate) as you enter it. A silent multi-stage run reads as a stall.
 
+**Denied tool calls:** a denial is a stop to report, never an obstacle to route around through a different tool or command.
+
 **Subagents:** any agent you spawn passes an explicit `model: "sonnet"`. Never omit it, never fable, never opus.
 
 **Output style:** ≤25 words between tool calls; final response ≤100 words unless more detail is required.

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.claude/agents/deck-reviewer.md

@@ -7,10 +7,12 @@ isolation: worktree
 
 You review one agentdeck PR as the merge gate. REVIEW ONLY on the code: never push a commit anywhere. You DO write review artifacts: the PR review itself, inline comments, and any DEFER, harness-note or Harvest issue.
 
-**First action:** invoke the `review-pr` skill and follow it. Everything procedural, the phases, the finding classes, the verdict format, the delivery mechanics, lives there. Do not rely on description-based auto-triggering here; call it explicitly.
+**First action:** read `.claude/skills/review-pr/SKILL.md` and its `references/`, and follow it. Everything procedural, the phases, the finding classes, the verdict format, the delivery mechanics, lives there. The `Skill` tool is not invocable from a subagent; read the file directly rather than calling it.
 
 **Progress:** say which phase you are entering as you enter it. A silent review reads as a stall.
 
+**Denied tool calls:** a denial is a stop to report, never an obstacle to route around through a different tool or command.
+
 **Subagents:** any agent you spawn passes an explicit `model: "sonnet"`. Never omit it, never fable, never opus.
 
 **Output style:** keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

agentdeck_sdk-5.2.0/.claude/skills/release/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: release
+description: Cut an agentdeck release  -  bump version, update CHANGELOG, merge dev to main, and tag vX.Y.Z.
+---
+
+# Release agentdeck
+
+Follow the release process strictly. All work starts on `dev`; `main` is release-only,
+and `dev` is the repository's default branch.
+
+## Two PRs, two issues
+
+A release needs two labeled `chore` issues and two PRs, not one of each.
+
+| PR | base | issue | closing keyword |
+|---|---|---|---|
+| bump | `dev` | its own labeled `chore` issue | `Closes #N`, works: `dev` is default |
+| promotion | `main` | its own labeled `chore` issue | `Refs #N` only, close by hand: `main` is not default, so GitHub never creates the closing reference |
+
+`git push origin dev` is rejected directly ("push declined due to repository rule violations").
+The bump goes through its own PR into `dev`.
+
+## Release Steps
+
+1. **Version:** Confirm SemVer bump (`pyproject.toml` and `CHANGELOG.md`).
+2. **Preflight:** Verify clean working tree, non-empty `[Unreleased]` section, and `make check`
+   is 100% green. Run it unpiped (`make check`, not `make check | tail`) so its own exit code is
+   what you read; a pipe reports the last command's status, not the gate's.
+3. **Bump PR into `dev`:**
+   - Update `version` in `pyproject.toml`.
+   - Move Unreleased entries to `## [X.Y.Z] - YYYY-MM-DD` in `CHANGELOG.md` with compare links.
+   - Run `python scripts/generate_docs_reference.py` once, then verify
+     `python scripts/generate_docs_reference.py --check`.
+   - Commit: `chore(release): vX.Y.Z`. Open the PR against the labeled bump issue
+     (`Closes #N`), wait for every required check, merge.
+4. **Promotion PR, `dev` to `main`:** Open it against the labeled promotion issue (`Refs #N`).
+   `Issue hygiene`, `slop`, and `Check affected documentation` skip themselves on a `main`-based
+   PR: each already ran the real per-PR version of itself against `dev` at merge time, and this
+   diff is the whole release cycle re-evaluated, not a new change. Wait for `check` and
+   `Build documentation`, then merge and close the promotion issue by hand.
+5. **Tag:** `git tag vX.Y.Z && git push origin vX.Y.Z`. `release.yml` publishes to PyPI on this
+   push; there is no undo once the tag lands.
+6. **Deploy:** In the `prod/` worktree (detached on a tag on purpose, so the public only sees
+   something released), run `./deploy-prod.sh vX.Y.Z`. It rebuilds `docs-site`, restarts
+   `agentdeck-docs-static.service`, and health-checks `127.0.0.1:4321`.
+7. **Report:** Return the GitHub release URL.
+
+## Ground Rules
+- Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.claude/skills/review-pr/SKILL.md

@@ -75,10 +75,9 @@ Every comment and the verdict body follow fixed templates: `references/templates
 - Reviews are COMMENTED only. Approve and request-changes are unavailable when the agent authenticates as the PR author.
 - Inline, line-anchored comments (BLOCK, DISCUSS, DEFER; NITs never inline) in Template A form:
   `gh api repos/{owner}/{repo}/pulls/<n>/comments -f body=... -f commit_id=$(gh pr view <n> --json headRefOid -q .headRefOid) -f path=<file> -F line=<line> -f side=RIGHT`
-- Post the verdict as a real review in Template B form: `gh pr review <n> --comment --body-file <file>`. Pass requires zero BLOCK and every DISCUSS answered. The marker applies only to the reviewed head commit; any later push needs a new one.
-- If the only change since the last pass is a NIT fix or a PR body edit, post a one-line re-stamp review at the new SHA instead of a full re-review. It still ends with the marker line; the gate matches the last review at `HEAD_SHA` regardless of length.
-- After posting the marked review, rerun the trusted gate: extract the run ID from the `Agent review` check URL (`gh pr checks <n> --json name,link`), then `gh run rerun <run-id>`. The gate only runs from base-branch workflow code, so a review submission does not trigger it directly.
-- Confirm the `Agent review` check turns green after a pass. A local pass with no green check is incomplete.
+- Post the verdict as a real review in Template B form: `gh pr review <n> --comment --body-file <file>`. Pass requires zero BLOCK and every DISCUSS answered.
+- The review is only delivered once it is on the PR. A local pass with nothing posted is incomplete.
+- A push that changes the code needs a new review: nothing enforces that mechanically, so it is on whoever merges.
 - File DEFER and harness-note issues per the finding-class table above.
 
 ## Return to the orchestrator

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.claude/skills/review-pr/references/templates.md

@@ -1,8 +1,7 @@
 # Report templates
 
 Every review output falls into one of three templates. Low freedom: this is the narrow bridge,
-not the open field. A script parses Template B's marker line, so structure, length, and style are
-fixed here; do not paraphrase the numbers.
+not the open field. Structure, length and style are fixed here; do not paraphrase the numbers.
 
 Contents: Template A (inline comment), Template B (verdict), worked examples, Template C
 (orchestrator return), style rules, why the numbers are these numbers.
@@ -52,15 +51,14 @@ ALWAYS use this exact template structure:
     - `service.py:12` ...
     </details>
 
-    <!-- agentdeck-review: pass --> (0 BLOCK, 1 DISCUSS answered, 1 DEFER #431, 4 NIT)
+    0 BLOCK, 1 DISCUSS answered, 1 DEFER #431, 4 NIT
 
 - **300 words maximum**, excluding the rubric table and the collapsed NIT block.
 - **Per finding: 25 words. A DISCUSS gets 35**, because it carries `Settled by:`.
 - Sections in exactly this order. **An empty section is omitted entirely**, never written as
   "None".
 - NITs are always inside the `<details>` block and never inline on the diff.
-- The marker line is last, alone, and exactly as specified (`<!-- agentdeck-review: pass -->` or
-  `block`, with the counts). A scorecard greps it.
+- The counts line is last and alone, so the verdict is legible without reading the findings.
 
 ## Worked examples
 

agentdeck_sdk-5.2.0/.claude/skills/ship-issue/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: ship-issue
+description: "Run one agentdeck issue through the full pipeline: brief the user, deck-dev implements it, deck-reviewer gates it, findings get fixed, PR merges to dev, board updated."
+---
+
+# Ship an issue
+
+Orchestrate the end-to-end delivery of an issue.
+
+## 0. Brief Before Launching
+Read the issue and verify its claims against the tree. **Spec gate first:** if the issue lacks `Done when` outcomes or scope bounds (what must NOT be added), fix the issue body or ask the user; do not spawn deck-dev against an unbounded spec. Then output a concise 5-point brief (1–2 lines each):
+> **The claim:** What the issue asks for.
+> **What's true now:** Current behavior in the codebase (file:line).
+> **The shape:** Implementation plan in 3–4 concise bullets.
+> **The hard gate:** Invariants that must not break (`tests/golden/`, public API, import law).
+> **Skipped:** What is deliberately out of scope.
+
+## 1. Board Tracking
+Update GitHub Project (`PVT_kwHOBHijkM4BgHFZ`): Set **Status = In progress**, record Start Date, comment with start timestamp.
+
+## 2. Implement
+Spawn `deck-dev` with the issue number and brief. It runs Stage 0 (Understand) then Stage 1
+(Design, posted to the draft PR body), then stops there and reports back rather than continuing
+into Stage 2.
+
+If it stops at its own spec gate despite step 0, the issue needs a human decision: set the board
+back to **Todo**, surface what is missing, stop the pipeline.
+
+**Design gate:** compare the reported design against this step's own brief. A design is never
+blocked for being larger; it is blocked only for a *named* problem: a duplication of something
+already in `scripts/repomap.py`'s output, an abstraction with one caller, a divergence from its
+own declared `## Analog`, configuration for a value that never changes. No such problem: send
+`deck-dev` a message to proceed to Stage 2. A problem found: send it back naming the problem, not
+a target size; `deck-dev` revises Stage 1 and reports again before Stage 2 starts.
+
+Once past the gate, `deck-dev` continues through Implement, Self-review, and Gate, posting task
+progress; poll for stalls.
+
+## 3. Attach PR
+Verify the draft PR targets `dev`, includes `Closes #<n>`, and its body carries the design sections (`## Reuse analysis`, `## Analog`, `## Concept budget`, `## Expected delta`). Missing sections go back to deck-dev before any review is spent. Set **Status = In review** when marked ready.
+
+## 4. Review
+Spawn `deck-reviewer` on the PR. The reviewer must post a COMMENTED GitHub review; a session-only verdict does not count.
+
+## 5. Address Findings
+The review lands on the PR itself (GitHub review + inline comments); read it there. Route by class: **BLOCK** goes to `deck-dev` to fix on the branch. **DISCUSS** is answered in the thread by the author; if the reviewer and author still disagree once answered, escalate to the user rather than letting either side rule. **DEFER** is already a `finding:`-titled issue the reviewer filed and linked; schedule it as its own harness PR, never implemented by the reviewer. **NIT** needs no action unless the author wants it.
+
+## 6. Merge
+Merge when every required check is green **and every review thread is resolved**: `gh pr merge --squash --delete-branch`.
+
+Green checks are not sufficient. One open thread holds the PR at `BLOCKED` with nothing in `gh pr checks` to explain it, and `--admin` cannot force it: `enforce_admins` is on and the ruleset has no bypass actors. Two independent mechanisms enforce it under two different names, and both are live, so read both rather than assuming one mirrors the other:
+
+```bash
+gh api repos/{owner}/{repo}/branches/dev/protection    # required_conversation_resolution
+gh api repos/{owner}/{repo}/rules/branches/dev         # required_review_thread_resolution
+gh api graphql -f query='{repository(owner:"{owner}",name:"{repo}"){pullRequest(number:<n>){reviewThreads(first:20){nodes{id isResolved}}}}}'
+```
+
+Read those payloads whole. Filtering the protection endpoint down to the fields you expected is how this rule got missed in the first place: absence from a `--jq` selection is not absence from the data.
+
+Step 6 detects; it does not resolve. The author resolves each thread, and `ship-pr` carries the mutation. When the orchestrator authored the PR itself, it is the author.
+
+## 7. Complete
+Set **Status = Done**, record Target Date, comment with completion summary and PR link.
+
+## Ground Rules
+- Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.claude/skills/ship-pr/SKILL.md

@@ -95,10 +95,7 @@ including the coverage question. An unanswered question fails the stage.
 - Compact the PR body: it describes the change as it now stands, not the rounds that produced it.
   Delete abandoned design and justifications the code no longer needs.
 - CONSTRAINT: `make check` 100% green before `gh pr ready`. Consequence: `gh pr ready` on a red
-  `make check` fails the Agent review gate and the PR cannot merge.
-- JUDGMENT: if `dev` has advanced past your branch, run `gh pr update-branch --rebase`, not the
-  plain merge default. A merge commit moves the head SHA and invalidates a review's PASS marker
-  for no code reason.
+  `make check` puts a red required check on the PR and it cannot merge.
 - No attribution trailers anywhere.
 
 ## Answering a review

agentdeck_sdk-5.2.0/.codex/agents/deck-dev.toml

@@ -0,0 +1,5 @@
+# Generated by scripts/sync_claude_to_codex.py; do not edit.
+# Claude model "sonnet" omitted; this agent inherits the active Codex model.
+name = "deck-dev"
+description = "Implements a GitHub issue (feature or bug fix) for agentdeck end-to-end in an isolated worktree and opens one PR to dev."
+developer_instructions = "You implement one agentdeck GitHub issue end-to-end in an isolated worktree and open a PR.\n\n**Objective: implement the issue with the smallest coherent change.** Order of preference: reuse an existing abstraction, modify one, consolidate/delete, and only then create. Your PR will be evaluated on: reuse of existing abstractions, consistency with `docs/patterns/`, minimal new concepts, minimal public surface, no narrating comments, no structural regression.\n\n**First action:** read `.claude/skills/ship-pr/SKILL.md` and its `references/`, and follow it. Every stage, the design gate, the self-review questions and the coverage question, the gate commands, live there. The `Skill` tool is not invocable from a subagent; read the file directly rather than calling it.\n\n**Progress:** name each stage (Understand / Design / Implement / Self-review / Gate) as you enter it. A silent multi-stage run reads as a stall.\n\n**Denied tool calls:** a denial is a stop to report, never an obstacle to route around through a different tool or command.\n\n**Subagents:** any agent you spawn passes an explicit `model: \"sonnet\"`. Never omit it, never fable, never opus.\n\n**Output style:** ≤25 words between tool calls; final response ≤100 words unless more detail is required.\n\nReturn: PR URL, one-paragraph summary, `make check` status, and declared-vs-actual concept budget.\n\nCodex compatibility:\n- Preserve worktree isolation: before changing branches or files, create and use a dedicated git worktree outside the primary checkout, and run all task commands there."

agentdeck_sdk-5.2.0/.codex/agents/deck-reviewer.toml

@@ -0,0 +1,5 @@
+# Generated by scripts/sync_claude_to_codex.py; do not edit.
+# Claude model "sonnet" omitted; this agent inherits the active Codex model.
+name = "deck-reviewer"
+description = "Review gate for an agentdeck PR before merge. Verifies correctness, spec compliance, simplicity, conciseness, and test quality against docs/engineering/."
+developer_instructions = "You review one agentdeck PR as the merge gate. REVIEW ONLY on the code: never push a commit anywhere. You DO write review artifacts: the PR review itself, inline comments, and any DEFER, harness-note or Harvest issue.\n\n**First action:** read `.claude/skills/review-pr/SKILL.md` and its `references/`, and follow it. Everything procedural, the phases, the finding classes, the verdict format, the delivery mechanics, lives there. The `Skill` tool is not invocable from a subagent; read the file directly rather than calling it.\n\n**Progress:** say which phase you are entering as you enter it. A silent review reads as a stall.\n\n**Denied tool calls:** a denial is a stop to report, never an obstacle to route around through a different tool or command.\n\n**Subagents:** any agent you spawn passes an explicit `model: \"sonnet\"`. Never omit it, never fable, never opus.\n\n**Output style:** keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.\n\nReturn to the orchestrator: verdict, `make check` result, counts per finding class, links to the posted review and any DEFER issues.\n\nCodex compatibility:\n- Preserve worktree isolation: before changing branches or files, create and use a dedicated git worktree outside the primary checkout, and run all task commands there."

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/PULL_REQUEST_TEMPLATE.md

@@ -29,7 +29,8 @@ new dependencies: 0
 - [ ] New behavior has a test
 - [ ] CHANGELOG entry under **Unreleased** for every user-visible change
 - [ ] User-visible behavior changes update the affected `docs-site/` pages in this PR
-- [ ] Unchanged pages reviewed: <!-- the pages `make check` reports, comma separated; delete the line if none -->
+<!-- If a page above is affected but intentionally left unchanged, name it here (comma separated), the exact form `make check` reports. Delete this checklist line if none. -->
+- [ ] Unchanged pages reviewed:
 - [ ] Implementation diverging from a design doc amends that doc with a dated note in this PR
 - [ ] Goldens (`tests/golden/`, `tests/core/snapshots/`) unchanged  -  or the change is declared and justified here
 - [ ] Deliberate simplifications/shortcuts are marked with a comment naming the ceiling

agentdeck_sdk-5.2.0/.github/dependabot.yml

@@ -0,0 +1,29 @@
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  # Python dependencies, resolved through uv.lock.
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # One PR for the week's minor and patch bumps: they share `uv.lock`, so separate branches
+    # each resolve against the same base and only the first can merge (#499). Majors stay on
+    # their own, because a major is a migration, and a migration inside a batch is one nobody
+    # reviews.
+    groups:
+      python-minor-and-patch:
+        patterns: ["*"]
+        update-types: ["minor", "patch"]
+
+  # The pinned action refs in .github/workflows/.
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Same split, and #477 is why majors are excluded: setup-uv v5 to v7 needed
+    # `activate-environment: true` at the call site, not just a new tag.
+    groups:
+      actions-minor-and-patch:
+        patterns: ["*"]
+        update-types: ["minor", "patch"]

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/ci.yml

@@ -66,7 +66,7 @@ jobs:
       AGENTDECK_TEST_REDIS_URL: redis://127.0.0.1:6379/15
       AGENTDECK_TEST_POSTGRES_DSN: postgresql://postgres:postgres@127.0.0.1:5432/agentdeck_test
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           # The schema's backward-compatibility gate (#47) loads the newest *released*
           # reader out of git (by tag) and measures this tree's events against it. The
@@ -87,9 +87,12 @@ jobs:
             echo "$strays"
             exit 1
           fi
-      - uses: astral-sh/setup-uv@v5
+      - uses: astral-sh/setup-uv@v7
         with:
           python-version: ${{ matrix.python-version }}
+          # v6 made this opt-in; without it `uv pip install` below finds no venv, and the
+          # Makefile's `.venv/bin/*` calls have nothing to run.
+          activate-environment: true
           enable-cache: true
           cache-dependency-glob: "uv.lock"
       # postgres pulls in the psycopg driver the Postgres event log's tests need: omitting an
@@ -154,12 +157,15 @@ jobs:
   # The anti-slop gate for code that never went through a Claude Code hook:
   # outside contributors, and anything written by a process the Edit|Write
   # matcher never saw. Same scripts, PR-base-relative, stdlib only.
+  #
+  # Skipped on a `main`-based PR: that diff is the whole release cycle since main's last
+  # advance, re-flagging lines each contributing PR already passed against `dev` (#536).
   slop:
-    if: github.event_name == 'pull_request'
+    if: github.event_name == 'pull_request' && github.base_ref != 'main'
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
       - name: Comment slop on lines this PR adds

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/docs-check.yml

@@ -28,7 +28,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
@@ -50,7 +50,7 @@ jobs:
 
       - name: Set up Node.js
         if: steps.changed.outputs.run == 'true'
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v7
         with:
           node-version: 22
           cache: npm

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/docs-impact.yml

@@ -14,10 +14,13 @@ permissions:
 jobs:
   check:
     name: Check affected documentation
+    # Skipped on a `main`-based PR: that diff re-accumulates everything merged into `dev`
+    # since main's last advance, each already reviewed against `dev` as its base (#536).
+    if: github.event.pull_request.base.ref != 'main'
     runs-on: ubuntu-latest
     timeout-minutes: 5
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
       # The acknowledgement names its pages, so it survives a push that affects nothing new and

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/docs-pages.yml

@@ -24,12 +24,12 @@ jobs:
 
     steps:
       - name: Checkout released revision
-        uses: actions/checkout@v4
+        uses: actions/checkout@v7
         with:
           ref: ${{ github.event.release.tag_name || github.ref }}
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v7
         with:
           node-version: 22
           cache: npm

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/issue-hygiene.yml

@@ -19,8 +19,13 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 2
     steps:
+      # GitHub creates closing references only for PRs based on the default branch, so this
+      # can never pass on a PR based on anything else (a promotion PR to `main`, a stacked
+      # PR based on a feature branch) (#486).
       - name: Require a labeled closing issue
-        if: github.event.pull_request.user.login != 'dependabot[bot]'
+        if: >-
+          github.event.pull_request.user.login != 'dependabot[bot]' &&
+          github.event.pull_request.base.ref == github.event.repository.default_branch
         env:
           GH_TOKEN: ${{ github.token }}
           PR_NUMBER: ${{ github.event.pull_request.number }}

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.github/workflows/release.yml

@@ -54,10 +54,13 @@ jobs:
       AGENTDECK_TEST_REDIS_URL: redis://127.0.0.1:6379/15
       AGENTDECK_TEST_POSTGRES_DSN: postgresql://postgres:postgres@127.0.0.1:5432/agentdeck_test
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
         with:
           python-version: "3.12"
+          # v6 made this opt-in; without it `uv pip install` below finds no venv, and the
+          # Makefile's `.venv/bin/*` calls have nothing to run.
+          activate-environment: true
           enable-cache: true
           cache-dependency-glob: "uv.lock"
       - name: Verify tag matches pyproject version

{agentdeck_sdk-5.0.3 → agentdeck_sdk-5.2.0}/.gitignore

@@ -23,3 +23,6 @@ docs/brand/*.jpg
 # deepeval writes a cache and a telemetry marker beside the suite
 .deepeval/
 .deepeval-cache.json
+
+# make check's per-target logs (worktree-scoped, see Makefile's LOG)
+.make-*.log

agentdeck_sdk-5.2.0/.import_linter_cache/agentdeck.meta.json

@@ -0,0 +1 @@
+{"agentdeck.adapters.stores.redis": 1787991318.031553, "agentdeck.adapters.executors.openai_agents.runconfig": 1787991318.0304673, "agentdeck.adapters.telemetry": 1787991318.0319402, "agentdeck.core.ports.store": 1787991318.0344682, "agentdeck.adapters.telemetry.langfuse.sink": 1787991318.0322003, "agentdeck.core.ports.executor": 1787991318.0344682, "agentdeck.skills": 1787991318.035757, "agentdeck.authoring.compile": 1787991318.0328615, "agentdeck.surfaces.serve.app": 1787991318.0367963, "agentdeck.adapters.stores": 1787991318.03117, "agentdeck.authoring.native": 1787991318.0328615, "agentdeck.mcp": 1787991318.0347571, "agentdeck.core.status": 1787991318.0344682, "agentdeck.composition": 1787991318.0334094, "agentdeck.adapters.stores.memory.store": 1787991318.03141, "agentdeck.core.ports.lease": 1787991318.0344682, "agentdeck.adapters.control.sqlite": 1787991318.0299516, "agentdeck.core.ports.control": 1787991318.0344682, "agentdeck.adapters.executors.stub.executor": 1787991318.030887, "agentdeck.adapters.tools.mcp.lifecycle": 1787991318.0325863, "agentdeck.errors": 1787991318.0347571, "agentdeck.core.base": 1787991318.0338304, "agentdeck.authoring.injection": 1787991318.0328615, "agentdeck.adapters.executors": 1787991318.0300517, "agentdeck.runtime.discovery": 1787991318.0355892, "agentdeck.adapters.control.memory": 1787991318.0299008, "agentdeck.adapters.stores.memory": 1787991318.0313525, "agentdeck.core.invocable": 1787991318.0338304, "agentdeck.adapters.executors.openai_agents.sessions": 1787991318.0304673, "agentdeck.views": 1787991318.0367963, "agentdeck.serve": 1787991318.035757, "agentdeck": 1787991318.0297182, "agentdeck.adapters.stores.sqlite.store": 1787991318.0319402, "agentdeck.core.events": 1787991318.0338304, "agentdeck.adapters.leases.sqlite.port": 1787991318.03117, "agentdeck.adapters.stores.postgres.store": 1787991318.031553, "agentdeck.authoring.agent": 1787991318.0328615, "agentdeck.adapters.tools.mcp": 1787991318.0325322, "agentdeck.core.ports.tools": 1787991318.0344682, "agentdeck.authoring": 1787991318.0325863, "agentdeck.core.ports": 1787991318.0338304, "agentdeck.adapters.executors.openai_agents.translate": 1787991318.0304673, "agentdeck.authoring.instructions": 1787991318.0328615, "agentdeck.adapters.telemetry.langfuse": 1787991318.0321436, "agentdeck.adapters.leases.sqlite": 1787991318.0310664, "agentdeck.runtime": 1787991318.0347571, "agentdeck.core.ports.sink": 1787991318.0344682, "agentdeck.adapters.executors.native.executor": 1787991318.0302494, "agentdeck.surfaces.cli": 1787991318.0366344, "agentdeck.runtime.capture": 1787991318.0355892, "agentdeck.adapters.stores.sqlite": 1787991318.0317483, "agentdeck.core.errors": 1787991318.0338304, "agentdeck.authoring.runners.agent": 1787991318.0334094, "agentdeck.core.context": 1787991318.0338304, "agentdeck.authoring.hooks": 1787991318.0328615, "agentdeck.adapters.control.sqlite.port": 1787991318.0300517, "agentdeck.core": 1787991318.0334094, "agentdeck.core.content": 1787991318.0338304, "agentdeck.core.reporting": 1787991318.0344682, "agentdeck.adapters.tools": 1787991318.0322003, "agentdeck.runtime.dispatch": 1787991318.0355892, "agentdeck.core.workers": 1787991318.0344682, "agentdeck.observers": 1787991318.0347571, "agentdeck.adapters.stores.redis.store": 1787991318.0317483, "agentdeck.adapters.control": 1787991318.0298378, "agentdeck.testing": 1787991318.0367963, "agentdeck.adapters.executors.stub": 1787991318.0304673, "agentdeck.adapters.executors.openai_agents.executor": 1787991318.0304673, "agentdeck.adapters.executors.openai_agents": 1787991318.0302494, "agentdeck.runtime.service": 1787991318.0355892, "agentdeck.adapters.executors.openai_agents.reconcile": 1787991318.0304673, "agentdeck.adapters.leases.memory": 1787991318.0310168, "agentdeck.surfaces": 1787991318.0365074, "agentdeck.adapters.tools.mcp.source": 1787991318.0325863, "agentdeck.adapters.telemetry.langfuse.trace": 1787991318.0322003, "agentdeck.core.control": 1787991318.0338304, "agentdeck.cli": 1787991318.0334094, "agentdeck.adapters.stores.postgres": 1787991318.03141, "agentdeck.authoring.runners": 1787991318.0328615, "agentdeck.adapters.tools.mcp.transport": 1787991318.0325863, "agentdeck.adapters.leases.memory.port": 1787991318.0310664, "agentdeck.surfaces.serve.compat": 1787991318.0367963, "agentdeck.authoring.tools": 1787991318.0334094, "agentdeck.adapters.leases": 1787991318.030887, "agentdeck.authoring.skills": 1787991318.0334094, "agentdeck.surfaces.cli.chat": 1787991318.0366855, "agentdeck.authoring.web_search": 1787991318.0334094, "agentdeck.runtime.registry": 1787991318.0355892, "agentdeck.adapters.telemetry.langfuse.client": 1787991318.0322003, "agentdeck.adapters.tools.mcp.wiring": 1787991318.0325863, "agentdeck.runtime.settings": 1787991318.0355892, "agentdeck.adapters": 1787991318.0297182, "agentdeck.surfaces.serve": 1787991318.0366855, "agentdeck.authoring.interrupts": 1787991318.0328615, "agentdeck.adapters.executors.native": 1787991318.0301964, "agentdeck.adapters.control.memory.port": 1787991318.0299516, "agentdeck.skills.bundle": 1787991318.0365074, "agentdeck.deck": 1787991318.0347571}