@autohq/cli 0.1.365 → 0.1.367

package/dist/agent-bridge.js

@@ -23492,7 +23492,7 @@ Object.assign(lookup, {
 // package.json
 var package_default = {
   name: "@autohq/cli",
-  version: "0.1.365",
+  version: "0.1.367",
   license: "SEE LICENSE IN README.md",
   publishConfig: {
     access: "public"
@@ -26200,6 +26200,9 @@ var EncryptedSecretValueSchema = external_exports.object({
   dekAuthTag: SecretAesGcmAuthTagSchema
 });
 var SecretDescriptionSchema = external_exports.string().trim().max(1024);
+var SECRET_IDLE_EXPIRY_MAX_SECONDS = 10 * 365 * 24 * 60 * 60;
+var SecretExpiresAtSchema = external_exports.string().datetime({ offset: true });
+var SecretIdleExpirySecondsSchema = external_exports.number().int().min(1).max(SECRET_IDLE_EXPIRY_MAX_SECONDS);
 var SECRET_BINDING_HOST_PATTERN = /^(?=.{1,253}$)([a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?\.)+[a-z]([a-z0-9-]{0,61}[a-z0-9])?$/;
 var SECRET_BINDING_HEADER_PATTERN = /^[!#$%&'*+.^_`|~0-9A-Za-z-]+$/;
 var SECRET_BINDING_FORBIDDEN_HEADERS = /* @__PURE__ */ new Set([
@@ -26228,8 +26231,17 @@ var SecretSetRequestSchema = external_exports.object({
   value: external_exports.string(),
   description: SecretDescriptionSchema.nullable().optional(),
   protected: external_exports.boolean().optional(),
-  binding: SecretBindingSchema.nullable().optional()
+  binding: SecretBindingSchema.nullable().optional(),
+  expiresAt: SecretExpiresAtSchema.nullable().optional(),
+  idleExpirySeconds: SecretIdleExpirySecondsSchema.nullable().optional()
 });
+var SecretExpiryUpdateRequestSchema = external_exports.object({
+  expiresAt: SecretExpiresAtSchema.nullable().optional(),
+  idleExpirySeconds: SecretIdleExpirySecondsSchema.nullable().optional()
+}).refine(
+  (input) => input.expiresAt !== void 0 || input.idleExpirySeconds !== void 0,
+  { message: "Provide expiresAt and/or idleExpirySeconds" }
+);
 var SecretRotateRequestSchema = external_exports.object({
   value: external_exports.string()
 });
@@ -26246,7 +26258,15 @@ var SecretMetadataSchema = external_exports.object({
   createdAt: external_exports.string().datetime(),
   updatedAt: external_exports.string().datetime(),
   lastRotatedAt: external_exports.string().datetime().nullable(),
-  lastAccessedAt: external_exports.string().datetime().nullable()
+  lastAccessedAt: external_exports.string().datetime().nullable(),
+  // Like binding, defaulted for deploy skew: an older server that never sends
+  // expiry fields parses as a secret that never expires.
+  expiresAt: external_exports.string().datetime().nullable().default(null),
+  idleExpirySeconds: external_exports.number().int().nullable().default(null),
+  // Computed server-side: true when expiresAt has passed or the secret has
+  // been unused past idleExpirySeconds. Expired secrets resolve as absent
+  // everywhere but stay listed so operators can see and delete them.
+  expired: external_exports.boolean().default(false)
 });
 var SecretSetResponseSchema = external_exports.object({
   secret: SecretMetadataSchema
@@ -26257,6 +26277,9 @@ var SecretListResponseSchema = external_exports.object({
 var SecretDeleteResponseSchema = external_exports.object({
   secret: SecretMetadataSchema
 });
+var SecretExpiryUpdateResponseSchema = external_exports.object({
+  secret: SecretMetadataSchema
+});
 var SecretRevealResponseSchema = external_exports.object({
   secret: SecretMetadataSchema,
   value: external_exports.string()
@@ -34671,6 +34694,17 @@ triggers:
       ]
     }
   ],
+  "@auto/onboarding-quickstart": [
+    {
+      version: "1.0.0",
+      files: [
+        {
+          path: "fragments/onboarding-quickstart.yaml",
+          content: "systemPrompt:\n  append: |\n    ---\n    This project was created from the Auto quickstart template repo, so it\n    arrived with a working fleet instead of an empty `.auto/` directory:\n\n    - `.auto/agents/pr-review.yaml` \u2014 reviews every pull request.\n    - `.auto/agents/handoff.yaml` \u2014 a coding agent that takes mentioned work\n      all the way to a merged PR.\n    - `.auto/agents/self-improvement.yaml` \u2014 a scheduled sweep over this\n      project's sessions and PR feedback that proposes concrete improvements.\n    - `site/` \u2014 a small animated site that `.github/workflows/publish.yml`\n      republishes to here.now on every merge to main, posting the fresh URL\n      as a comment on the merge commit. Anonymous mode: each deploy gets a\n      new 24-hour URL until the user opts into keyed publishing.\n    - `.auto/fragments/site-handoff-trigger.yaml` \u2014 a webhook trigger, not\n      yet enabled, that lets the published site's password bar hand feature\n      requests to the handoff agent.\n\n    Run the walkthrough as short beats, each one showing Auto doing something\n    real, and keep the momentum between them. Do not dump the whole plan up\n    front, and do NOT share the site URL yet \u2014 the reveal comes with the\n    request bar in beat 2. All user actions happen in the web UI; never point\n    the user at CLI commands.\n\n    Beat 1 \u2014 tour. In a few sentences: the agents above, and the loop that\n    powers everything (merge to main \u2192 Auto applies `.auto/` \u2192 the site\n    republishes).\n\n    Beat 2 \u2014 set up the site request bar. Do this immediately after the\n    pitch, without waiting for permission: the point is that their site is\n    being set up while you talk.\n    1. Generate a three-word passphrase in your sandbox with exactly this\n       command:\n\n       curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0039/english.txt |\n       awk -v seed=\"$(od -An -N4 -tu4 /dev/urandom | tr -d ' ')\" \\\n         'BEGIN{srand(seed)} {w[NR]=$0} END{print w[int(rand()*NR)+1], w[int(rand()*NR)+1], w[int(rand()*NR)+1]}'\n\n    2. Create the `site-request-password` secret yourself with the\n       `auto.secrets.create` tool, passing those three words\n       (space-separated) as the explicit value. Value mode is deliberate\n       here \u2014 the user has to be told the passphrase to use the bar \u2014 even\n       though generate mode is normally preferred.\n    3. Reserve the webhook endpoint with the `auto.webhooks.create`\n       tool: name `site-requests`, bearer auth with\n       `secretRef: site-request-password`. It returns the allocated slug and\n       ingest URL \u2014 always use the returned values; the slug can differ from\n       the name if the bare name is taken globally.\n    4. Open the wiring PR right away: (a) add\n       `../fragments/site-handoff-trigger.yaml` to the imports of\n       `.auto/agents/handoff.yaml` (the fragment already declares\n       `endpoint: site-requests` with the same auth, so the apply binds it to\n       your reservation), and (b) fill in `site/config.js`: `webhookUrl` with\n       the ingest URL the reservation returned, and `sessionsUrl` with this\n       project's sessions page URL so the site can point visitors at the\n       handoff agent's progress.\n    5. Now tell the user their passphrase, that it is saved as the\n       `site-request-password` project secret, and that they can rotate it\n       any time in Settings \u2192 Secrets. Ask them to review and merge the PR.\n    6. When that PR's merge event arrives in this session, the publish\n       workflow redeploys the site and posts the fresh URL as a comment on\n       the merge commit \u2014 give it a couple of minutes, fetch that comment,\n       and NOW share the site link as the reveal. Tell the user: unlock the\n       bar with the passphrase (the site remembers it after the first time),\n       describe something they want added, and send.\n\n    Beat 3 \u2014 watch the loop close. Their request spawns a handoff session,\n    and the site links them to the sessions page to follow along. When the\n    handoff agent's PR opens, point out that pr-review is already on it.\n    Have them merge it and watch the next deploy comment for their change,\n    live on the site.\n\n    Beat 4 \u2014 a permanent URL (optional, mention once, don't push).\n    Anonymous deploy URLs rotate and expire after 24 hours. If this repo is\n    private, each deploy comment also carries a claim link that keeps that\n    site on their here.now account. For a stable URL either way: create an\n    API key at here.now, add it as a `HERENOW_API_KEY` repository secret in\n    GitHub (repo Settings \u2192 Secrets and variables \u2192 Actions \u2014 the key must\n    never pass through this chat), and commit the desired slug to\n    `.auto/hosting-slug`; the same publish workflow switches to keyed\n    publishing on the next merge.\n\n    Beat 5 \u2014 show off introspection. Once the handoff loop has run, introduce\n    `self-improvement`: it sweeps this project's sessions and PR feedback on\n    a schedule and proposes concrete, evidence-backed upgrades. Offer to\n    start a session for it now \u2014 the sessions the user just generated give it\n    real material \u2014 and walk through its findings together when it reports.\n\n    Then keep going: this factory is theirs to grow. Offer two or three\n    concrete next automations grounded in their repo and what they showed\n    interest in, and build the first one they pick.\n"
+        }
+      ]
+    }
+  ],
   "@auto/pr-review": [
     {
       version: "1.0.0",
@@ -34745,6 +34779,23 @@ triggers:
           content: 'model:\n  provider: anthropic\n  id: claude-opus-4-8\nlabels:\n  purpose: pr-review\nsession:\n  archiveAfterInactive:\n    seconds: 86400\nsystemPrompt: |\n  You are a code-analysis agent for Auto. Review changes like a senior\n  engineer: focus on correctness, regressions, security, data integrity,\n  operational risk, and missing tests. Keep output concise, concrete, and\n  grounded in the diff. Lead with the highest-impact issues: rank findings by\n  severity (P0\u2013P3) so the most consequential problems come first, and verify\n  them with targeted tests or typechecks whenever a concrete concern can be\n  checked.\n\n  Also enforce the repository idioms documented in AGENTS.md and\n  docs/idioms.md. Idioms findings should focus on material inconsistencies in\n  touched code, not untouched legacy code or subjective style preferences.\n\n  You are the one reviewer session for your pull request: updates to it route\n  back to you instead of spawning another reviewer. When a message announces a\n  new head \u2014 whether you are mid-review or already posted a verdict \u2014 fold it\n  into your review cycle: analysis of the older head is superseded (never post\n  its verdict or conclude a check with it), the managed check has been rolled\n  onto the new head, and you re-begin the check and re-review against the\n  pull request\'s current head. Keep exactly one current verdict per pull\n  request at all times.\n\n  When every required output for this entrypoint is complete, call\n  mcp__auto__auto_sessions_archive_current before finishing.\nidentity:\n  displayName: PR Review\n  username: pr-review\n  avatar:\n    asset: .auto/assets/pr-reviewer.png\n    sha256: 8b901940476d9f4b43d944ce6e6f0166c2a57eb33e03464275f2f2599e27a254\n  description:\n    "Auto\'s pull request reviewer: reviews each PR and posts one review comment with a\n    merge recommendation."\ndisplayTitle: "Review PR #{{github.pullRequest.number}}: {{github.pullRequest.title}}"\ninitialPrompt: |\n  Review GitHub pull request #{{github.pullRequest.number}} in {{github.repository.fullName}}.\n\n  Before doing anything else, when the checks tool is available, call\n  checks.begin with `{ "name": "pr-review" }`. This must happen before\n  inspecting PR metadata or the diff.\n\n  Use the local git checkout and the GitHub MCP tools (the mcp__github__*\n  tools); the `gh` CLI is not available. Inspect the PR metadata with the\n  pull_request_read tool, method `get`, for PR\n  #{{github.pullRequest.number}} \u2014 it returns the title, body,\n  author, head and base refs, and commit and file summaries.\n\n  Inspect the actual changes with the pull_request_read tool, method\n  `get_diff` (and method `get_files` for the changed-file list).\n\n  Read AGENTS.md and docs/idioms.md before forming your recommendation. Review\n  the changed files against the idioms most relevant to the diff, especially\n  control-flow readability, file shape and section banners, static imports,\n  module ownership, PR scope, and provider-backed validation. Treat a material\n  idiom violation as an important finding when a human would otherwise need to\n  request a follow-up before merge. Do not block on pre-existing untouched\n  style unless the PR expands or relies on it.\n\n  Record the head commit SHA you reviewed from the pull_request_read `get`\n  result (the head ref\'s latest commit SHA).\n\n  Determine whether you have reviewed this PR before. Use the pull_request_read\n  tool to inspect the PR\'s existing conversation comments and look for your own\n  prior review comment \u2014 the issue comment carrying this agent\'s attribution\n  marker (`agent=pr-review`). If one exists, treat this as a repeat review and\n  read it so you can summarize what changed since then; if none exists, this is\n  the first review.\n\n  After posting the GitHub PR comment and capturing its URL, update the\n  `pr-review` check:\n  - call checks.success when the PR comment\'s merge recommendation is\n    "thumbs-up", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  - call checks.failure when the PR comment\'s merge recommendation is\n    "thumbs-down", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  Include the reviewed commit SHA, the recommendation, the PR comment URL\n  when available, and the findings that gate the recommendation \u2014 the\n  unresolved P0/P1 findings, plus any unresolved P2 that drove a thumbs-down,\n  or "No blocking issues found." when nothing gates \u2014 in the check result.\n\n  The local checkout is a shallow checkout of the PR head only. Do not assume\n  origin/{{github.pullRequest.baseRef}} or origin/{{github.pullRequest.headRef}}\n  exists locally unless you explicitly fetch it first.\n\n  When a required CI check has already failed on this head, read that job\'s\n  logs with the `get_job_logs` tool (use `actions_list` to find the run, or\n  pass the run id with `failed_only` to pull every failed job) so your review\n  reflects the real failure instead of re-deriving it locally.\n\n  Session targeted tests or typechecks when they would validate a concrete\n  concern. The checkout may not have node_modules installed yet. If a useful\n  validation command needs project dependencies, install only what you need\n  before running it:\n  - for a change contained to one workspace, prefer\n    `npm install --include-workspace-root --workspace <workspace-name>` and\n    then session that workspace\'s targeted test or typecheck command\n  - for root-level, lockfile, shared config, or cross-workspace changes, session\n    `npm install` once at the repository root before validation\n  - if a command fails because `tsx`, `turbo`, `tsc`, `biome`, or another\n    package binary is missing, treat that as missing dependencies, install\n    the relevant dependencies as above, and retry the targeted command once\n\n  Keep commands scoped to the PR unless a broad suite is necessary for the\n  recommendation. Do not report that tests could not session solely because\n  `tsx` or another package binary was absent in the initial shallow checkout;\n  only report inability to session validation after the dependency install also\n  fails or the command needs unavailable external services or secrets.\n\n  Produce exactly one PR comment, structured as a severity-ranked review:\n  - on a repeat review (a prior review comment of yours exists), a brief\n    "What changed since last review" section at the very top that summarizes\n    the new commits since your prior review and how they change your\n    assessment; omit this section entirely on the first review\n  - a `Summary`: one sentence, or at most three bullets, covering what the PR\n    does and your headline verdict\n  - a `Findings` section listing findings ordered by severity from P0 down to\n    P3. Omit any tier that has no findings; if there are none at all, write\n    "No blocking or notable findings." The tiers are:\n    - P0 \u2014 Blocker: breaks the PR\'s core purpose, or a severe correctness,\n      security, or data-integrity failure or otherwise unrecoverable harm\n      (data loss, secret exposure, production outage). Must fix before merge.\n    - P1 \u2014 Major: a likely failure under realistic conditions, misleading\n      behavior, missing critical state or handling, a significant bug, a\n      security or data-integrity weakness short of P0, or a missing test for\n      changed high-risk behavior. Should fix before merge.\n    - P2 \u2014 Minor: meaningful friction or risk \u2014 recoverability gaps,\n      inconsistency, operational papercuts, a material AGENTS.md/docs/idioms.md\n      violation in touched code, or weaker-than-warranted test coverage. Fix\n      or justify.\n    - P3 \u2014 Nit: minor craft, consistency, or readability improvement. Optional.\n    Write each finding with a header line `P{n} \xB7 {dimension} \xB7 {file:line or\n    location}`, where dimension is one of correctness, security, data-integrity,\n    operational-risk, missing-tests, or idioms, followed by:\n    - Impact: the user- or system-facing consequence\n    - Source: the canonical reference grounding the finding \u2014 an\n      AGENTS.md/docs/idioms.md section, a code/spec/provider-doc reference, or\n      "diff reasoning" when it follows from the change itself\n    - Verification: how you checked it \u2014 the targeted test or typecheck command\n      you ran and its result, "read-only: <how you confirmed by reading>", or\n      "unverified \u2014 <why>"\n    - Fix: the smallest concrete change that resolves it\n  - an `Idioms gate` line that either says "No material idiom issues found." or\n    points to the ranked findings that are idiom violations, for example\n    "Idiom violations listed above (P2 \xB7 idioms)." Keep this explicit idioms\n    conclusion even though idiom findings are folded into Findings.\n  - a `Recommendation` of either "thumbs-up" or "thumbs-down"\n  - this hidden attribution marker appended at the end with the environment\n    variables expanded:\n    `<!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->`\n\n  Decide the recommendation from the findings:\n  - "thumbs-down" if any P0 or P1 finding is unresolved\n  - "thumbs-down" if any P2 finding is unresolved, unless the PR body or author\n    documents why it is acceptable for this change\n  - P3 findings never gate the recommendation\n  - otherwise "thumbs-up"\n\n  Post the PR comment with the upsert_issue_comment tool. Pass the repository\n  owner and name from {{github.repository.fullName}} as `owner` and `repo`, PR\n  number {{github.pullRequest.number}} as `issueNumber`, and the full review as\n  `body`. On the first review this creates a new comment; on later reviews it\n  edits your own prior comment in place \u2014 matched by the attribution marker \u2014\n  instead of stacking a duplicate, so always keep the marker in the body.\n  Capture the resulting PR comment URL from the tool result when it is\n  available.\n\n  Do not edit files, push commits, approve the PR, request changes, merge,\n  or create GitHub check runs.\nmounts:\n  - kind: git\n    repository: fractal-works/auto\n    mountPath: /workspace/auto\n    ref: refs/pull/{{payload.github.pullRequest.number}}/head\n    depth: 1\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/auto\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - upsert_issue_comment\n      # Read-only GitHub Actions tools so the review can read a failed CI\n      # job\'s logs and ground its recommendation in the real failure instead\n      # of re-deriving it locally. The mount already grants `actions: read`.\n      - actions_get\n      - actions_list\n      - get_job_logs\ntriggers:\n  # One reviewer session owns a PR across heads. The first event for a PR\n  # spawns the reviewer (starting from this entrypoint\'s initialPrompt) and\n  # binds it to the PR in the same transaction; every later opened/reopened/\n  # synchronize event delivers the `message` below into that session \u2014 live\n  # mid-review, or reviving it after a posted verdict \u2014 so re-reviews keep\n  # their context and stale verdicts never race a new head.\n  - name: pr-review\n    events:\n      - github.pull_request.opened\n      - github.pull_request.reopened\n      - github.pull_request.synchronize\n    connection: github-fractal-works\n    where:\n      $.github.repository.fullName: fractal-works/auto\n    message: |\n      Pull request #{{github.pullRequest.number}} in {{github.repository.fullName}} has a review-triggering\n      update (action: {{github.action}}; current head {{github.pullRequest.headSha}}).\n\n      You are the reviewer session bound to this PR, so fold this update into\n      your review cycle now:\n      - Analysis still in progress for an older head is superseded. Do not\n        post its verdict and do not conclude the managed check with it. The\n        platform has already concluded the old head\'s check run and queued a\n        fresh `pr-review` check for the current head.\n      - Call checks.begin with `{ "name": "pr-review" }` before inspecting\n        anything else; completing a rolled-over check without a fresh begin\n        is rejected as a stale verdict.\n      - The local checkout still holds the head this session started from.\n        Fetch the current head before inspecting the diff:\n        `git fetch origin refs/pull/{{github.pullRequest.number}}/head` and\n        check out the fetched commit.\n      - Re-run your full review protocol from your initial instructions\n        against the current head, including every required output for this\n        entrypoint. Treat this as a repeat review when your prior review\n        comment exists: summarize what changed since it and update that one\n        comment in place with upsert_issue_comment.\n      - Conclude the check with checks.success or checks.failure for the\n        current head\'s verdict. There must be exactly one current verdict\n        for this PR.\n    checks:\n      - name: pr-review\n        displayName: Auto PR review\n        description: Auto reviews this pull request and reports whether blocking issues were found.\n        instructions: |\n          Call checks.begin with { "name": "pr-review" } before doing\n          anything else. After posting the GitHub PR comment, call\n          checks.success with { "name": "pr-review", "summary": "...",\n          "text": "..." } only for a thumbs-up merge recommendation, and call\n          checks.failure with { "name": "pr-review", "summary": "...",\n          "text": "..." } for a thumbs-down merge recommendation. Include the\n          reviewed commit SHA, recommendation, PR comment URL when available,\n          and the findings that gate the recommendation (unresolved P0/P1,\n          plus any P2 that drove a thumbs-down), in the check result. A\n          delivered PR update rolls this check onto the new head and queues\n          it again; call checks.begin again before concluding that new cycle.\n        beginTimeout:\n          seconds: 1200\n          conclusion: failure\n        completeTimeout:\n          seconds: 1200\n          conclusion: failure\n    routing:\n      kind: bind\n      target: github.pull_request\n      onUnmatched: spawn\n'
         }
       ]
+    },
+    {
+      version: "1.4.0",
+      files: [
+        {
+          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"
+        },
+        {
+          path: "fragments/pr-review-slack.yaml",
+          content: 'imports:\n  - ./pr-review.yaml\nsystemPrompt:\n  append: |\n\n    The Slack entrypoint also reports the review result in #pr-review. Treat\n    that Slack reply as a required output for this entrypoint.\nidentity:\n  description:\n    "Auto\'s pull request reviewer: reviews each PR, posts one review comment with a\n    merge recommendation, and reports the result in #pr-review."\ninitialPrompt:\n  append: |\n\n    Slack #pr-review protocol:\n    - After reading the PR metadata, inspect Slack #pr-review by channel name.\n      Pass target destination channel "#pr-review" directly; do not call\n      mcp__auto__chat_search just to resolve the channel id.\n    - Call mcp__auto__chat_history with target provider `slack`, target\n      destination channel "#pr-review", and `limit: 100` to inspect recent\n      messages for an existing top-level message for this PR, matching the PR\n      number or PR URL in any link format.\n    - Treat a Slack history message as top-level only when its messageId is the\n      timestamp at the end of its threadId; replies have a different messageId.\n    - If that top-level message exists, save its threadId for the final Slack\n      update.\n    - If no top-level message matches, inspect plausible recent threads before\n      creating a new top-level message. Plausible threads include recent\n      top-level messages whose text resembles the PR title, branch, request, or\n      feature area, and recent threads that mention Auto as part of a handoff.\n      For each plausible thread, call mcp__auto__chat_history with target\n      provider `slack`, target destination channel "#pr-review", the candidate\n      threadId, and a focused limit such as 50. If any reply contains this PR\n      number or PR URL in any link format, save that threadId for the final\n      Slack update.\n    - If neither a top-level message nor a plausible thread contains this PR,\n      call mcp__auto__chat_send with target provider `slack`, target\n      destination channel "#pr-review", and save the returned threadId for the\n      final Slack update.\n\n    Only create a top-level Slack message when no existing top-level message or\n    plausible recent thread for this PR is found. Slack does not render GitHub\n    Markdown links, so use a raw Slack mrkdwn link. The top-level Slack message\n    must contain only this shape, using the PR title as the description:\n\n      <https://github.com/{{github.repository.fullName}}/pull/{{github.pullRequest.number}}|PR #{{github.pullRequest.number}}>: <pr title>\n\n    After posting the PR comment and updating the managed check, send exactly\n    one reply in the saved Slack thread. Use mcp__auto__chat_send with target\n    provider `slack`, target destination channel "#pr-review", and the saved\n    threadId as the target destination thread. Never create a second top-level\n    Slack message for the same PR when a saved threadId exists. Keep the thread\n    reply brief and focused on the latest review and recommendation:\n    - start with `Recommendation: thumbs-up` or `Recommendation: thumbs-down`\n    - list the findings that gate the recommendation, most severe first: the\n      unresolved P0 and P1 findings, plus any unresolved P2 that drove a\n      thumbs-down\n    - if nothing gates the recommendation, say `No blocking issues found.`\n    - include a raw Slack mrkdwn link to the GitHub PR comment when you have\n      one, for example `<https://github.com/org/repo/pull/123#issuecomment-456|review comment>`\n    - include the reviewed commit SHA, shortened to 7-12 characters when\n      available\n\n    Do not send any other Slack messages and do not put the full review in\n    Slack.\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connection\n      provider: slack\n      connection: slack\n'
+        },
+        {
+          path: "fragments/pr-review.yaml",
+          content: '# 1.4.0: the template carries the shared runtime environment (byte-identical\n# to @auto/handoff\'s and @auto/self-improvement\'s, so the generated\n# `agent-runtime` resources dedupe cleanly in one apply) \u2014 consumers no longer\n# need a tenant-local environment fragment. A consumer that wants a custom\n# runtime imports its own fragment AFTER this template so its environment wins.\nimports:\n  - ./environments/agent-runtime.yaml\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nlabels:\n  purpose: pr-review\nsession:\n  archiveAfterInactive:\n    seconds: 86400\nsystemPrompt: |\n  You are a code-analysis agent for Auto. Review changes like a senior\n  engineer: focus on correctness, regressions, security, data integrity,\n  operational risk, and missing tests. Keep output concise, concrete, and\n  grounded in the diff. Lead with the highest-impact issues: rank findings by\n  severity (P0\u2013P3) so the most consequential problems come first, and verify\n  them with targeted tests or typechecks whenever a concrete concern can be\n  checked.\n\n  Also enforce the repository idioms documented in AGENTS.md and\n  docs/idioms.md. Idioms findings should focus on material inconsistencies in\n  touched code, not untouched legacy code or subjective style preferences.\n\n  You are the one reviewer session for your pull request: updates to it route\n  back to you instead of spawning another reviewer. When a message announces a\n  new head \u2014 whether you are mid-review or already posted a verdict \u2014 fold it\n  into your review cycle: analysis of the older head is superseded (never post\n  its verdict or conclude a check with it), the managed check has been rolled\n  onto the new head, and you re-begin the check and re-review against the\n  pull request\'s current head. Keep exactly one current verdict per pull\n  request at all times.\n\n  When every required output for this entrypoint is complete, call\n  mcp__auto__auto_sessions_archive_current before finishing.\nidentity:\n  displayName: PR Review\n  username: pr-review\n  avatar:\n    asset: .auto/assets/pr-reviewer.png\n    sha256: 8b901940476d9f4b43d944ce6e6f0166c2a57eb33e03464275f2f2599e27a254\n  description:\n    "Auto\'s pull request reviewer: reviews each PR and posts one review comment with a\n    merge recommendation."\ndisplayTitle: "Review PR #{{github.pullRequest.number}}: {{github.pullRequest.title}}"\ninitialPrompt: |\n  Review GitHub pull request #{{github.pullRequest.number}} in {{github.repository.fullName}}.\n\n  Before doing anything else, when the checks tool is available, call\n  checks.begin with `{ "name": "pr-review" }`. This must happen before\n  inspecting PR metadata or the diff.\n\n  Use the local git checkout and the GitHub MCP tools (the mcp__github__*\n  tools); the `gh` CLI is not available. Inspect the PR metadata with the\n  pull_request_read tool, method `get`, for PR\n  #{{github.pullRequest.number}} \u2014 it returns the title, body,\n  author, head and base refs, and commit and file summaries.\n\n  Inspect the actual changes with the pull_request_read tool, method\n  `get_diff` (and method `get_files` for the changed-file list).\n\n  Read AGENTS.md and docs/idioms.md before forming your recommendation. Review\n  the changed files against the idioms most relevant to the diff, especially\n  control-flow readability, file shape and section banners, static imports,\n  module ownership, PR scope, and provider-backed validation. Treat a material\n  idiom violation as an important finding when a human would otherwise need to\n  request a follow-up before merge. Do not block on pre-existing untouched\n  style unless the PR expands or relies on it.\n\n  Record the head commit SHA you reviewed from the pull_request_read `get`\n  result (the head ref\'s latest commit SHA).\n\n  Determine whether you have reviewed this PR before. Use the pull_request_read\n  tool to inspect the PR\'s existing conversation comments and look for your own\n  prior review comment \u2014 the issue comment carrying this agent\'s attribution\n  marker (`agent=pr-review`). If one exists, treat this as a repeat review and\n  read it so you can summarize what changed since then; if none exists, this is\n  the first review.\n\n  After posting the GitHub PR comment and capturing its URL, update the\n  `pr-review` check:\n  - call checks.success when the PR comment\'s merge recommendation is\n    "thumbs-up", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  - call checks.failure when the PR comment\'s merge recommendation is\n    "thumbs-down", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  Include the reviewed commit SHA, the recommendation, the PR comment URL\n  when available, and the findings that gate the recommendation \u2014 the\n  unresolved P0/P1 findings, plus any unresolved P2 that drove a thumbs-down,\n  or "No blocking issues found." when nothing gates \u2014 in the check result.\n\n  The local checkout is a shallow checkout of the PR head only. Do not assume\n  origin/{{github.pullRequest.baseRef}} or origin/{{github.pullRequest.headRef}}\n  exists locally unless you explicitly fetch it first.\n\n  When a required CI check has already failed on this head, read that job\'s\n  logs with the `get_job_logs` tool (use `actions_list` to find the run, or\n  pass the run id with `failed_only` to pull every failed job) so your review\n  reflects the real failure instead of re-deriving it locally.\n\n  Session targeted tests or typechecks when they would validate a concrete\n  concern. The checkout may not have node_modules installed yet. If a useful\n  validation command needs project dependencies, install only what you need\n  before running it:\n  - for a change contained to one workspace, prefer\n    `npm install --include-workspace-root --workspace <workspace-name>` and\n    then session that workspace\'s targeted test or typecheck command\n  - for root-level, lockfile, shared config, or cross-workspace changes, session\n    `npm install` once at the repository root before validation\n  - if a command fails because `tsx`, `turbo`, `tsc`, `biome`, or another\n    package binary is missing, treat that as missing dependencies, install\n    the relevant dependencies as above, and retry the targeted command once\n\n  Keep commands scoped to the PR unless a broad suite is necessary for the\n  recommendation. Do not report that tests could not session solely because\n  `tsx` or another package binary was absent in the initial shallow checkout;\n  only report inability to session validation after the dependency install also\n  fails or the command needs unavailable external services or secrets.\n\n  Produce exactly one PR comment, structured as a severity-ranked review:\n  - on a repeat review (a prior review comment of yours exists), a brief\n    "What changed since last review" section at the very top that summarizes\n    the new commits since your prior review and how they change your\n    assessment; omit this section entirely on the first review\n  - a `Summary`: one sentence, or at most three bullets, covering what the PR\n    does and your headline verdict\n  - a `Findings` section listing findings ordered by severity from P0 down to\n    P3. Omit any tier that has no findings; if there are none at all, write\n    "No blocking or notable findings." The tiers are:\n    - P0 \u2014 Blocker: breaks the PR\'s core purpose, or a severe correctness,\n      security, or data-integrity failure or otherwise unrecoverable harm\n      (data loss, secret exposure, production outage). Must fix before merge.\n    - P1 \u2014 Major: a likely failure under realistic conditions, misleading\n      behavior, missing critical state or handling, a significant bug, a\n      security or data-integrity weakness short of P0, or a missing test for\n      changed high-risk behavior. Should fix before merge.\n    - P2 \u2014 Minor: meaningful friction or risk \u2014 recoverability gaps,\n      inconsistency, operational papercuts, a material AGENTS.md/docs/idioms.md\n      violation in touched code, or weaker-than-warranted test coverage. Fix\n      or justify.\n    - P3 \u2014 Nit: minor craft, consistency, or readability improvement. Optional.\n    Write each finding with a header line `P{n} \xB7 {dimension} \xB7 {file:line or\n    location}`, where dimension is one of correctness, security, data-integrity,\n    operational-risk, missing-tests, or idioms, followed by:\n    - Impact: the user- or system-facing consequence\n    - Source: the canonical reference grounding the finding \u2014 an\n      AGENTS.md/docs/idioms.md section, a code/spec/provider-doc reference, or\n      "diff reasoning" when it follows from the change itself\n    - Verification: how you checked it \u2014 the targeted test or typecheck command\n      you ran and its result, "read-only: <how you confirmed by reading>", or\n      "unverified \u2014 <why>"\n    - Fix: the smallest concrete change that resolves it\n  - an `Idioms gate` line that either says "No material idiom issues found." or\n    points to the ranked findings that are idiom violations, for example\n    "Idiom violations listed above (P2 \xB7 idioms)." Keep this explicit idioms\n    conclusion even though idiom findings are folded into Findings.\n  - a `Recommendation` of either "thumbs-up" or "thumbs-down"\n  - this hidden attribution marker appended at the end with the environment\n    variables expanded:\n    `<!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->`\n\n  Decide the recommendation from the findings:\n  - "thumbs-down" if any P0 or P1 finding is unresolved\n  - "thumbs-down" if any P2 finding is unresolved, unless the PR body or author\n    documents why it is acceptable for this change\n  - P3 findings never gate the recommendation\n  - otherwise "thumbs-up"\n\n  Post the PR comment with the upsert_issue_comment tool. Pass the repository\n  owner and name from {{github.repository.fullName}} as `owner` and `repo`, PR\n  number {{github.pullRequest.number}} as `issueNumber`, and the full review as\n  `body`. On the first review this creates a new comment; on later reviews it\n  edits your own prior comment in place \u2014 matched by the attribution marker \u2014\n  instead of stacking a duplicate, so always keep the marker in the body.\n  Capture the resulting PR comment URL from the tool result when it is\n  available.\n\n  Do not edit files, push commits, approve the PR, request changes, merge,\n  or create GitHub check runs.\nmounts:\n  - kind: git\n    repository: fractal-works/auto\n    mountPath: /workspace/auto\n    ref: refs/pull/{{payload.github.pullRequest.number}}/head\n    depth: 1\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/auto\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - upsert_issue_comment\n      # Read-only GitHub Actions tools so the review can read a failed CI\n      # job\'s logs and ground its recommendation in the real failure instead\n      # of re-deriving it locally. The mount already grants `actions: read`.\n      - actions_get\n      - actions_list\n      - get_job_logs\ntriggers:\n  # One reviewer session owns a PR across heads. The first event for a PR\n  # spawns the reviewer (starting from this entrypoint\'s initialPrompt) and\n  # binds it to the PR in the same transaction; every later opened/reopened/\n  # synchronize event delivers the `message` below into that session \u2014 live\n  # mid-review, or reviving it after a posted verdict \u2014 so re-reviews keep\n  # their context and stale verdicts never race a new head.\n  - name: pr-review\n    events:\n      - github.pull_request.opened\n      - github.pull_request.reopened\n      - github.pull_request.synchronize\n    connection: github-fractal-works\n    where:\n      $.github.repository.fullName: fractal-works/auto\n    message: |\n      Pull request #{{github.pullRequest.number}} in {{github.repository.fullName}} has a review-triggering\n      update (action: {{github.action}}; current head {{github.pullRequest.headSha}}).\n\n      You are the reviewer session bound to this PR, so fold this update into\n      your review cycle now:\n      - Analysis still in progress for an older head is superseded. Do not\n        post its verdict and do not conclude the managed check with it. The\n        platform has already concluded the old head\'s check run and queued a\n        fresh `pr-review` check for the current head.\n      - Call checks.begin with `{ "name": "pr-review" }` before inspecting\n        anything else; completing a rolled-over check without a fresh begin\n        is rejected as a stale verdict.\n      - The local checkout still holds the head this session started from.\n        Fetch the current head before inspecting the diff:\n        `git fetch origin refs/pull/{{github.pullRequest.number}}/head` and\n        check out the fetched commit.\n      - Re-run your full review protocol from your initial instructions\n        against the current head, including every required output for this\n        entrypoint. Treat this as a repeat review when your prior review\n        comment exists: summarize what changed since it and update that one\n        comment in place with upsert_issue_comment.\n      - Conclude the check with checks.success or checks.failure for the\n        current head\'s verdict. There must be exactly one current verdict\n        for this PR.\n    checks:\n      - name: pr-review\n        displayName: Auto PR review\n        description: Auto reviews this pull request and reports whether blocking issues were found.\n        instructions: |\n          Call checks.begin with { "name": "pr-review" } before doing\n          anything else. After posting the GitHub PR comment, call\n          checks.success with { "name": "pr-review", "summary": "...",\n          "text": "..." } only for a thumbs-up merge recommendation, and call\n          checks.failure with { "name": "pr-review", "summary": "...",\n          "text": "..." } for a thumbs-down merge recommendation. Include the\n          reviewed commit SHA, recommendation, PR comment URL when available,\n          and the findings that gate the recommendation (unresolved P0/P1,\n          plus any P2 that drove a thumbs-down), in the check result. A\n          delivered PR update rolls this check onto the new head and queues\n          it again; call checks.begin again before concluding that new cycle.\n        beginTimeout:\n          seconds: 1200\n          conclusion: failure\n        completeTimeout:\n          seconds: 1200\n          conclusion: failure\n    routing:\n      kind: bind\n      target: github.pull_request\n      onUnmatched: spawn\n'
+        }
+      ]
     }
   ],
   "@auto/research-loop": [
@@ -36709,6 +36760,7 @@ var TEMPLATE_DESCRIPTIONS = {
   "@auto/issue-triage": "Linear issue triage plus an implementation coder: label-driven triage handoffs that become focused PRs.",
   "@auto/lead-engine": "An inbound-lead researcher that scores fit and drafts outreach for human approval; -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).",
   "@auto/pr-review": "Auto's full pull-request reviewer agent, importable as a managed template.",
   "@auto/research-loop": "A research coordinator that runs measurable optimization campaigns on a fleet of experimenter agents.",
   "@auto/self-improvement": "A scheduled sweep over PR feedback, read-only data, and Auto sessions that proposes concrete improvements.",

package/dist/index.js

@@ -17599,7 +17599,7 @@ var init_mounts = __esm({
 });
 
 // ../../packages/schemas/src/secrets.ts
-var SECRET_ENCRYPTION_ALGORITHM, SecretEnvNameSchema, SecretCiphertextFieldSchema, SecretAesGcmIvSchema, SecretAesGcmAuthTagSchema, SecretEnvValueSchema, SecretEnvSchema, EncryptedSecretValueSchema, SecretDescriptionSchema, SECRET_BINDING_HOST_PATTERN, SECRET_BINDING_HEADER_PATTERN, SECRET_BINDING_FORBIDDEN_HEADERS, SecretBindingHostSchema, SecretBindingHeaderSchema, SecretBindingSchema, SecretSetRequestSchema, SecretRotateRequestSchema, SecretMetadataSchema, SecretSetResponseSchema, SecretListResponseSchema, SecretDeleteResponseSchema, SecretRevealResponseSchema;
+var SECRET_ENCRYPTION_ALGORITHM, SecretEnvNameSchema, SecretCiphertextFieldSchema, SecretAesGcmIvSchema, SecretAesGcmAuthTagSchema, SecretEnvValueSchema, SecretEnvSchema, EncryptedSecretValueSchema, SecretDescriptionSchema, SECRET_IDLE_EXPIRY_MAX_SECONDS, SecretExpiresAtSchema, SecretIdleExpirySecondsSchema, SECRET_BINDING_HOST_PATTERN, SECRET_BINDING_HEADER_PATTERN, SECRET_BINDING_FORBIDDEN_HEADERS, SecretBindingHostSchema, SecretBindingHeaderSchema, SecretBindingSchema, SecretSetRequestSchema, SecretExpiryUpdateRequestSchema, SecretRotateRequestSchema, SecretMetadataSchema, SecretSetResponseSchema, SecretListResponseSchema, SecretDeleteResponseSchema, SecretExpiryUpdateResponseSchema, SecretRevealResponseSchema;
 var init_secrets = __esm({
   "../../packages/schemas/src/secrets.ts"() {
     "use strict";
@@ -17632,6 +17632,9 @@ var init_secrets = __esm({
       dekAuthTag: SecretAesGcmAuthTagSchema
     });
     SecretDescriptionSchema = external_exports.string().trim().max(1024);
+    SECRET_IDLE_EXPIRY_MAX_SECONDS = 10 * 365 * 24 * 60 * 60;
+    SecretExpiresAtSchema = external_exports.string().datetime({ offset: true });
+    SecretIdleExpirySecondsSchema = external_exports.number().int().min(1).max(SECRET_IDLE_EXPIRY_MAX_SECONDS);
     SECRET_BINDING_HOST_PATTERN = /^(?=.{1,253}$)([a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?\.)+[a-z]([a-z0-9-]{0,61}[a-z0-9])?$/;
     SECRET_BINDING_HEADER_PATTERN = /^[!#$%&'*+.^_`|~0-9A-Za-z-]+$/;
     SECRET_BINDING_FORBIDDEN_HEADERS = /* @__PURE__ */ new Set([
@@ -17660,8 +17663,17 @@ var init_secrets = __esm({
       value: external_exports.string(),
       description: SecretDescriptionSchema.nullable().optional(),
       protected: external_exports.boolean().optional(),
-      binding: SecretBindingSchema.nullable().optional()
+      binding: SecretBindingSchema.nullable().optional(),
+      expiresAt: SecretExpiresAtSchema.nullable().optional(),
+      idleExpirySeconds: SecretIdleExpirySecondsSchema.nullable().optional()
     });
+    SecretExpiryUpdateRequestSchema = external_exports.object({
+      expiresAt: SecretExpiresAtSchema.nullable().optional(),
+      idleExpirySeconds: SecretIdleExpirySecondsSchema.nullable().optional()
+    }).refine(
+      (input) => input.expiresAt !== void 0 || input.idleExpirySeconds !== void 0,
+      { message: "Provide expiresAt and/or idleExpirySeconds" }
+    );
     SecretRotateRequestSchema = external_exports.object({
       value: external_exports.string()
     });
@@ -17678,7 +17690,15 @@ var init_secrets = __esm({
       createdAt: external_exports.string().datetime(),
       updatedAt: external_exports.string().datetime(),
       lastRotatedAt: external_exports.string().datetime().nullable(),
-      lastAccessedAt: external_exports.string().datetime().nullable()
+      lastAccessedAt: external_exports.string().datetime().nullable(),
+      // Like binding, defaulted for deploy skew: an older server that never sends
+      // expiry fields parses as a secret that never expires.
+      expiresAt: external_exports.string().datetime().nullable().default(null),
+      idleExpirySeconds: external_exports.number().int().nullable().default(null),
+      // Computed server-side: true when expiresAt has passed or the secret has
+      // been unused past idleExpirySeconds. Expired secrets resolve as absent
+      // everywhere but stay listed so operators can see and delete them.
+      expired: external_exports.boolean().default(false)
     });
     SecretSetResponseSchema = external_exports.object({
       secret: SecretMetadataSchema
@@ -17689,6 +17709,9 @@ var init_secrets = __esm({
     SecretDeleteResponseSchema = external_exports.object({
       secret: SecretMetadataSchema
     });
+    SecretExpiryUpdateResponseSchema = external_exports.object({
+      secret: SecretMetadataSchema
+    });
     SecretRevealResponseSchema = external_exports.object({
       secret: SecretMetadataSchema,
       value: external_exports.string()
@@ -26483,6 +26506,17 @@ triggers:
           ]
         }
       ],
+      "@auto/onboarding-quickstart": [
+        {
+          version: "1.0.0",
+          files: [
+            {
+              path: "fragments/onboarding-quickstart.yaml",
+              content: "systemPrompt:\n  append: |\n    ---\n    This project was created from the Auto quickstart template repo, so it\n    arrived with a working fleet instead of an empty `.auto/` directory:\n\n    - `.auto/agents/pr-review.yaml` \u2014 reviews every pull request.\n    - `.auto/agents/handoff.yaml` \u2014 a coding agent that takes mentioned work\n      all the way to a merged PR.\n    - `.auto/agents/self-improvement.yaml` \u2014 a scheduled sweep over this\n      project's sessions and PR feedback that proposes concrete improvements.\n    - `site/` \u2014 a small animated site that `.github/workflows/publish.yml`\n      republishes to here.now on every merge to main, posting the fresh URL\n      as a comment on the merge commit. Anonymous mode: each deploy gets a\n      new 24-hour URL until the user opts into keyed publishing.\n    - `.auto/fragments/site-handoff-trigger.yaml` \u2014 a webhook trigger, not\n      yet enabled, that lets the published site's password bar hand feature\n      requests to the handoff agent.\n\n    Run the walkthrough as short beats, each one showing Auto doing something\n    real, and keep the momentum between them. Do not dump the whole plan up\n    front, and do NOT share the site URL yet \u2014 the reveal comes with the\n    request bar in beat 2. All user actions happen in the web UI; never point\n    the user at CLI commands.\n\n    Beat 1 \u2014 tour. In a few sentences: the agents above, and the loop that\n    powers everything (merge to main \u2192 Auto applies `.auto/` \u2192 the site\n    republishes).\n\n    Beat 2 \u2014 set up the site request bar. Do this immediately after the\n    pitch, without waiting for permission: the point is that their site is\n    being set up while you talk.\n    1. Generate a three-word passphrase in your sandbox with exactly this\n       command:\n\n       curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0039/english.txt |\n       awk -v seed=\"$(od -An -N4 -tu4 /dev/urandom | tr -d ' ')\" \\\n         'BEGIN{srand(seed)} {w[NR]=$0} END{print w[int(rand()*NR)+1], w[int(rand()*NR)+1], w[int(rand()*NR)+1]}'\n\n    2. Create the `site-request-password` secret yourself with the\n       `auto.secrets.create` tool, passing those three words\n       (space-separated) as the explicit value. Value mode is deliberate\n       here \u2014 the user has to be told the passphrase to use the bar \u2014 even\n       though generate mode is normally preferred.\n    3. Reserve the webhook endpoint with the `auto.webhooks.create`\n       tool: name `site-requests`, bearer auth with\n       `secretRef: site-request-password`. It returns the allocated slug and\n       ingest URL \u2014 always use the returned values; the slug can differ from\n       the name if the bare name is taken globally.\n    4. Open the wiring PR right away: (a) add\n       `../fragments/site-handoff-trigger.yaml` to the imports of\n       `.auto/agents/handoff.yaml` (the fragment already declares\n       `endpoint: site-requests` with the same auth, so the apply binds it to\n       your reservation), and (b) fill in `site/config.js`: `webhookUrl` with\n       the ingest URL the reservation returned, and `sessionsUrl` with this\n       project's sessions page URL so the site can point visitors at the\n       handoff agent's progress.\n    5. Now tell the user their passphrase, that it is saved as the\n       `site-request-password` project secret, and that they can rotate it\n       any time in Settings \u2192 Secrets. Ask them to review and merge the PR.\n    6. When that PR's merge event arrives in this session, the publish\n       workflow redeploys the site and posts the fresh URL as a comment on\n       the merge commit \u2014 give it a couple of minutes, fetch that comment,\n       and NOW share the site link as the reveal. Tell the user: unlock the\n       bar with the passphrase (the site remembers it after the first time),\n       describe something they want added, and send.\n\n    Beat 3 \u2014 watch the loop close. Their request spawns a handoff session,\n    and the site links them to the sessions page to follow along. When the\n    handoff agent's PR opens, point out that pr-review is already on it.\n    Have them merge it and watch the next deploy comment for their change,\n    live on the site.\n\n    Beat 4 \u2014 a permanent URL (optional, mention once, don't push).\n    Anonymous deploy URLs rotate and expire after 24 hours. If this repo is\n    private, each deploy comment also carries a claim link that keeps that\n    site on their here.now account. For a stable URL either way: create an\n    API key at here.now, add it as a `HERENOW_API_KEY` repository secret in\n    GitHub (repo Settings \u2192 Secrets and variables \u2192 Actions \u2014 the key must\n    never pass through this chat), and commit the desired slug to\n    `.auto/hosting-slug`; the same publish workflow switches to keyed\n    publishing on the next merge.\n\n    Beat 5 \u2014 show off introspection. Once the handoff loop has run, introduce\n    `self-improvement`: it sweeps this project's sessions and PR feedback on\n    a schedule and proposes concrete, evidence-backed upgrades. Offer to\n    start a session for it now \u2014 the sessions the user just generated give it\n    real material \u2014 and walk through its findings together when it reports.\n\n    Then keep going: this factory is theirs to grow. Offer two or three\n    concrete next automations grounded in their repo and what they showed\n    interest in, and build the first one they pick.\n"
+            }
+          ]
+        }
+      ],
       "@auto/pr-review": [
         {
           version: "1.0.0",
@@ -26557,6 +26591,23 @@ triggers:
               content: 'model:\n  provider: anthropic\n  id: claude-opus-4-8\nlabels:\n  purpose: pr-review\nsession:\n  archiveAfterInactive:\n    seconds: 86400\nsystemPrompt: |\n  You are a code-analysis agent for Auto. Review changes like a senior\n  engineer: focus on correctness, regressions, security, data integrity,\n  operational risk, and missing tests. Keep output concise, concrete, and\n  grounded in the diff. Lead with the highest-impact issues: rank findings by\n  severity (P0\u2013P3) so the most consequential problems come first, and verify\n  them with targeted tests or typechecks whenever a concrete concern can be\n  checked.\n\n  Also enforce the repository idioms documented in AGENTS.md and\n  docs/idioms.md. Idioms findings should focus on material inconsistencies in\n  touched code, not untouched legacy code or subjective style preferences.\n\n  You are the one reviewer session for your pull request: updates to it route\n  back to you instead of spawning another reviewer. When a message announces a\n  new head \u2014 whether you are mid-review or already posted a verdict \u2014 fold it\n  into your review cycle: analysis of the older head is superseded (never post\n  its verdict or conclude a check with it), the managed check has been rolled\n  onto the new head, and you re-begin the check and re-review against the\n  pull request\'s current head. Keep exactly one current verdict per pull\n  request at all times.\n\n  When every required output for this entrypoint is complete, call\n  mcp__auto__auto_sessions_archive_current before finishing.\nidentity:\n  displayName: PR Review\n  username: pr-review\n  avatar:\n    asset: .auto/assets/pr-reviewer.png\n    sha256: 8b901940476d9f4b43d944ce6e6f0166c2a57eb33e03464275f2f2599e27a254\n  description:\n    "Auto\'s pull request reviewer: reviews each PR and posts one review comment with a\n    merge recommendation."\ndisplayTitle: "Review PR #{{github.pullRequest.number}}: {{github.pullRequest.title}}"\ninitialPrompt: |\n  Review GitHub pull request #{{github.pullRequest.number}} in {{github.repository.fullName}}.\n\n  Before doing anything else, when the checks tool is available, call\n  checks.begin with `{ "name": "pr-review" }`. This must happen before\n  inspecting PR metadata or the diff.\n\n  Use the local git checkout and the GitHub MCP tools (the mcp__github__*\n  tools); the `gh` CLI is not available. Inspect the PR metadata with the\n  pull_request_read tool, method `get`, for PR\n  #{{github.pullRequest.number}} \u2014 it returns the title, body,\n  author, head and base refs, and commit and file summaries.\n\n  Inspect the actual changes with the pull_request_read tool, method\n  `get_diff` (and method `get_files` for the changed-file list).\n\n  Read AGENTS.md and docs/idioms.md before forming your recommendation. Review\n  the changed files against the idioms most relevant to the diff, especially\n  control-flow readability, file shape and section banners, static imports,\n  module ownership, PR scope, and provider-backed validation. Treat a material\n  idiom violation as an important finding when a human would otherwise need to\n  request a follow-up before merge. Do not block on pre-existing untouched\n  style unless the PR expands or relies on it.\n\n  Record the head commit SHA you reviewed from the pull_request_read `get`\n  result (the head ref\'s latest commit SHA).\n\n  Determine whether you have reviewed this PR before. Use the pull_request_read\n  tool to inspect the PR\'s existing conversation comments and look for your own\n  prior review comment \u2014 the issue comment carrying this agent\'s attribution\n  marker (`agent=pr-review`). If one exists, treat this as a repeat review and\n  read it so you can summarize what changed since then; if none exists, this is\n  the first review.\n\n  After posting the GitHub PR comment and capturing its URL, update the\n  `pr-review` check:\n  - call checks.success when the PR comment\'s merge recommendation is\n    "thumbs-up", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  - call checks.failure when the PR comment\'s merge recommendation is\n    "thumbs-down", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  Include the reviewed commit SHA, the recommendation, the PR comment URL\n  when available, and the findings that gate the recommendation \u2014 the\n  unresolved P0/P1 findings, plus any unresolved P2 that drove a thumbs-down,\n  or "No blocking issues found." when nothing gates \u2014 in the check result.\n\n  The local checkout is a shallow checkout of the PR head only. Do not assume\n  origin/{{github.pullRequest.baseRef}} or origin/{{github.pullRequest.headRef}}\n  exists locally unless you explicitly fetch it first.\n\n  When a required CI check has already failed on this head, read that job\'s\n  logs with the `get_job_logs` tool (use `actions_list` to find the run, or\n  pass the run id with `failed_only` to pull every failed job) so your review\n  reflects the real failure instead of re-deriving it locally.\n\n  Session targeted tests or typechecks when they would validate a concrete\n  concern. The checkout may not have node_modules installed yet. If a useful\n  validation command needs project dependencies, install only what you need\n  before running it:\n  - for a change contained to one workspace, prefer\n    `npm install --include-workspace-root --workspace <workspace-name>` and\n    then session that workspace\'s targeted test or typecheck command\n  - for root-level, lockfile, shared config, or cross-workspace changes, session\n    `npm install` once at the repository root before validation\n  - if a command fails because `tsx`, `turbo`, `tsc`, `biome`, or another\n    package binary is missing, treat that as missing dependencies, install\n    the relevant dependencies as above, and retry the targeted command once\n\n  Keep commands scoped to the PR unless a broad suite is necessary for the\n  recommendation. Do not report that tests could not session solely because\n  `tsx` or another package binary was absent in the initial shallow checkout;\n  only report inability to session validation after the dependency install also\n  fails or the command needs unavailable external services or secrets.\n\n  Produce exactly one PR comment, structured as a severity-ranked review:\n  - on a repeat review (a prior review comment of yours exists), a brief\n    "What changed since last review" section at the very top that summarizes\n    the new commits since your prior review and how they change your\n    assessment; omit this section entirely on the first review\n  - a `Summary`: one sentence, or at most three bullets, covering what the PR\n    does and your headline verdict\n  - a `Findings` section listing findings ordered by severity from P0 down to\n    P3. Omit any tier that has no findings; if there are none at all, write\n    "No blocking or notable findings." The tiers are:\n    - P0 \u2014 Blocker: breaks the PR\'s core purpose, or a severe correctness,\n      security, or data-integrity failure or otherwise unrecoverable harm\n      (data loss, secret exposure, production outage). Must fix before merge.\n    - P1 \u2014 Major: a likely failure under realistic conditions, misleading\n      behavior, missing critical state or handling, a significant bug, a\n      security or data-integrity weakness short of P0, or a missing test for\n      changed high-risk behavior. Should fix before merge.\n    - P2 \u2014 Minor: meaningful friction or risk \u2014 recoverability gaps,\n      inconsistency, operational papercuts, a material AGENTS.md/docs/idioms.md\n      violation in touched code, or weaker-than-warranted test coverage. Fix\n      or justify.\n    - P3 \u2014 Nit: minor craft, consistency, or readability improvement. Optional.\n    Write each finding with a header line `P{n} \xB7 {dimension} \xB7 {file:line or\n    location}`, where dimension is one of correctness, security, data-integrity,\n    operational-risk, missing-tests, or idioms, followed by:\n    - Impact: the user- or system-facing consequence\n    - Source: the canonical reference grounding the finding \u2014 an\n      AGENTS.md/docs/idioms.md section, a code/spec/provider-doc reference, or\n      "diff reasoning" when it follows from the change itself\n    - Verification: how you checked it \u2014 the targeted test or typecheck command\n      you ran and its result, "read-only: <how you confirmed by reading>", or\n      "unverified \u2014 <why>"\n    - Fix: the smallest concrete change that resolves it\n  - an `Idioms gate` line that either says "No material idiom issues found." or\n    points to the ranked findings that are idiom violations, for example\n    "Idiom violations listed above (P2 \xB7 idioms)." Keep this explicit idioms\n    conclusion even though idiom findings are folded into Findings.\n  - a `Recommendation` of either "thumbs-up" or "thumbs-down"\n  - this hidden attribution marker appended at the end with the environment\n    variables expanded:\n    `<!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->`\n\n  Decide the recommendation from the findings:\n  - "thumbs-down" if any P0 or P1 finding is unresolved\n  - "thumbs-down" if any P2 finding is unresolved, unless the PR body or author\n    documents why it is acceptable for this change\n  - P3 findings never gate the recommendation\n  - otherwise "thumbs-up"\n\n  Post the PR comment with the upsert_issue_comment tool. Pass the repository\n  owner and name from {{github.repository.fullName}} as `owner` and `repo`, PR\n  number {{github.pullRequest.number}} as `issueNumber`, and the full review as\n  `body`. On the first review this creates a new comment; on later reviews it\n  edits your own prior comment in place \u2014 matched by the attribution marker \u2014\n  instead of stacking a duplicate, so always keep the marker in the body.\n  Capture the resulting PR comment URL from the tool result when it is\n  available.\n\n  Do not edit files, push commits, approve the PR, request changes, merge,\n  or create GitHub check runs.\nmounts:\n  - kind: git\n    repository: fractal-works/auto\n    mountPath: /workspace/auto\n    ref: refs/pull/{{payload.github.pullRequest.number}}/head\n    depth: 1\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/auto\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - upsert_issue_comment\n      # Read-only GitHub Actions tools so the review can read a failed CI\n      # job\'s logs and ground its recommendation in the real failure instead\n      # of re-deriving it locally. The mount already grants `actions: read`.\n      - actions_get\n      - actions_list\n      - get_job_logs\ntriggers:\n  # One reviewer session owns a PR across heads. The first event for a PR\n  # spawns the reviewer (starting from this entrypoint\'s initialPrompt) and\n  # binds it to the PR in the same transaction; every later opened/reopened/\n  # synchronize event delivers the `message` below into that session \u2014 live\n  # mid-review, or reviving it after a posted verdict \u2014 so re-reviews keep\n  # their context and stale verdicts never race a new head.\n  - name: pr-review\n    events:\n      - github.pull_request.opened\n      - github.pull_request.reopened\n      - github.pull_request.synchronize\n    connection: github-fractal-works\n    where:\n      $.github.repository.fullName: fractal-works/auto\n    message: |\n      Pull request #{{github.pullRequest.number}} in {{github.repository.fullName}} has a review-triggering\n      update (action: {{github.action}}; current head {{github.pullRequest.headSha}}).\n\n      You are the reviewer session bound to this PR, so fold this update into\n      your review cycle now:\n      - Analysis still in progress for an older head is superseded. Do not\n        post its verdict and do not conclude the managed check with it. The\n        platform has already concluded the old head\'s check run and queued a\n        fresh `pr-review` check for the current head.\n      - Call checks.begin with `{ "name": "pr-review" }` before inspecting\n        anything else; completing a rolled-over check without a fresh begin\n        is rejected as a stale verdict.\n      - The local checkout still holds the head this session started from.\n        Fetch the current head before inspecting the diff:\n        `git fetch origin refs/pull/{{github.pullRequest.number}}/head` and\n        check out the fetched commit.\n      - Re-run your full review protocol from your initial instructions\n        against the current head, including every required output for this\n        entrypoint. Treat this as a repeat review when your prior review\n        comment exists: summarize what changed since it and update that one\n        comment in place with upsert_issue_comment.\n      - Conclude the check with checks.success or checks.failure for the\n        current head\'s verdict. There must be exactly one current verdict\n        for this PR.\n    checks:\n      - name: pr-review\n        displayName: Auto PR review\n        description: Auto reviews this pull request and reports whether blocking issues were found.\n        instructions: |\n          Call checks.begin with { "name": "pr-review" } before doing\n          anything else. After posting the GitHub PR comment, call\n          checks.success with { "name": "pr-review", "summary": "...",\n          "text": "..." } only for a thumbs-up merge recommendation, and call\n          checks.failure with { "name": "pr-review", "summary": "...",\n          "text": "..." } for a thumbs-down merge recommendation. Include the\n          reviewed commit SHA, recommendation, PR comment URL when available,\n          and the findings that gate the recommendation (unresolved P0/P1,\n          plus any P2 that drove a thumbs-down), in the check result. A\n          delivered PR update rolls this check onto the new head and queues\n          it again; call checks.begin again before concluding that new cycle.\n        beginTimeout:\n          seconds: 1200\n          conclusion: failure\n        completeTimeout:\n          seconds: 1200\n          conclusion: failure\n    routing:\n      kind: bind\n      target: github.pull_request\n      onUnmatched: spawn\n'
             }
           ]
+        },
+        {
+          version: "1.4.0",
+          files: [
+            {
+              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"
+            },
+            {
+              path: "fragments/pr-review-slack.yaml",
+              content: 'imports:\n  - ./pr-review.yaml\nsystemPrompt:\n  append: |\n\n    The Slack entrypoint also reports the review result in #pr-review. Treat\n    that Slack reply as a required output for this entrypoint.\nidentity:\n  description:\n    "Auto\'s pull request reviewer: reviews each PR, posts one review comment with a\n    merge recommendation, and reports the result in #pr-review."\ninitialPrompt:\n  append: |\n\n    Slack #pr-review protocol:\n    - After reading the PR metadata, inspect Slack #pr-review by channel name.\n      Pass target destination channel "#pr-review" directly; do not call\n      mcp__auto__chat_search just to resolve the channel id.\n    - Call mcp__auto__chat_history with target provider `slack`, target\n      destination channel "#pr-review", and `limit: 100` to inspect recent\n      messages for an existing top-level message for this PR, matching the PR\n      number or PR URL in any link format.\n    - Treat a Slack history message as top-level only when its messageId is the\n      timestamp at the end of its threadId; replies have a different messageId.\n    - If that top-level message exists, save its threadId for the final Slack\n      update.\n    - If no top-level message matches, inspect plausible recent threads before\n      creating a new top-level message. Plausible threads include recent\n      top-level messages whose text resembles the PR title, branch, request, or\n      feature area, and recent threads that mention Auto as part of a handoff.\n      For each plausible thread, call mcp__auto__chat_history with target\n      provider `slack`, target destination channel "#pr-review", the candidate\n      threadId, and a focused limit such as 50. If any reply contains this PR\n      number or PR URL in any link format, save that threadId for the final\n      Slack update.\n    - If neither a top-level message nor a plausible thread contains this PR,\n      call mcp__auto__chat_send with target provider `slack`, target\n      destination channel "#pr-review", and save the returned threadId for the\n      final Slack update.\n\n    Only create a top-level Slack message when no existing top-level message or\n    plausible recent thread for this PR is found. Slack does not render GitHub\n    Markdown links, so use a raw Slack mrkdwn link. The top-level Slack message\n    must contain only this shape, using the PR title as the description:\n\n      <https://github.com/{{github.repository.fullName}}/pull/{{github.pullRequest.number}}|PR #{{github.pullRequest.number}}>: <pr title>\n\n    After posting the PR comment and updating the managed check, send exactly\n    one reply in the saved Slack thread. Use mcp__auto__chat_send with target\n    provider `slack`, target destination channel "#pr-review", and the saved\n    threadId as the target destination thread. Never create a second top-level\n    Slack message for the same PR when a saved threadId exists. Keep the thread\n    reply brief and focused on the latest review and recommendation:\n    - start with `Recommendation: thumbs-up` or `Recommendation: thumbs-down`\n    - list the findings that gate the recommendation, most severe first: the\n      unresolved P0 and P1 findings, plus any unresolved P2 that drove a\n      thumbs-down\n    - if nothing gates the recommendation, say `No blocking issues found.`\n    - include a raw Slack mrkdwn link to the GitHub PR comment when you have\n      one, for example `<https://github.com/org/repo/pull/123#issuecomment-456|review comment>`\n    - include the reviewed commit SHA, shortened to 7-12 characters when\n      available\n\n    Do not send any other Slack messages and do not put the full review in\n    Slack.\ntools:\n  chat:\n    kind: local\n    implementation: chat\n    auth:\n      kind: connection\n      provider: slack\n      connection: slack\n'
+            },
+            {
+              path: "fragments/pr-review.yaml",
+              content: '# 1.4.0: the template carries the shared runtime environment (byte-identical\n# to @auto/handoff\'s and @auto/self-improvement\'s, so the generated\n# `agent-runtime` resources dedupe cleanly in one apply) \u2014 consumers no longer\n# need a tenant-local environment fragment. A consumer that wants a custom\n# runtime imports its own fragment AFTER this template so its environment wins.\nimports:\n  - ./environments/agent-runtime.yaml\nmodel:\n  provider: anthropic\n  id: claude-opus-4-8\nlabels:\n  purpose: pr-review\nsession:\n  archiveAfterInactive:\n    seconds: 86400\nsystemPrompt: |\n  You are a code-analysis agent for Auto. Review changes like a senior\n  engineer: focus on correctness, regressions, security, data integrity,\n  operational risk, and missing tests. Keep output concise, concrete, and\n  grounded in the diff. Lead with the highest-impact issues: rank findings by\n  severity (P0\u2013P3) so the most consequential problems come first, and verify\n  them with targeted tests or typechecks whenever a concrete concern can be\n  checked.\n\n  Also enforce the repository idioms documented in AGENTS.md and\n  docs/idioms.md. Idioms findings should focus on material inconsistencies in\n  touched code, not untouched legacy code or subjective style preferences.\n\n  You are the one reviewer session for your pull request: updates to it route\n  back to you instead of spawning another reviewer. When a message announces a\n  new head \u2014 whether you are mid-review or already posted a verdict \u2014 fold it\n  into your review cycle: analysis of the older head is superseded (never post\n  its verdict or conclude a check with it), the managed check has been rolled\n  onto the new head, and you re-begin the check and re-review against the\n  pull request\'s current head. Keep exactly one current verdict per pull\n  request at all times.\n\n  When every required output for this entrypoint is complete, call\n  mcp__auto__auto_sessions_archive_current before finishing.\nidentity:\n  displayName: PR Review\n  username: pr-review\n  avatar:\n    asset: .auto/assets/pr-reviewer.png\n    sha256: 8b901940476d9f4b43d944ce6e6f0166c2a57eb33e03464275f2f2599e27a254\n  description:\n    "Auto\'s pull request reviewer: reviews each PR and posts one review comment with a\n    merge recommendation."\ndisplayTitle: "Review PR #{{github.pullRequest.number}}: {{github.pullRequest.title}}"\ninitialPrompt: |\n  Review GitHub pull request #{{github.pullRequest.number}} in {{github.repository.fullName}}.\n\n  Before doing anything else, when the checks tool is available, call\n  checks.begin with `{ "name": "pr-review" }`. This must happen before\n  inspecting PR metadata or the diff.\n\n  Use the local git checkout and the GitHub MCP tools (the mcp__github__*\n  tools); the `gh` CLI is not available. Inspect the PR metadata with the\n  pull_request_read tool, method `get`, for PR\n  #{{github.pullRequest.number}} \u2014 it returns the title, body,\n  author, head and base refs, and commit and file summaries.\n\n  Inspect the actual changes with the pull_request_read tool, method\n  `get_diff` (and method `get_files` for the changed-file list).\n\n  Read AGENTS.md and docs/idioms.md before forming your recommendation. Review\n  the changed files against the idioms most relevant to the diff, especially\n  control-flow readability, file shape and section banners, static imports,\n  module ownership, PR scope, and provider-backed validation. Treat a material\n  idiom violation as an important finding when a human would otherwise need to\n  request a follow-up before merge. Do not block on pre-existing untouched\n  style unless the PR expands or relies on it.\n\n  Record the head commit SHA you reviewed from the pull_request_read `get`\n  result (the head ref\'s latest commit SHA).\n\n  Determine whether you have reviewed this PR before. Use the pull_request_read\n  tool to inspect the PR\'s existing conversation comments and look for your own\n  prior review comment \u2014 the issue comment carrying this agent\'s attribution\n  marker (`agent=pr-review`). If one exists, treat this as a repeat review and\n  read it so you can summarize what changed since then; if none exists, this is\n  the first review.\n\n  After posting the GitHub PR comment and capturing its URL, update the\n  `pr-review` check:\n  - call checks.success when the PR comment\'s merge recommendation is\n    "thumbs-up", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  - call checks.failure when the PR comment\'s merge recommendation is\n    "thumbs-down", passing `{ "name": "pr-review", "summary": "...", "text": "..." }`\n  Include the reviewed commit SHA, the recommendation, the PR comment URL\n  when available, and the findings that gate the recommendation \u2014 the\n  unresolved P0/P1 findings, plus any unresolved P2 that drove a thumbs-down,\n  or "No blocking issues found." when nothing gates \u2014 in the check result.\n\n  The local checkout is a shallow checkout of the PR head only. Do not assume\n  origin/{{github.pullRequest.baseRef}} or origin/{{github.pullRequest.headRef}}\n  exists locally unless you explicitly fetch it first.\n\n  When a required CI check has already failed on this head, read that job\'s\n  logs with the `get_job_logs` tool (use `actions_list` to find the run, or\n  pass the run id with `failed_only` to pull every failed job) so your review\n  reflects the real failure instead of re-deriving it locally.\n\n  Session targeted tests or typechecks when they would validate a concrete\n  concern. The checkout may not have node_modules installed yet. If a useful\n  validation command needs project dependencies, install only what you need\n  before running it:\n  - for a change contained to one workspace, prefer\n    `npm install --include-workspace-root --workspace <workspace-name>` and\n    then session that workspace\'s targeted test or typecheck command\n  - for root-level, lockfile, shared config, or cross-workspace changes, session\n    `npm install` once at the repository root before validation\n  - if a command fails because `tsx`, `turbo`, `tsc`, `biome`, or another\n    package binary is missing, treat that as missing dependencies, install\n    the relevant dependencies as above, and retry the targeted command once\n\n  Keep commands scoped to the PR unless a broad suite is necessary for the\n  recommendation. Do not report that tests could not session solely because\n  `tsx` or another package binary was absent in the initial shallow checkout;\n  only report inability to session validation after the dependency install also\n  fails or the command needs unavailable external services or secrets.\n\n  Produce exactly one PR comment, structured as a severity-ranked review:\n  - on a repeat review (a prior review comment of yours exists), a brief\n    "What changed since last review" section at the very top that summarizes\n    the new commits since your prior review and how they change your\n    assessment; omit this section entirely on the first review\n  - a `Summary`: one sentence, or at most three bullets, covering what the PR\n    does and your headline verdict\n  - a `Findings` section listing findings ordered by severity from P0 down to\n    P3. Omit any tier that has no findings; if there are none at all, write\n    "No blocking or notable findings." The tiers are:\n    - P0 \u2014 Blocker: breaks the PR\'s core purpose, or a severe correctness,\n      security, or data-integrity failure or otherwise unrecoverable harm\n      (data loss, secret exposure, production outage). Must fix before merge.\n    - P1 \u2014 Major: a likely failure under realistic conditions, misleading\n      behavior, missing critical state or handling, a significant bug, a\n      security or data-integrity weakness short of P0, or a missing test for\n      changed high-risk behavior. Should fix before merge.\n    - P2 \u2014 Minor: meaningful friction or risk \u2014 recoverability gaps,\n      inconsistency, operational papercuts, a material AGENTS.md/docs/idioms.md\n      violation in touched code, or weaker-than-warranted test coverage. Fix\n      or justify.\n    - P3 \u2014 Nit: minor craft, consistency, or readability improvement. Optional.\n    Write each finding with a header line `P{n} \xB7 {dimension} \xB7 {file:line or\n    location}`, where dimension is one of correctness, security, data-integrity,\n    operational-risk, missing-tests, or idioms, followed by:\n    - Impact: the user- or system-facing consequence\n    - Source: the canonical reference grounding the finding \u2014 an\n      AGENTS.md/docs/idioms.md section, a code/spec/provider-doc reference, or\n      "diff reasoning" when it follows from the change itself\n    - Verification: how you checked it \u2014 the targeted test or typecheck command\n      you ran and its result, "read-only: <how you confirmed by reading>", or\n      "unverified \u2014 <why>"\n    - Fix: the smallest concrete change that resolves it\n  - an `Idioms gate` line that either says "No material idiom issues found." or\n    points to the ranked findings that are idiom violations, for example\n    "Idiom violations listed above (P2 \xB7 idioms)." Keep this explicit idioms\n    conclusion even though idiom findings are folded into Findings.\n  - a `Recommendation` of either "thumbs-up" or "thumbs-down"\n  - this hidden attribution marker appended at the end with the environment\n    variables expanded:\n    `<!-- auto:v=1 session_id=$AUTO_SESSION_ID agent=$AUTO_AGENT_NAME -->`\n\n  Decide the recommendation from the findings:\n  - "thumbs-down" if any P0 or P1 finding is unresolved\n  - "thumbs-down" if any P2 finding is unresolved, unless the PR body or author\n    documents why it is acceptable for this change\n  - P3 findings never gate the recommendation\n  - otherwise "thumbs-up"\n\n  Post the PR comment with the upsert_issue_comment tool. Pass the repository\n  owner and name from {{github.repository.fullName}} as `owner` and `repo`, PR\n  number {{github.pullRequest.number}} as `issueNumber`, and the full review as\n  `body`. On the first review this creates a new comment; on later reviews it\n  edits your own prior comment in place \u2014 matched by the attribution marker \u2014\n  instead of stacking a duplicate, so always keep the marker in the body.\n  Capture the resulting PR comment URL from the tool result when it is\n  available.\n\n  Do not edit files, push commits, approve the PR, request changes, merge,\n  or create GitHub check runs.\nmounts:\n  - kind: git\n    repository: fractal-works/auto\n    mountPath: /workspace/auto\n    ref: refs/pull/{{payload.github.pullRequest.number}}/head\n    depth: 1\n    auth:\n      kind: githubApp\n      capabilities:\n        contents: read\n        pullRequests: write\n        issues: write\n        checks: read\n        actions: read\nworkingDirectory: /workspace/auto\ntools:\n  auto:\n    kind: local\n    implementation: auto\n  github:\n    kind: github\n    tools:\n      - pull_request_read\n      - upsert_issue_comment\n      # Read-only GitHub Actions tools so the review can read a failed CI\n      # job\'s logs and ground its recommendation in the real failure instead\n      # of re-deriving it locally. The mount already grants `actions: read`.\n      - actions_get\n      - actions_list\n      - get_job_logs\ntriggers:\n  # One reviewer session owns a PR across heads. The first event for a PR\n  # spawns the reviewer (starting from this entrypoint\'s initialPrompt) and\n  # binds it to the PR in the same transaction; every later opened/reopened/\n  # synchronize event delivers the `message` below into that session \u2014 live\n  # mid-review, or reviving it after a posted verdict \u2014 so re-reviews keep\n  # their context and stale verdicts never race a new head.\n  - name: pr-review\n    events:\n      - github.pull_request.opened\n      - github.pull_request.reopened\n      - github.pull_request.synchronize\n    connection: github-fractal-works\n    where:\n      $.github.repository.fullName: fractal-works/auto\n    message: |\n      Pull request #{{github.pullRequest.number}} in {{github.repository.fullName}} has a review-triggering\n      update (action: {{github.action}}; current head {{github.pullRequest.headSha}}).\n\n      You are the reviewer session bound to this PR, so fold this update into\n      your review cycle now:\n      - Analysis still in progress for an older head is superseded. Do not\n        post its verdict and do not conclude the managed check with it. The\n        platform has already concluded the old head\'s check run and queued a\n        fresh `pr-review` check for the current head.\n      - Call checks.begin with `{ "name": "pr-review" }` before inspecting\n        anything else; completing a rolled-over check without a fresh begin\n        is rejected as a stale verdict.\n      - The local checkout still holds the head this session started from.\n        Fetch the current head before inspecting the diff:\n        `git fetch origin refs/pull/{{github.pullRequest.number}}/head` and\n        check out the fetched commit.\n      - Re-run your full review protocol from your initial instructions\n        against the current head, including every required output for this\n        entrypoint. Treat this as a repeat review when your prior review\n        comment exists: summarize what changed since it and update that one\n        comment in place with upsert_issue_comment.\n      - Conclude the check with checks.success or checks.failure for the\n        current head\'s verdict. There must be exactly one current verdict\n        for this PR.\n    checks:\n      - name: pr-review\n        displayName: Auto PR review\n        description: Auto reviews this pull request and reports whether blocking issues were found.\n        instructions: |\n          Call checks.begin with { "name": "pr-review" } before doing\n          anything else. After posting the GitHub PR comment, call\n          checks.success with { "name": "pr-review", "summary": "...",\n          "text": "..." } only for a thumbs-up merge recommendation, and call\n          checks.failure with { "name": "pr-review", "summary": "...",\n          "text": "..." } for a thumbs-down merge recommendation. Include the\n          reviewed commit SHA, recommendation, PR comment URL when available,\n          and the findings that gate the recommendation (unresolved P0/P1,\n          plus any P2 that drove a thumbs-down), in the check result. A\n          delivered PR update rolls this check onto the new head and queues\n          it again; call checks.begin again before concluding that new cycle.\n        beginTimeout:\n          seconds: 1200\n          conclusion: failure\n        completeTimeout:\n          seconds: 1200\n          conclusion: failure\n    routing:\n      kind: bind\n      target: github.pull_request\n      onUnmatched: spawn\n'
+            }
+          ]
         }
       ],
       "@auto/research-loop": [
@@ -28552,6 +28603,7 @@ var init_hardcoded = __esm({
       "@auto/issue-triage": "Linear issue triage plus an implementation coder: label-driven triage handoffs that become focused PRs.",
       "@auto/lead-engine": "An inbound-lead researcher that scores fit and drafts outreach for human approval; -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).",
       "@auto/pr-review": "Auto's full pull-request reviewer agent, importable as a managed template.",
       "@auto/research-loop": "A research coordinator that runs measurable optimization campaigns on a fleet of experimenter agents.",
       "@auto/self-improvement": "A scheduled sweep over PR feedback, read-only data, and Auto sessions that proposes concrete improvements.",
@@ -30539,6 +30591,25 @@ function createApiClient(input) {
       }
       return SecretSetResponseSchema.parse(await response.json());
     },
+    async updateSecretExpiry(name, request, options = {}) {
+      const organization = await activeOrganization();
+      const path2 = `${secretPath(organization.organizationId, options.projectId, name)}/expiry`;
+      const response = await authenticatedFetch(
+        apiUrl(path2, options.apiBaseUrl),
+        {
+          method: "PATCH",
+          headers: {
+            "content-type": "application/json"
+          },
+          body: JSON.stringify(request)
+        },
+        options.apiBaseUrl
+      );
+      if (!response.ok) {
+        throw new Error(await responseErrorMessage(response));
+      }
+      return SecretExpiryUpdateResponseSchema.parse(await response.json());
+    },
     async revealSecret(name, options = {}) {
       const organization = await activeOrganization();
       const path2 = `${secretPath(organization.organizationId, options.projectId, name)}/value`;
@@ -31605,7 +31676,7 @@ var init_package = __esm({
   "package.json"() {
     package_default = {
       name: "@autohq/cli",
-      version: "0.1.365",
+      version: "0.1.367",
       license: "SEE LICENSE IN README.md",
       publishConfig: {
         access: "public"
@@ -32776,7 +32847,11 @@ function fileBackedStringField() {
   return {
     target: "spec",
     read: (value, context) => resolveFileBackedString2(value, context),
-    merge: (base, override) => resolveAppendDirective(base, override)
+    merge: (base, override) => resolveAppendDirective(base, override),
+    compile: (value) => ({
+      resources: [],
+      value: rejectUnresolvedAppendDirective(value)
+    })
   };
 }
 function rejectDirectiveObject(value, input) {
@@ -32848,14 +32923,42 @@ function readAppendDirectiveMarker(value, input) {
 function resolveAppendDirective(base, override) {
   const directive = appendDirectiveFromMarker(override);
   if (!directive) {
+    const droppedPending = appendDirectiveFromMarker(base);
+    if (droppedPending) {
+      throw new Error(
+        `Invalid agent authoring file ${droppedPending.path}: ${droppedPending.field} append directive was merged before any base value; import the base document before its append overlay`
+      );
+    }
     return mergeValues3(base, override);
   }
-  if (typeof base !== "string") {
-    throw new Error(
-      `Invalid agent authoring file ${directive.path}: ${directive.field} append directive has no imported ${directive.field} to append to`
-    );
+  if (typeof base === "string") {
+    return base + directive.text;
+  }
+  const pendingBase = appendDirectiveFromMarker(base);
+  if (pendingBase) {
+    return {
+      [APPEND_DIRECTIVE_MARKER_KEY]: {
+        text: pendingBase.text + directive.text,
+        path: directive.path,
+        field: directive.field
+      }
+    };
+  }
+  if (base === void 0) {
+    return override;
   }
-  return base + directive.text;
+  throw new Error(
+    `Invalid agent authoring file ${directive.path}: ${directive.field} append directive has no imported ${directive.field} to append to`
+  );
+}
+function rejectUnresolvedAppendDirective(value) {
+  const directive = appendDirectiveFromMarker(value);
+  if (!directive) {
+    return value;
+  }
+  throw new Error(
+    `Invalid agent authoring file ${directive.path}: ${directive.field} append directive has no imported ${directive.field} to append to`
+  );
 }
 function appendDirectiveFromMarker(value) {
   if (!isRecord2(value)) {
@@ -50047,6 +50150,7 @@ function memberLine2(member, style) {
 }
 
 // src/commands/secrets/actions.ts
+init_src();
 async function setSecret(input) {
   const value = await secretValue({
     options: input.commandOptions,
@@ -50059,6 +50163,7 @@ async function setSecret(input) {
       value,
       ...input.commandOptions.description === void 0 ? {} : { description: input.commandOptions.description },
       ...resolveProtectedFlag(input.commandOptions),
+      ...resolveExpiryFields(input.commandOptions),
       ...resolveBindingFlags(input.commandOptions)
     },
     {
@@ -50084,6 +50189,17 @@ async function rotateSecret(input) {
   );
   writeRotateResponse(response, input);
 }
+async function updateSecretExpiry(input) {
+  const fields = resolveExpiryFields(input.commandOptions);
+  if (fields.expiresAt === void 0 && fields.idleExpirySeconds === void 0) {
+    throw new Error("Provide --expires-at and/or --idle-expiry.");
+  }
+  const response = await input.client.updateSecretExpiry(input.name, fields, {
+    projectId: await secretProjectId(input),
+    apiBaseUrl: input.commandOptions.apiBaseUrl
+  });
+  writeExpiryResponse(response, input);
+}
 async function revealSecret(input) {
   const response = await input.client.revealSecret(input.name, {
     projectId: await secretProjectId(input),
@@ -50106,9 +50222,23 @@ async function listSecrets(input) {
   }
   for (const secret of response.secrets) {
     const flags = secret.protected ? "protected" : "revealable";
-    input.context.writeOutput(
-      `${secret.name}  ${scopeLabel(secret.projectId)}  ${flags}  updated ${secret.updatedAt}`
-    );
+    const parts = [
+      secret.name,
+      scopeLabel(secret.projectId),
+      flags,
+      `updated ${secret.updatedAt}`
+    ];
+    if (secret.expired) {
+      parts.push("expired");
+    } else {
+      if (secret.expiresAt !== null) {
+        parts.push(`expires ${secret.expiresAt}`);
+      }
+      if (secret.idleExpirySeconds !== null) {
+        parts.push(`idle-expiry ${secret.idleExpirySeconds}s`);
+      }
+    }
+    input.context.writeOutput(parts.join("  "));
   }
 }
 function resolveProtectedFlag(options) {
@@ -50123,6 +50253,43 @@ function resolveProtectedFlag(options) {
   }
   return {};
 }
+function parseExpiresAt(input) {
+  if (input === "never") {
+    return null;
+  }
+  const parsed = new Date(input);
+  if (Number.isNaN(parsed.getTime())) {
+    throw new Error(
+      `Invalid --expires-at value "${input}". Use an ISO 8601 timestamp or "never".`
+    );
+  }
+  return parsed.toISOString();
+}
+function parseIdleExpiry(input) {
+  if (input === "never") {
+    return null;
+  }
+  const match = /^(\d+)(s|m|h|d)?$/.exec(input);
+  if (!match) {
+    throw new Error(
+      `Invalid --idle-expiry value "${input}". Use seconds or a duration like 30d, 12h, 90m, 3600s, or "never".`
+    );
+  }
+  const unitSeconds = { s: 1, m: 60, h: 3600, d: 86400 }[match[2] ?? "s"] ?? 1;
+  const seconds = Number(match[1]) * unitSeconds;
+  if (seconds < 1 || seconds > SECRET_IDLE_EXPIRY_MAX_SECONDS) {
+    throw new Error(
+      `--idle-expiry must be between 1 second and ${SECRET_IDLE_EXPIRY_MAX_SECONDS} seconds (10 years).`
+    );
+  }
+  return seconds;
+}
+function resolveExpiryFields(options) {
+  return {
+    ...options.expiresAt === void 0 ? {} : { expiresAt: parseExpiresAt(options.expiresAt) },
+    ...options.idleExpiry === void 0 ? {} : { idleExpirySeconds: parseIdleExpiry(options.idleExpiry) }
+  };
+}
 function resolveBindingFlags(options) {
   const hasBindingFlags = (options.bindHost?.length ?? 0) > 0 || options.bindHeader !== void 0 || options.bindFormat !== void 0;
   if (options.unbind) {
@@ -50228,6 +50395,16 @@ function writeRotateResponse(response, input) {
     `secret ${response.secret.name} rotated scope=${scopeLabel(response.secret.projectId)}`
   );
 }
+function writeExpiryResponse(response, input) {
+  if (input.commandOptions.json) {
+    input.context.writeOutput(JSON.stringify(response));
+    return;
+  }
+  const idle = response.secret.idleExpirySeconds === null ? "never" : `${response.secret.idleExpirySeconds}s`;
+  input.context.writeOutput(
+    `secret ${response.secret.name} expiry updated scope=${scopeLabel(response.secret.projectId)} expires=${response.secret.expiresAt ?? "never"} idle=${idle}`
+  );
+}
 function writeRevealResponse(response, input) {
   if (input.commandOptions.json) {
     input.context.writeOutput(JSON.stringify(response));
@@ -50315,7 +50492,13 @@ function registerSecretCommands(program, context) {
   ).option("--unbind", "clear an existing destination binding").option("--protected", "mark write-only: refuse plaintext reveal (default)").option(
     "--unprotected",
     "allow scope-gated plaintext reveal of this secret"
-  ).option("--raw", "allow empty values and preserve stdin exactly").option("--json", "print the updated secret metadata as JSON").option("--api-url <url>", "Auto API base URL").option("--api-base-url <url>", "Auto API base URL").action(async (name, commandOptions) => {
+  ).option("--raw", "allow empty values and preserve stdin exactly").option(
+    "--expires-at <timestamp>",
+    'absolute expiry as an ISO 8601 timestamp, or "never" to clear'
+  ).option(
+    "--idle-expiry <duration>",
+    'expire after this long unused (seconds or 30d/12h/90m/3600s), or "never" to clear'
+  ).option("--json", "print the updated secret metadata as JSON").option("--api-url <url>", "Auto API base URL").option("--api-base-url <url>", "Auto API base URL").action(async (name, commandOptions) => {
     await setSecret({
       client: createContextApiClient(context),
       commandOptions: withApiBaseUrl(context, commandOptions),
@@ -50334,6 +50517,20 @@ function registerSecretCommands(program, context) {
       name
     });
   });
+  secrets.command("expiry").description("Update a secret's expiry without changing its value.").argument("<name>", "secret name").option("--project <project>", "project id; defaults to organization scope").option(
+    "--expires-at <timestamp>",
+    'absolute expiry as an ISO 8601 timestamp, or "never" to clear'
+  ).option(
+    "--idle-expiry <duration>",
+    'expire after this long unused (seconds or 30d/12h/90m/3600s), or "never" to clear'
+  ).option("--json", "print the updated secret metadata as JSON").option("--api-url <url>", "Auto API base URL").option("--api-base-url <url>", "Auto API base URL").action(async (name, commandOptions) => {
+    await updateSecretExpiry({
+      client: createContextApiClient(context),
+      commandOptions: withApiBaseUrl(context, commandOptions),
+      context,
+      name
+    });
+  });
   secrets.command("reveal").description(
     "Print the decrypted value of a non-protected secret (audited)."
   ).argument("<name>", "secret name").option("--project <project>", "project id; defaults to organization scope").option("--json", "print the secret value and metadata as JSON").option("--api-url <url>", "Auto API base URL").option("--api-base-url <url>", "Auto API base URL").action(async (name, commandOptions) => {

package/package.json

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