@astrale-os/cli 0.6.0-alpha.0 → 0.6.2-alpha.0

package/dist/astrale.js

@@ -2576,7 +2576,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@astrale-os/cli",
-    version: "0.6.0-alpha.0",
+    version: "0.6.2-alpha.0",
     description: "Astrale CLI — connect to existing Astrale kernels",
     keywords: [
       "astrale",
@@ -73387,9 +73387,9 @@ function buildPrompt(opts) {
 `);
   const filing = opts.file ? `
 FILE the issues that clear the quality bar (after writing report.md). Use the normal door, one call per issue:
-  astrale call /:admin.astrale.ai:class.Issue:report -i admin --ci kind=<bug|friction|feature> title="<one line>" body="<evidence: exact command, exact error, expected vs actual, session ${id}>"
+  astrale call /:issues.astrale.ai:class.Issue:create -i admin --ci parent=/issues status=open title="<one line>" body="<evidence: exact command, exact error, expected vs actual, session ${id}>" initialTags='["<bug|friction|feature>","<area>"]'
 Always pass --ci and keep title/body plain ASCII (no smart quotes/arrows) — long special-character bodies can hang the call.
-Duplicates of existing issues are acceptable — recurrence is signal, triage groups them later. Do NOT dedup-check first. Record each returned issue id in report.md under "## Filed". If filing fails (auth/offline), record the failure in report.md — do not retry more than once.` : `
+Duplicates of existing issues are acceptable — recurrence is signal, triage groups them later. Do NOT dedup-check first. Record each returned issue path in report.md under "## Filed". If filing fails (auth/offline), record the failure in report.md — do not retry more than once.` : `
 Do NOT file any issues in this run (dry-run). report.md is the only output.`;
   return `You are the DX analyst for Astrale (a graph OS; developers build "domains" against its CLI/SDK). Below is the complete evidence of ONE local work session. Your job: find the real frictions the developer or their coding agent hit with ASTRALE tooling — CLI, SDK, docs, skills — and write \`report.md\` in the current directory.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrale-os/cli",
-  "version": "0.6.0-alpha.0",
+  "version": "0.6.2-alpha.0",
   "description": "Astrale CLI — connect to existing Astrale kernels",
   "keywords": [
     "astrale",

package/src/telemetry/analyze.ts

@@ -1,8 +1,8 @@
 /**
  * Session analyzer: free gate first, then ONE headless `claude -p` pass over
  * the session's evidence (event digest, harness transcripts, live workspace).
- * Dry-run by default — the agent writes report.md; --file also files issues
- * through the normal `astrale call … Issue:report` door.
+ * Dry-run by default — the agent writes report.md; --file also creates issues
+ * through the native `issues.astrale.ai` domain.
  */
 import { spawn } from 'node:child_process'
 import { appendFileSync, writeFileSync } from 'node:fs'
@@ -75,9 +75,9 @@ function buildPrompt(opts: {
   const filing = opts.file
     ? `
 FILE the issues that clear the quality bar (after writing report.md). Use the normal door, one call per issue:
-  astrale call /:admin.astrale.ai:class.Issue:report -i admin --ci kind=<bug|friction|feature> title="<one line>" body="<evidence: exact command, exact error, expected vs actual, session ${id}>"
+  astrale call /:issues.astrale.ai:class.Issue:create -i admin --ci parent=/issues status=open title="<one line>" body="<evidence: exact command, exact error, expected vs actual, session ${id}>" initialTags='["<bug|friction|feature>","<area>"]'
 Always pass --ci and keep title/body plain ASCII (no smart quotes/arrows) — long special-character bodies can hang the call.
-Duplicates of existing issues are acceptable — recurrence is signal, triage groups them later. Do NOT dedup-check first. Record each returned issue id in report.md under "## Filed". If filing fails (auth/offline), record the failure in report.md — do not retry more than once.`
+Duplicates of existing issues are acceptable — recurrence is signal, triage groups them later. Do NOT dedup-check first. Record each returned issue path in report.md under "## Filed". If filing fails (auth/offline), record the failure in report.md — do not retry more than once.`
     : `
 Do NOT file any issues in this run (dry-run). report.md is the only output.`
 

package/studio/server/agent/prompt.ts

@@ -66,9 +66,9 @@ export function buildSystemPrompt(opts: { bridge: boolean }): string {
     'working in this domain costs YOU friction — a confusing or missing Astrale API/error, stale',
     'docs or skills, or a bug that forced a workaround — FILE a DX issue as part of the task, per',
     'the **astrale-cli** skill’s “Reporting DX Issues” section: dedup against open issues first, then',
-    '`astrale call /:admin.astrale.ai:class.Issue:report kind=<bug|friction|feature> title=… body=…`.',
+    '`astrale call /:issues.astrale.ai:class.Issue:create -i admin parent=/issues status=open title=… body=… initialTags=\'["<bug|friction|feature>","<area>"]\'`.',
     'It is best-effort and non-blocking — never let filing one derail the user’s task — and mention',
-    'the returned id in your reply when you file one.',
+    'the returned issue path in your reply when you file one.',
     '',
     'REPLY PROTOCOL — this is how the user sees your answers (they are NOT watching your terminal):',
     '- For EVERY open thread, append exactly one concise {role:"author"} reply: what you changed,',