@arjunkhera/atlas 0.3.32 → 0.3.34

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "atlas",
-  "version": "0.3.32",
+  "version": "0.3.34",
   "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, for any repository.",
   "author": {
     "name": "Arjun Khera"

package/door/kit-releases.json

@@ -28,6 +28,10 @@
     {
       "kit_sha256": "08c868aa39e6c9f471da2571e9a1d5939932a59856cea9c4176e3173f93454db",
       "first_package": "0.3.30"
+    },
+    {
+      "kit_sha256": "c4a506ec261d2d2fd7884943c9d317fb7b522704f4f63669b5bd37d32326bde5",
+      "first_package": "0.3.32"
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arjunkhera/atlas",
-  "version": "0.3.32",
+  "version": "0.3.34",
   "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, as a Claude Code plugin for any repository.",
   "type": "module",
   "license": "UNLICENSED",

package/skills/feedback/SKILL.md

@@ -3,7 +3,7 @@ name: feedback
 description: >
   File a report about Atlas, or about a product, as an issue in the right public repo.
   Trigger when someone says "Atlas should …", "report this", "file an issue", or asks for a
-  feature or a fix that is not a correction of the work in this session. It searches open
+  feature or a fix that is not a correction of the work in this session. It searches the
   issues first and files nothing until the person says "file it".
 ---
 
@@ -18,10 +18,14 @@ goes to the `atlas:learnings` skill instead.
 1. **Find the issue repo.** Read it from the product record: the Atlas
    tools return it with the product. For a report about Atlas itself, the
    issue repo is the Atlas repo. If no issue repo is known, ask for it.
-2. **Search open issues first.** Use `gh issue list --repo <repo>
-   --state open --search "<key words>"`. Try two or three short searches.
-3. **Show what you found.** If an open issue matches, show its title and
-   link. Offer to add the new detail to it as a comment.
+2. **Search the issues first.** Use `gh issue list --repo <repo>
+   --state all --search "<key words>"`. Try two or three short searches.
+   Search closed issues too: an issue closes when its tracker item
+   exists, and its closing note names the item.
+3. **Show what you found.** If an issue matches, show its title and
+   link. A closing note can name an item. Then the work lives in that
+   item, so offer to add the new detail with `item_comment`. Otherwise
+   offer to add it to the issue as a comment.
 4. **Draft the issue.** Write a title and a short body: what happens, what
    should happen, and the steps to see it. Write in plain words.
 5. **Run the privacy filter.** Write the draft to a scratch file, and run
@@ -30,24 +34,28 @@ goes to the `atlas:learnings` skill instead.
    "file it", or the same in their own words.
 7. **File it once.** Use `gh issue create --repo <repo> --title <title>
    --body-file <file>`.
-8. **Put the issue in the tracker.** Every open issue has a tracker item.
+8. **Move the issue into the tracker.** The tracker item is the one home
+   for the work. The issue stays as the record of the report, closed.
    The lead does this step, because only the lead writes to the tracker.
    1. Call `item_propose` with the product and the repo of the issue.
       Use the issue title as the title. Use the person's own words as
       the origin, with the issue link as its source.
    2. Call `item_link` on the new item with kind `issue`, the issue URL
       and role `report`.
-   3. Add a comment on the issue that names the item id.
+   3. Close the issue with a comment that names the item id. Say that
+      the item now holds the work. Use `gh issue close <number> --repo
+      <repo> --comment "<note>"`.
    4. Give the person the issue link and the item id.
 
-   If the issue adds to an open issue that has an item, link it to that
-   item instead, and make no new item. If `item_propose` refuses because
-   the owner is not present, give the person the issue link and say that
-   the owner must add the item.
+   The issue can add to an issue that has an item. Then link it to that
+   item, make no new item, and close it the same way. `item_propose` can
+   refuse because the owner is not present. Then keep the issue open,
+   give the person the issue link, and say that the owner must add it.
 
 Example: the person says "Atlas should show which copy runs", then
 "file it". The lead files issue #150, proposes the item "Show which copy
-of Atlas runs", links #150 to it, and comments the item id on #150.
+of Atlas runs", and links #150 to it. Then the lead closes #150 with the
+note "Tracked as item 1a2b3c4d. The item holds the work now."
 
 When `gh` fails or is not there, use the session's GitHub tools for the
 same search and the same issue.
@@ -60,3 +68,5 @@ same search and the same issue.
 3. One report is one issue. Split a report that holds two asks.
 4. Never leave a filed issue with no tracker item, except when the owner
    is not present. Then say so.
+5. Never keep an issue open after its item exists. The owner's rule of
+   21 October 2026: the work moves to the item.

package/tests/model.mjs

@@ -291,6 +291,9 @@ export async function runClaude({ prompt, args = [], key, cwd, meter, what, reda
     meter.add(Number.isFinite(cost) ? cost : left, what, id);
     if (!envelope) throw new Error(`${what}: the model command gave no answer (exit ${out.exit}): ${(redactor ? redactor.text(out.stderr || out.stdout) : out.stderr || out.stdout).slice(0, 400)}`);
     const clean = (t) => (redactor ? redactor.text(t) : t);
+    // An error answer with no cost never reached the model: a refused sign-in, no credit, a bad model
+    // name. The scenario cannot pass or fail on it, so it reads blocked, with the reason.
+    if (envelope.is_error && !Number.isFinite(cost)) throw new Blocked(`${what}: the model call failed before the model answered: ${clean(String(envelope.result ?? envelope.error ?? (out.stderr || out.stdout))).slice(0, 400)}`);
     if (out.signal === 'SIGKILL') throw new Error(`${what}: the model call ran past ${Math.round(timeoutMs / 1000)} seconds and was stopped`);
     return { exit: out.exit, stdout: clean(out.stdout), stderr: clean(out.stderr), envelope, events, cost: Number.isFinite(cost) ? cost : null };
   } finally {