@autohq/cli 0.1.408 → 0.1.409

package/dist/agent-bridge.js

@@ -30819,7 +30819,7 @@ Object.assign(lookup, {
 // package.json
 var package_default = {
   name: "@autohq/cli",
-  version: "0.1.408",
+  version: "0.1.409",
   license: "SEE LICENSE IN README.md",
   publishConfig: {
     access: "public"
@@ -33491,6 +33491,18 @@ var ConnectionRemoveResponseSchema = external_exports.object({
   message: external_exports.string().trim().min(1)
 });
 
+// ../../packages/schemas/src/dormant-capabilities.ts
+var DormantCapabilityConnectionSchema = external_exports.object({
+  provider: external_exports.string().trim().min(1),
+  connection: external_exports.string().trim().min(1)
+});
+var DormantCapabilitySchema = external_exports.object({
+  kind: external_exports.enum(["tool", "trigger"]),
+  name: external_exports.string().trim().min(1),
+  connections: external_exports.array(DormantCapabilityConnectionSchema).min(1)
+});
+var DormantCapabilitiesSchema = external_exports.array(DormantCapabilitySchema);
+
 // ../../packages/schemas/src/github-sync.ts
 var GITHUB_SYNC_AUTO_PATH = ".auto";
 var GITHUB_SYNC_CI_WATCHDOG_DEFAULT_DELAY_MS = 15e3;
@@ -41851,6 +41863,47 @@ triggers:
           content: "harness: claude-code\nenvironment:\n  name: agent-runtime\n  image:\n    kind: preset\n    name: node24\n  resources:\n    memoryMB: 8192\n"
         }
       ]
+    },
+    {
+      version: "1.4.0",
+      files: [
+        {
+          path: "agents/issue-coder-linear-slack.yaml",
+          content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-coder-linear.yaml, whose Slack mention entrypoint uses the\n# standard `slack` connection. This subpath preserves the parameterized,\n# Slack-required behavior of earlier `-linear-slack` versions for existing\n# @latest facades through at least the next minor version.\nimports:\n  - ./issue-coder-linear.yaml\nremove:\n  tools:\n    - slack\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged Linear issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-coder-linear.yaml",
+          content: 'name: issue-coder\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Coder\n  username: issue-coder\n  avatar:\n    asset: .auto/assets/patch.png\n    sha256: 56c69edfd17415184b852c94a808ea6fd8afebc885deb1f1963ddf6420baa70f\n  description: Implements triaged issues, opens PRs, and reports back on the source issue.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the implementation agent for {{ $repoFullName }}.\n\n  Treat each run as fresh, scoped implementation work. Read the repo\'s\n  contribution docs before editing. Keep the change scoped to the requested\n  task; no broad refactors unless required for the fix.\n\n  Work from the mounted checkout on main. Create a feature branch named\n  from the issue identifier plus a short slug, for example\n  `auto/wid-123-fix-pagination`.\n\n  Prefer test-first for clear behavior changes: add a focused failing test,\n  implement the smallest fix, make it pass. Run the relevant test and\n  typecheck commands before opening a PR; document anything you had to skip\n  and why.\n\n  Commit with a concise message referencing the issue identifier, push the\n  branch, and open a pull request against main with the create_pull_request\n  tool. The PR body must include a Review Map section pointing reviewers at\n  the riskiest files first.\n\n  When posting GitHub comments or PRs, append this hidden attribution\n  marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\n\n  Comment back on the Linear issue (chat.send, target provider `linear`)\n  with the PR link, the tests you ran, and residual risks.\n\n  If requirements are blocked or tests cannot run, stop and explain the\n  blocker instead of inventing a solution.\ninitialPrompt: |\n  Implement the issue described in the spawn message. Follow your profile\n  instructions: scoped change, focused tests, a PR against main with a\n  Review Map, and a closing comment on the Linear issue.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: write\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n  slack:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - create_pull_request\n      - add_issue_comment\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged Linear issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-coder-slack.yaml",
+          content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-coder.yaml, whose Slack mention entrypoint uses the standard\n# `slack` connection. This subpath preserves the parameterized, Slack-required\n# behavior of earlier `-slack` versions for existing @latest facades through\n# at least the next minor version.\nimports:\n  - ./issue-coder.yaml\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: false\n      connections:\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged GitHub issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-coder.yaml",
+          content: 'name: issue-coder\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Coder\n  username: issue-coder\n  avatar:\n    asset: .auto/assets/patch.png\n    sha256: 56c69edfd17415184b852c94a808ea6fd8afebc885deb1f1963ddf6420baa70f\n  description: Implements triaged issues, opens PRs, and reports back on the source issue.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the implementation agent for {{ $repoFullName }}.\n\n  Treat each run as fresh, scoped implementation work. Read the repo\'s\n  contribution docs before editing. Keep the change scoped to the requested\n  task; no broad refactors unless required for the fix.\n\n  Work from the mounted checkout on main. Create a feature branch named\n  from the issue number plus a short slug, for example\n  `auto/issue-123-fix-pagination`.\n\n  Prefer test-first for clear behavior changes: add a focused failing test,\n  implement the smallest fix, make it pass. Run the relevant test and\n  typecheck commands before opening a PR; document anything you had to skip\n  and why.\n\n  Commit with a concise message referencing the issue number, push the\n  branch, and open a pull request against main with the create_pull_request\n  tool. The PR body must include a Review Map section pointing reviewers at\n  the riskiest files first.\n\n  When posting GitHub comments or PRs, append this hidden attribution\n  marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\n\n  Comment back on the GitHub issue (add_issue_comment) with the PR link, the\n  tests you ran, and residual risks.\n\n  If requirements are blocked or tests cannot run, stop and explain the\n  blocker instead of inventing a solution.\ninitialPrompt: |\n  Implement the issue described in the spawn message. Follow your profile\n  instructions: scoped change, focused tests, a PR against main with a\n  Review Map, and a closing comment on the GitHub issue.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: write\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - create_pull_request\n      - issue_read\n      - add_issue_comment\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged GitHub issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-triage-linear-slack.yaml",
+          content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-triage-linear.yaml, whose Slack reporting uses the standard\n# `slack` connection and `#dev` channel. This subpath preserves the\n# parameterized, Slack-required behavior of earlier `-linear-slack` versions\n# for existing @latest facades through at least the next minor version.\nimports:\n  - ./issue-triage-linear.yaml\nremove:\n  tools:\n    - slack\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from Linear as the\n  source of truth, using chat.issue.get, chat.issue.update, chat.history,\n  and chat.send with target provider `linear`.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a Linear comment.\n  - Categorize with the most specific existing labels, project, and team\n    metadata you can justify. Never create Linear labels, statuses,\n    projects, teams, or users \u2014 if the expected metadata does not exist,\n    note that in a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a Linear comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Update the issue state to an existing in-progress state if one fits.\n  - Remove the `auto-triage` label.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue identifier, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the Linear issue with the PR link,\n    tests run, and residual risks.\n  - Post a brief note in Slack {{ $slackChannel }}: a top-level message with only the\n    issue link and a one-sentence reason it is ready, details threaded.\n    Slack renders mrkdwn links: <https://url|text>.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn.\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a Linear issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage Linear issues\n      labeled `auto-triage`, prepare implementation handoffs, and post\n      ready-work notes to {{ $slackChannel }}.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-triage-linear.yaml",
+          content: 'name: issue-triage\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Triage\n  username: issue-triage\n  avatar:\n    asset: .auto/assets/triage.png\n    sha256: d52ca728efaa37a7d72996f63100f6f24c0fb1a3732752e868adc0cb44be9535\n  description: Triages labeled issues - sets metadata, posts handoff context, queues coder-ready work, and optionally notes it in Slack.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from Linear as the\n  source of truth, using chat.issue.get, chat.issue.update, chat.history,\n  and chat.send with target provider `linear`.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a Linear comment.\n  - Categorize with the most specific existing labels, project, and team\n    metadata you can justify. Never create Linear labels, statuses,\n    projects, teams, or users \u2014 if the expected metadata does not exist,\n    note that in a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a Linear comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Update the issue state to an existing in-progress state if one fits.\n  - Remove the `auto-triage` label.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue identifier, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the Linear issue with the PR link,\n    tests run, and residual risks.\n  - When Slack is available as a chat.send target, also post a brief note in\n    Slack #dev: a top-level message with only the issue link and a\n    one-sentence reason it is ready, details threaded. Slack renders mrkdwn\n    links: <https://url|text>.\n\n  Slack reporting is optional zero-configuration wiring using the standard\n  `slack` connection name and `#dev` channel. When Slack is not an available\n  chat.send target, skip the Slack steps and do not treat that as a failure \u2014\n  Linear comments remain the complete triage record. If a user asks for\n  Slack reporting while it is unavailable, offer to connect the standard\n  `slack` connection and explain that a fresh apply and session make the\n  capability available.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn.\ninitialPrompt: |\n  Triage Linear issue {{linear.issue.identifier}}: {{linear.issue.title}}\n\n  Trigger event: {{type}}\n  Issue URL: {{linear.issue.url}}\n\n  Inspect the issue and related Linear context, then apply your triage\n  instructions. Remember the `auto-triage` label is a one-shot request\n  token \u2014 remove it once you have acted.\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n  slack:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: issue-created\n    event: linear.issue.created\n    connection: "{{ $linearConnection }}"\n    where:\n      $.linear.issue.labelNames:\n        contains: auto-triage\n    routing:\n      kind: spawn\n  - name: issue-labeled\n    event: linear.issue.updated\n    connection: "{{ $linearConnection }}"\n    where:\n      $.linear.updatedFrom.labelNames.added:\n        contains: auto-triage\n    routing:\n      kind: spawn\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a Linear issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage Linear issues\n      labeled `auto-triage`, prepare implementation handoffs, and post\n      ready-work notes to #dev.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-triage-slack.yaml",
+          content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-triage.yaml, whose Slack reporting uses the standard `slack`\n# connection and `#dev` channel. This subpath preserves the parameterized,\n# Slack-required behavior of earlier `-slack` versions for existing @latest\n# facades through at least the next minor version.\nimports:\n  - ./issue-triage.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from GitHub Issues\n  as the source of truth, using issue_read, issue_write, and add_issue_comment\n  through the github tool to inspect, update, and comment on issues.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it with issue_write once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a GitHub issue comment.\n  - Categorize with the most specific existing labels you can justify. Never\n    create GitHub labels \u2014 if the expected label does not exist, note that in\n    a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a GitHub issue comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Remove the `auto-triage` label with issue_write.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue number, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the GitHub issue with the PR link,\n    tests run, and residual risks.\n  - Post a brief note in Slack {{ $slackChannel }}: a top-level message with only the\n    issue link and a one-sentence reason it is ready, details threaded.\n    Slack renders mrkdwn links: <https://url|text>.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn. When posting GitHub comments, append this\n  hidden attribution marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: false\n      connections:\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a GitHub issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage newly opened\n      GitHub issues and `auto-triage`-labeled re-triage requests, prepare\n      implementation handoffs, and post ready-work notes to {{ $slackChannel }}.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "agents/issue-triage.yaml",
+          content: 'name: issue-triage\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Triage\n  username: issue-triage\n  avatar:\n    asset: .auto/assets/triage.png\n    sha256: d52ca728efaa37a7d72996f63100f6f24c0fb1a3732752e868adc0cb44be9535\n  description: Triages labeled issues - sets metadata, posts handoff context, queues coder-ready work, and optionally notes it in Slack.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from GitHub Issues\n  as the source of truth, using issue_read, issue_write, and add_issue_comment\n  through the github tool to inspect, update, and comment on issues.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it with issue_write once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a GitHub issue comment.\n  - Categorize with the most specific existing labels you can justify. Never\n    create GitHub labels \u2014 if the expected label does not exist, note that in\n    a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a GitHub issue comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Remove the `auto-triage` label with issue_write.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue number, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the GitHub issue with the PR link,\n    tests run, and residual risks.\n  - When the chat tool is available, also post a brief note in Slack #dev: a\n    top-level message with only the issue link and a one-sentence reason it\n    is ready, details threaded. Slack renders mrkdwn links:\n    <https://url|text>.\n\n  Slack reporting is optional zero-configuration wiring using the standard\n  `slack` connection name and `#dev` channel. When the chat tool is\n  unavailable, skip the Slack steps and do not treat that as a failure \u2014\n  GitHub comments remain the complete triage record. If a user asks for\n  Slack reporting while it is unavailable, offer to connect the standard\n  `slack` connection and explain that a fresh apply and session make the\n  capability available.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn. When posting GitHub comments, append this\n  hidden attribution marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\ninitialPrompt: |\n  Triage GitHub issue #{{github.issue.number}}: {{github.issue.title}}\n\n  Trigger event: {{type}}\n  Issue URL: {{github.issue.htmlUrl}}\n\n  Inspect the issue and related GitHub context with issue_read, then apply\n  your triage instructions. Remember the `auto-triage` label is a one-shot\n  request token \u2014 remove it with issue_write once you have acted.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: none\n        issues: write\n        checks: none\n        actions: none\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - issue_read\n      - issue_write\n      - add_issue_comment\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: issue-opened\n    event: github.issue.opened\n    connection: "{{ $githubConnection }}"\n    where:\n      $.github.repository.fullName: "{{ $repoFullName }}"\n      $.github.auto.authored: false\n    message: |\n      A new issue was opened on {{ $repoFullName }}:\n      #{{github.issue.number}} \u2014 {{github.issue.title}}.\n\n      Issue URL: {{github.issue.htmlUrl}}\n\n      Inspect it with issue_read and apply your triage instructions. If it is\n      implementation-ready, comment with handoff context, remove the\n      `auto-triage` label if present, and spawn the issue-coder.\n    routing:\n      kind: bind\n      target: github.issue\n      onUnmatched: spawn\n  - name: issue-labeled\n    event: github.issue.labeled\n    connection: "{{ $githubConnection }}"\n    where:\n      $.github.repository.fullName: "{{ $repoFullName }}"\n      $.github.auto.authored: false\n      $.github.label.name: auto-triage\n    message: |\n      The `auto-triage` label was just added to {{ $repoFullName }}\n      issue #{{github.issue.number}} \u2014 {{github.issue.title}}.\n\n      Issue URL: {{github.issue.htmlUrl}}\n\n      The label is a one-shot re-triage request. Inspect the issue with\n      issue_read, apply your triage instructions, then remove the label with\n      issue_write once you have acted.\n    routing:\n      kind: bind\n      target: github.issue\n      onUnmatched: spawn\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a GitHub issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage newly opened\n      GitHub issues and `auto-triage`-labeled re-triage requests, prepare\n      implementation handoffs, and post ready-work notes to #dev.\n    routing:\n      kind: spawn\n'
+        },
+        {
+          path: "fragments/environments/agent-runtime.yaml",
+          content: "harness: claude-code\nenvironment:\n  name: agent-runtime\n  image:\n    kind: preset\n    name: node24\n  resources:\n    memoryMB: 8192\n"
+        }
+      ]
     }
   ],
   "@auto/lead-engine": [
@@ -49507,7 +49560,7 @@ var TEMPLATE_DESCRIPTIONS = {
   "@auto/engineering-tier": "An engineering-tier fleet: senior and junior engineers with PR ownership, a live-iteration designer, and a session introspector.",
   "@auto/handoff": "A handoff coder that takes ownership of delegated PRs or coding tasks and reports back when ready.",
   "@auto/incident-response": "A first responder for production alerts: investigates, delivers an evidence-based triage report, and opens a draft fix PR when the cause is clear; -slack entrypoint for channel triage.",
-  "@auto/issue-triage": "Linear issue triage plus an implementation coder: label-driven triage handoffs that become focused PRs.",
+  "@auto/issue-triage": "Issue triage plus an implementation coder on a GitHub Issues or Linear substrate, with optional Slack reporting; deprecated -slack entrypoints keep the required-Slack behavior.",
   "@auto/lead-engine": "A sourced lead researcher for webhook payloads, direct-session criteria, public web signals, and authorized provider-backed sources; -slack entrypoint for a sales-channel flow.",
   "@auto/onboarding": "Auto's house onboarding guidance, importable as a managed template.",
   "@auto/onboarding-quickstart": "The quickstart template repo's onboarding overlay: composes onto @auto/onboarding with the fork-flow walkthrough beats (site request bar, handoff loop, self-improvement demo).",

package/dist/index.js

@@ -17432,6 +17432,25 @@ var init_connections = __esm({
   }
 });
 
+// ../../packages/schemas/src/dormant-capabilities.ts
+var DormantCapabilityConnectionSchema, DormantCapabilitySchema, DormantCapabilitiesSchema;
+var init_dormant_capabilities = __esm({
+  "../../packages/schemas/src/dormant-capabilities.ts"() {
+    "use strict";
+    init_zod();
+    DormantCapabilityConnectionSchema = external_exports.object({
+      provider: external_exports.string().trim().min(1),
+      connection: external_exports.string().trim().min(1)
+    });
+    DormantCapabilitySchema = external_exports.object({
+      kind: external_exports.enum(["tool", "trigger"]),
+      name: external_exports.string().trim().min(1),
+      connections: external_exports.array(DormantCapabilityConnectionSchema).min(1)
+    });
+    DormantCapabilitiesSchema = external_exports.array(DormantCapabilitySchema);
+  }
+});
+
 // ../../packages/schemas/src/github-sync.ts
 var GITHUB_SYNC_AUTO_PATH, GITHUB_SYNC_CI_WATCHDOG_DEFAULT_DELAY_MS, GithubSyncRepositoryFullNameSchema, GithubSyncProductionBranchSchema, GithubSyncCiWatchdogWorkflowSchema, GithubSyncCiWatchdogSchema, GithubSyncBindingSchema, GithubSyncBindingCreateRequestSchema, GithubSyncInitialSyncSchema, GithubSyncBindingCreateResponseSchema, GithubSyncBindingListResponseSchema, GithubSyncTriggerArtifactSchema, GithubSyncWorkflowInputSchema, GithubSyncWorkflowResultSchema;
 var init_github_sync = __esm({
@@ -26234,6 +26253,47 @@ triggers:
               content: "harness: claude-code\nenvironment:\n  name: agent-runtime\n  image:\n    kind: preset\n    name: node24\n  resources:\n    memoryMB: 8192\n"
             }
           ]
+        },
+        {
+          version: "1.4.0",
+          files: [
+            {
+              path: "agents/issue-coder-linear-slack.yaml",
+              content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-coder-linear.yaml, whose Slack mention entrypoint uses the\n# standard `slack` connection. This subpath preserves the parameterized,\n# Slack-required behavior of earlier `-linear-slack` versions for existing\n# @latest facades through at least the next minor version.\nimports:\n  - ./issue-coder-linear.yaml\nremove:\n  tools:\n    - slack\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged Linear issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-coder-linear.yaml",
+              content: 'name: issue-coder\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Coder\n  username: issue-coder\n  avatar:\n    asset: .auto/assets/patch.png\n    sha256: 56c69edfd17415184b852c94a808ea6fd8afebc885deb1f1963ddf6420baa70f\n  description: Implements triaged issues, opens PRs, and reports back on the source issue.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the implementation agent for {{ $repoFullName }}.\n\n  Treat each run as fresh, scoped implementation work. Read the repo\'s\n  contribution docs before editing. Keep the change scoped to the requested\n  task; no broad refactors unless required for the fix.\n\n  Work from the mounted checkout on main. Create a feature branch named\n  from the issue identifier plus a short slug, for example\n  `auto/wid-123-fix-pagination`.\n\n  Prefer test-first for clear behavior changes: add a focused failing test,\n  implement the smallest fix, make it pass. Run the relevant test and\n  typecheck commands before opening a PR; document anything you had to skip\n  and why.\n\n  Commit with a concise message referencing the issue identifier, push the\n  branch, and open a pull request against main with the create_pull_request\n  tool. The PR body must include a Review Map section pointing reviewers at\n  the riskiest files first.\n\n  When posting GitHub comments or PRs, append this hidden attribution\n  marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\n\n  Comment back on the Linear issue (chat.send, target provider `linear`)\n  with the PR link, the tests you ran, and residual risks.\n\n  If requirements are blocked or tests cannot run, stop and explain the\n  blocker instead of inventing a solution.\ninitialPrompt: |\n  Implement the issue described in the spawn message. Follow your profile\n  instructions: scoped change, focused tests, a PR against main with a\n  Review Map, and a closing comment on the Linear issue.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: write\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n  slack:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - create_pull_request\n      - add_issue_comment\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged Linear issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-coder-slack.yaml",
+              content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-coder.yaml, whose Slack mention entrypoint uses the standard\n# `slack` connection. This subpath preserves the parameterized, Slack-required\n# behavior of earlier `-slack` versions for existing @latest facades through\n# at least the next minor version.\nimports:\n  - ./issue-coder.yaml\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: false\n      connections:\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged GitHub issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-coder.yaml",
+              content: 'name: issue-coder\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Coder\n  username: issue-coder\n  avatar:\n    asset: .auto/assets/patch.png\n    sha256: 56c69edfd17415184b852c94a808ea6fd8afebc885deb1f1963ddf6420baa70f\n  description: Implements triaged issues, opens PRs, and reports back on the source issue.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the implementation agent for {{ $repoFullName }}.\n\n  Treat each run as fresh, scoped implementation work. Read the repo\'s\n  contribution docs before editing. Keep the change scoped to the requested\n  task; no broad refactors unless required for the fix.\n\n  Work from the mounted checkout on main. Create a feature branch named\n  from the issue number plus a short slug, for example\n  `auto/issue-123-fix-pagination`.\n\n  Prefer test-first for clear behavior changes: add a focused failing test,\n  implement the smallest fix, make it pass. Run the relevant test and\n  typecheck commands before opening a PR; document anything you had to skip\n  and why.\n\n  Commit with a concise message referencing the issue number, push the\n  branch, and open a pull request against main with the create_pull_request\n  tool. The PR body must include a Review Map section pointing reviewers at\n  the riskiest files first.\n\n  When posting GitHub comments or PRs, append this hidden attribution\n  marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\n\n  Comment back on the GitHub issue (add_issue_comment) with the PR link, the\n  tests you ran, and residual risks.\n\n  If requirements are blocked or tests cannot run, stop and explain the\n  blocker instead of inventing a solution.\ninitialPrompt: |\n  Implement the issue described in the spawn message. Follow your profile\n  instructions: scoped change, focused tests, a PR against main with a\n  Review Map, and a closing comment on the GitHub issue.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: write\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - create_pull_request\n      - issue_read\n      - add_issue_comment\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If this is a clear triage handoff,\n      handle it. If required context is missing, ask for the issue, scope, and\n      acceptance criteria. Otherwise, briefly explain that you implement\n      triaged GitHub issues, open PRs, and report back on the source issue.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-triage-linear-slack.yaml",
+              content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-triage-linear.yaml, whose Slack reporting uses the standard\n# `slack` connection and `#dev` channel. This subpath preserves the\n# parameterized, Slack-required behavior of earlier `-linear-slack` versions\n# for existing @latest facades through at least the next minor version.\nimports:\n  - ./issue-triage-linear.yaml\nremove:\n  tools:\n    - slack\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from Linear as the\n  source of truth, using chat.issue.get, chat.issue.update, chat.history,\n  and chat.send with target provider `linear`.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a Linear comment.\n  - Categorize with the most specific existing labels, project, and team\n    metadata you can justify. Never create Linear labels, statuses,\n    projects, teams, or users \u2014 if the expected metadata does not exist,\n    note that in a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a Linear comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Update the issue state to an existing in-progress state if one fits.\n  - Remove the `auto-triage` label.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue identifier, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the Linear issue with the PR link,\n    tests run, and residual risks.\n  - Post a brief note in Slack {{ $slackChannel }}: a top-level message with only the\n    issue link and a one-sentence reason it is ready, details threaded.\n    Slack renders mrkdwn links: <https://url|text>.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn.\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a Linear issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage Linear issues\n      labeled `auto-triage`, prepare implementation handoffs, and post\n      ready-work notes to {{ $slackChannel }}.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-triage-linear.yaml",
+              content: 'name: issue-triage\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Triage\n  username: issue-triage\n  avatar:\n    asset: .auto/assets/triage.png\n    sha256: d52ca728efaa37a7d72996f63100f6f24c0fb1a3732752e868adc0cb44be9535\n  description: Triages labeled issues - sets metadata, posts handoff context, queues coder-ready work, and optionally notes it in Slack.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from Linear as the\n  source of truth, using chat.issue.get, chat.issue.update, chat.history,\n  and chat.send with target provider `linear`.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a Linear comment.\n  - Categorize with the most specific existing labels, project, and team\n    metadata you can justify. Never create Linear labels, statuses,\n    projects, teams, or users \u2014 if the expected metadata does not exist,\n    note that in a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a Linear comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Update the issue state to an existing in-progress state if one fits.\n  - Remove the `auto-triage` label.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue identifier, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the Linear issue with the PR link,\n    tests run, and residual risks.\n  - When Slack is available as a chat.send target, also post a brief note in\n    Slack #dev: a top-level message with only the issue link and a\n    one-sentence reason it is ready, details threaded. Slack renders mrkdwn\n    links: <https://url|text>.\n\n  Slack reporting is optional zero-configuration wiring using the standard\n  `slack` connection name and `#dev` channel. When Slack is not an available\n  chat.send target, skip the Slack steps and do not treat that as a failure \u2014\n  Linear comments remain the complete triage record. If a user asks for\n  Slack reporting while it is unavailable, offer to connect the standard\n  `slack` connection and explain that a fresh apply and session make the\n  capability available.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn.\ninitialPrompt: |\n  Triage Linear issue {{linear.issue.identifier}}: {{linear.issue.title}}\n\n  Trigger event: {{type}}\n  Issue URL: {{linear.issue.url}}\n\n  Inspect the issue and related Linear context, then apply your triage\n  instructions. Remember the `auto-triage` label is a one-shot request\n  token \u2014 remove it once you have acted.\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      connections:\n        - provider: linear\n          connection: "{{ $linearConnection }}"\n  slack:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: issue-created\n    event: linear.issue.created\n    connection: "{{ $linearConnection }}"\n    where:\n      $.linear.issue.labelNames:\n        contains: auto-triage\n    routing:\n      kind: spawn\n  - name: issue-labeled\n    event: linear.issue.updated\n    connection: "{{ $linearConnection }}"\n    where:\n      $.linear.updatedFrom.labelNames.added:\n        contains: auto-triage\n    routing:\n      kind: spawn\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a Linear issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage Linear issues\n      labeled `auto-triage`, prepare implementation handoffs, and post\n      ready-work notes to #dev.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-triage-slack.yaml",
+              content: '# Deprecated compatibility entrypoint. New installs should import\n# agents/issue-triage.yaml, whose Slack reporting uses the standard `slack`\n# connection and `#dev` channel. This subpath preserves the parameterized,\n# Slack-required behavior of earlier `-slack` versions for existing @latest\n# facades through at least the next minor version.\nimports:\n  - ./issue-triage.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from GitHub Issues\n  as the source of truth, using issue_read, issue_write, and add_issue_comment\n  through the github tool to inspect, update, and comment on issues.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it with issue_write once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a GitHub issue comment.\n  - Categorize with the most specific existing labels you can justify. Never\n    create GitHub labels \u2014 if the expected label does not exist, note that in\n    a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a GitHub issue comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Remove the `auto-triage` label with issue_write.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue number, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the GitHub issue with the PR link,\n    tests run, and residual risks.\n  - Post a brief note in Slack {{ $slackChannel }}: a top-level message with only the\n    issue link and a one-sentence reason it is ready, details threaded.\n    Slack renders mrkdwn links: <https://url|text>.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn. When posting GitHub comments, append this\n  hidden attribution marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: false\n      connections:\n        - provider: slack\n          connection: "{{ $slackConnection }}"\ntriggers:\n  - name: mention\n    event: chat.message.mentioned\n    connection: "{{ $slackConnection }}"\n    optional: false\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a GitHub issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage newly opened\n      GitHub issues and `auto-triage`-labeled re-triage requests, prepare\n      implementation handoffs, and post ready-work notes to {{ $slackChannel }}.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "agents/issue-triage.yaml",
+              content: 'name: issue-triage\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nidentity:\n  displayName: Issue Triage\n  username: issue-triage\n  avatar:\n    asset: .auto/assets/triage.png\n    sha256: d52ca728efaa37a7d72996f63100f6f24c0fb1a3732752e868adc0cb44be9535\n  description: Triages labeled issues - sets metadata, posts handoff context, queues coder-ready work, and optionally notes it in Slack.\nimports:\n  - ../fragments/environments/agent-runtime.yaml\nsystemPrompt: |\n  You are the issue triage agent for {{ $repoFullName }}. Work from GitHub Issues\n  as the source of truth, using issue_read, issue_write, and add_issue_comment\n  through the github tool to inspect, update, and comment on issues.\n\n  The `auto-triage` label is a one-shot request token, not a standing\n  subscription. Remove it with issue_write once you have acted on the request.\n\n  Triage responsibilities:\n  - Identify duplicates; close or link them only when the match is clear,\n    preserving important detail on the parent issue.\n  - Rank priority from impact, urgency, user signal, and blocked work.\n    Explain non-obvious priority changes in a GitHub issue comment.\n  - Categorize with the most specific existing labels you can justify. Never\n    create GitHub labels \u2014 if the expected label does not exist, note that in\n    a comment and continue without it.\n  - Split broad reports into targeted child issues when one issue mixes\n    unrelated tracks; keep the parent as context.\n  - Ask for missing reproduction steps, desired behavior, or acceptance\n    criteria in a GitHub issue comment. Do not invent requirements.\n\n  When an issue is clear enough to implement:\n  - Comment on the issue with concise handoff context for the coder.\n  - Remove the `auto-triage` label with issue_write.\n  - Call auto.sessions.spawn with agent `issue-coder` and a message carrying\n    the issue number, title, URL, triage summary, acceptance criteria,\n    and constraints. Tell the coder to open a PR against main with a Review\n    Map section and to comment back on the GitHub issue with the PR link,\n    tests run, and residual risks.\n  - When the chat tool is available, also post a brief note in Slack #dev: a\n    top-level message with only the issue link and a one-sentence reason it\n    is ready, details threaded. Slack renders mrkdwn links:\n    <https://url|text>.\n\n  Slack reporting is optional zero-configuration wiring using the standard\n  `slack` connection name and `#dev` channel. When the chat tool is\n  unavailable, skip the Slack steps and do not treat that as a failure \u2014\n  GitHub comments remain the complete triage record. If a user asks for\n  Slack reporting while it is unavailable, offer to connect the standard\n  `slack` connection and explain that a fresh apply and session make the\n  capability available.\n\n  Keep changes small and reversible. Prefer comments that explain what you\n  did over silent metadata churn. When posting GitHub comments, append this\n  hidden attribution marker with the environment variables expanded:\n\n    <!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->\ninitialPrompt: |\n  Triage GitHub issue #{{github.issue.number}}: {{github.issue.title}}\n\n  Trigger event: {{type}}\n  Issue URL: {{github.issue.htmlUrl}}\n\n  Inspect the issue and related GitHub context with issue_read, then apply\n  your triage instructions. Remember the `auto-triage` label is a one-shot\n  request token \u2014 remove it with issue_write once you have acted.\nmounts:\n  - kind: git\n    repository: "{{ $repoFullName }}"\n    mountPath: /workspace/repo\n    ref: main\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: none\n        issues: write\n        checks: none\n        actions: none\nworkingDirectory: /workspace/repo\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - issue_read\n      - issue_write\n      - add_issue_comment\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connections\n      optional: true\n      connections:\n        - provider: slack\n          connection: slack\ntriggers:\n  - name: issue-opened\n    event: github.issue.opened\n    connection: "{{ $githubConnection }}"\n    where:\n      $.github.repository.fullName: "{{ $repoFullName }}"\n      $.github.auto.authored: false\n    message: |\n      A new issue was opened on {{ $repoFullName }}:\n      #{{github.issue.number}} \u2014 {{github.issue.title}}.\n\n      Issue URL: {{github.issue.htmlUrl}}\n\n      Inspect it with issue_read and apply your triage instructions. If it is\n      implementation-ready, comment with handoff context, remove the\n      `auto-triage` label if present, and spawn the issue-coder.\n    routing:\n      kind: bind\n      target: github.issue\n      onUnmatched: spawn\n  - name: issue-labeled\n    event: github.issue.labeled\n    connection: "{{ $githubConnection }}"\n    where:\n      $.github.repository.fullName: "{{ $repoFullName }}"\n      $.github.auto.authored: false\n      $.github.label.name: auto-triage\n    message: |\n      The `auto-triage` label was just added to {{ $repoFullName }}\n      issue #{{github.issue.number}} \u2014 {{github.issue.title}}.\n\n      Issue URL: {{github.issue.htmlUrl}}\n\n      The label is a one-shot re-triage request. Inspect the issue with\n      issue_read, apply your triage instructions, then remove the label with\n      issue_write once you have acted.\n    routing:\n      kind: bind\n      target: github.issue\n      onUnmatched: spawn\n  - name: mention\n    event: chat.message.mentioned\n    connection: slack\n    optional: true\n    where:\n      $.chat.provider: slack\n      $.auto.authored: false\n    message: |\n      {{message.author.userName}} mentioned you on Slack:\n\n      {{message.text}}\n\n      Channel: {{chat.channelId}}\n      Thread: {{chat.threadId}}\n\n      Reply in that thread with chat.send. If the user clearly links or asks\n      about a GitHub issue, triage it. If required context is missing, ask for\n      the issue link. Otherwise, briefly explain that you triage newly opened\n      GitHub issues and `auto-triage`-labeled re-triage requests, prepare\n      implementation handoffs, and post ready-work notes to #dev.\n    routing:\n      kind: spawn\n'
+            },
+            {
+              path: "fragments/environments/agent-runtime.yaml",
+              content: "harness: claude-code\nenvironment:\n  name: agent-runtime\n  image:\n    kind: preset\n    name: node24\n  resources:\n    memoryMB: 8192\n"
+            }
+          ]
         }
       ],
       "@auto/lead-engine": [
@@ -33921,7 +33981,7 @@ var init_hardcoded = __esm({
       "@auto/engineering-tier": "An engineering-tier fleet: senior and junior engineers with PR ownership, a live-iteration designer, and a session introspector.",
       "@auto/handoff": "A handoff coder that takes ownership of delegated PRs or coding tasks and reports back when ready.",
       "@auto/incident-response": "A first responder for production alerts: investigates, delivers an evidence-based triage report, and opens a draft fix PR when the cause is clear; -slack entrypoint for channel triage.",
-      "@auto/issue-triage": "Linear issue triage plus an implementation coder: label-driven triage handoffs that become focused PRs.",
+      "@auto/issue-triage": "Issue triage plus an implementation coder on a GitHub Issues or Linear substrate, with optional Slack reporting; deprecated -slack entrypoints keep the required-Slack behavior.",
       "@auto/lead-engine": "A sourced lead researcher for webhook payloads, direct-session criteria, public web signals, and authorized provider-backed sources; -slack entrypoint for a sales-channel flow.",
       "@auto/onboarding": "Auto's house onboarding guidance, importable as a managed template.",
       "@auto/onboarding-quickstart": "The quickstart template repo's onboarding overlay: composes onto @auto/onboarding with the fork-flow walkthrough beats (site request bar, handoff loop, self-improvement demo).",
@@ -34212,6 +34272,7 @@ var init_src = __esm({
     init_conversation();
     init_conversation_reducer();
     init_connections();
+    init_dormant_capabilities();
     init_github_sync();
     init_github_credentials();
     init_github_mcp_catalog();
@@ -37012,7 +37073,7 @@ var init_package = __esm({
   "package.json"() {
     package_default = {
       name: "@autohq/cli",
-      version: "0.1.408",
+      version: "0.1.409",
       license: "SEE LICENSE IN README.md",
       publishConfig: {
         access: "public"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autohq/cli",
-  "version": "0.1.408",
+  "version": "0.1.409",
   "license": "SEE LICENSE IN README.md",
   "publishConfig": {
     "access": "public"