@plainconceptsplatform/workflows 1.9.0 → 1.10.0

package/loops/workflows/agent-merge-gate.md

@@ -25,7 +25,9 @@ env:
   RISK_INDICATORS: "Any diff touching authentication, authorization or session handling. Any change to a calculation or pricing engine, or to code handling money. Any database migration, or a change to an entity or schema. Any change to an audit or event log, or anything that could break its continuity. Any change to a public API contract or a shared library other repositories consume."
   # Paths a bot may change but never merge on its own: an extended regular expression matched
   # against every changed path in the pull request. A match holds the merge for a human; it does
-  # not stop the agent repairing failed CI on the same files.
+  # not stop the agent repairing failed CI on the same files. A pull request a person with write
+  # access opened is not held for them: that person could push the same change to the branch, and
+  # GitHub does not let them approve their own pull request, so the hold only stranded it.
   #
   # Only the automation itself. This list used to hold every dependency manifest, lockfile and
   # dotted directory as well, and with a size threshold and an owner list as wide it parked most
@@ -188,6 +190,7 @@ jobs:
       closes: ${{ steps.subject.outputs.closes }}
       conclusion: ${{ steps.subject.outputs.conclusion }}
       run-id: ${{ steps.subject.outputs.run-id }}
+      human_author: ${{ steps.subject.outputs.human-author }}
       review_blocked: ${{ steps.review.outputs.review_blocked }}
       pr_base: ${{ steps.stack.outputs.pr_base }}
       stack_root: ${{ steps.stack.outputs.stack_root }}
@@ -311,7 +314,7 @@ jobs:
         with:
           token: ${{ github.token }}
           pr-number: ${{ needs.subject.outputs.pr }}
-          protected-paths: ${{ env.PROTECTED_PATHS }}
+          protected-paths: ${{ needs.subject.outputs.human_author != 'true' && env.PROTECTED_PATHS || '' }}
           owner-paths: ${{ env.OWNER_PATHS }}
           sensitive-paths: ${{ env.SENSITIVE_PATHS }}
           high-files: ${{ env.BLAST_HIGH_FILES }}
@@ -426,13 +429,13 @@ jobs:
           body: |
             ${{ env.GATE_MARKER }}
             PR #${{ needs.subject.outputs.pr }} changes protected files and cannot be auto-merged.
-            The `review` and `owner-review` labels are set: the person who owns these files
-            decides, and merges.
+            The `review` and `owner-review` labels are set. Anyone with write access can review it:
+            approving the pull request merges it.
 
             Protected files:
             ${{ needs.protected_changes.outputs.files }}
 
-            Required owners: `${{ needs.protected_changes.outputs.required_owners || 'none configured' }}`
+            Asked to review: `${{ needs.protected_changes.outputs.required_owners || 'nobody named in CODEOWNERS' }}`
 
             **Verdict:** owner-review
       - name: Replay the verification plan for the owner
@@ -613,7 +616,7 @@ jobs:
               && format('| Accepted unattended | {0} |', needs.validate_output.outputs.flags)
               || '' }}
             ${{ needs.validate_output.outputs.outcome == 'owner-review'
-              && format('| Required owners | `{0}` |', needs.protected_changes.outputs.required_owners != '' && needs.protected_changes.outputs.required_owners || 'none configured, see the matched paths above')
+              && format('| Asked to review | `{0}` |', needs.protected_changes.outputs.required_owners != '' && needs.protected_changes.outputs.required_owners || 'nobody named in CODEOWNERS, see the matched paths above')
               || '' }}
 
             Why this blast radius:
@@ -622,7 +625,8 @@ jobs:
             ```
 
             ${{ needs.subject.outputs.issue != '' && format('Findings and verification on the linked issue: #{0}.', needs.subject.outputs.issue) || 'Findings and verification are in the review comment above.' }} [View this workflow run](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})
-            ${{ env.EVIDENCE_BEFORE_REVIEW == 'true' && contains(fromJson('["human-review","owner-review"]'), needs.validate_output.outputs.outcome) && 'Screenshots of this head follow in their own comment if it carries a verification plan. Approving the pull request merges it.' || '' }}
+            ${{ env.EVIDENCE_BEFORE_REVIEW == 'true' && contains(fromJson('["human-review","owner-review"]'), needs.validate_output.outputs.outcome) && 'Screenshots of this head follow in their own comment if it carries a verification plan.' || '' }}
+            ${{ contains(fromJson('["human-review","owner-review"]'), needs.validate_output.outputs.outcome) && 'Anyone with write access can review it: approving the pull request merges it.' || '' }}
       - name: Read the head to land
         id: landing_head
         if: needs.validate_output.outputs.outcome == 'auto-merge' && (needs.subject.outputs.stack_root != 'true' || needs.subject.outputs.root_complete == 'true')

package/loops/workflows/agent-refine.md

@@ -58,6 +58,17 @@ env:
   DRAFT_MARKER: "<!-- agent-refine-draft -->"
   INITIAL_MODE: first
   RESPONSE_MODE: rerefine
+  # The pass the router starts when nobody answered the questions in time, or the author accepted
+  # them with a thumbs-up: every proposed answer is taken as given. See REFINE_ANSWER_TIMEOUT_HOURS
+  # in work-router.yml.
+  ASSUME_MODE: assume
+  ASSUMED_LABEL: assumed
+  # The sentence that opens the batched questions, and the two ways a question ends. The validator
+  # reads the first to decide the outcome; the router reads the other two to know whether the
+  # questions can be taken as answered.
+  QUESTIONS_LINE: "I have some questions about this issue"
+  PROPOSED_TAG: "**Proposed:**"
+  DECISION_TAG: "**Your decision needed:**"
   MAX_SELF_QUESTIONS: "5"
   TRIVIAL_MARKER: "<!-- complexity: trivial -->"
   ESTIMATE_MARKER_PREFIX: "<!-- estimate: "
@@ -76,8 +87,9 @@ env:
   GIT_COMMITTER_NAME: "github-actions[bot]"
   GIT_COMMITTER_EMAIL: "github-actions[bot]@users.noreply.github.com"
 description: |
-  Refines an issue into a user story, on a first pass or after the author has answered the
-  bot's questions. Replaces .loops/recipes/refine-loop.yaml.
+  Refines an issue into a user story, on a first pass, after the author has answered the
+  bot's questions, or once the bot's proposed answers stand because nobody answered in time.
+  Replaces .loops/recipes/refine-loop.yaml.
 
   The refined story is wrapped in the repository's own issue template when one matches.
   When questions remain, the worker leaves that template-wrapped temporal draft on the
@@ -92,7 +104,7 @@ description: |
   still parks an issue for a person.
 
   Router-only worker: triggered exclusively via workflow_call from work-router.yml.
-  Contract inputs: issue-number, mode(first|rerefine).
+  Contract inputs: issue-number, mode(first|rerefine|assume).
 
 name: "Agent: Refine Issue"
 
@@ -114,7 +126,7 @@ on:
         required: true
         type: string
       mode:
-        description: Refinement pass mode (first or rerefine).
+        description: Refinement pass mode (first, rerefine or assume).
         required: false
         type: string
         default: first
@@ -177,9 +189,10 @@ jobs:
           labels=$(gh issue view "$ISSUE_NUMBER" --repo "$GITHUB_REPOSITORY" --json labels \
             --jq '[.labels[].name]')
           if jq -e 'index("review")' >/dev/null <<<"$labels"; then
-            if [ "$MODE" = "rerefine" ]; then
+            if [ "$MODE" = "rerefine" ] || [ "$MODE" = "assume" ]; then
               # A rerefine is triggered by a human comment on an issue the bot parked for
-              # review. The comment is the review: clear the label and proceed.
+              # review. The comment is the review: clear the label and proceed. An assume pass
+              # is the router's answer to the same park once the deadline passed.
               gh issue edit "$ISSUE_NUMBER" --remove-label "review" 2>/dev/null ||
                 echo "::notice::review label already gone on #$ISSUE_NUMBER"
               echo "eligible=true" >> "$GITHUB_OUTPUT"
@@ -323,6 +336,8 @@ jobs:
           token: ${{ github.token }}
           issue-number: ${{ inputs.issue-number }}
           labels: ${{ env.WORKING_LABEL }}
+      # `assumed` says the router already spent its assume pass on this issue. A refinement from
+      # scratch earns a new one.
       - name: Clear the human-needed flag
         uses: ./.github/actions/remove-issue-labels
         with:
@@ -331,6 +346,7 @@ jobs:
           labels: |-
             ${{ env.REVIEW_LABEL }}
             ${{ env.STALLED_LABEL }}
+            ${{ inputs.mode == env.INITIAL_MODE && env.ASSUMED_LABEL || '' }}
   validate_output:
     needs: [activation, agent, safe_outputs]
     if: >
@@ -362,6 +378,7 @@ jobs:
           draft-marker: ${{ env.DRAFT_MARKER }}
           comment-prefix: ${{ env.SAFE_OUTPUT_COMMENT_PREFIX }}
           issue-number: ${{ inputs.issue-number }}
+          questions-line: ${{ env.QUESTIONS_LINE }}
   conclude:
     needs: [activation, agent, safe_outputs, validate_output]
     # `always()` is load-bearing: without it GitHub prepends `success()`, which returns false
@@ -418,6 +435,7 @@ jobs:
           labels: |-
             ${{ env.REFINED_LABEL }}
             ${{ env.IMPLEMENT_LABEL }}
+            ${{ inputs.mode == env.ASSUME_MODE && env.ASSUMED_LABEL || '' }}
       - name: Clear complete refinement labels
         if: needs.validate_output.outputs.outcome == 'complete'
         uses: ./.github/actions/remove-issue-labels
@@ -645,13 +663,18 @@ jobs:
             gh issue edit "$child" --repo "$REPO" --add-label "$IMPLEMENT_LABEL" >/dev/null
             echo "#$child handed to implement"
           done
+      # An assume pass that still asks leaves `assumed` beside `review`, which the router reads as
+      # "already assumed once": the questions then wait for a person instead of being assumed
+      # again every working day.
       - name: Flag questions for review
         if: needs.validate_output.outputs.outcome == 'questions'
         uses: ./.github/actions/add-issue-labels
         with:
           token: ${{ steps.app-token.outputs.token }}
           issue-number: ${{ inputs.issue-number }}
-          labels: ${{ env.REVIEW_LABEL }}
+          labels: |-
+            ${{ env.REVIEW_LABEL }}
+            ${{ inputs.mode == env.ASSUME_MODE && env.ASSUMED_LABEL || '' }}
       - name: Release questions for the author
         if: needs.validate_output.outputs.outcome == 'questions'
         uses: ./.github/actions/remove-issue-labels
@@ -903,7 +926,15 @@ timeout-minutes: 90
    - On a `${{ env.RESPONSE_MODE }}` pass, incorporate only the supplied answers from the issue author or an
      assignee. Do not use answers from other commenters. The body may already hold the
      temporal draft from the earlier pass: reuse what still holds, and resolve its pending
-     marks with the author's answers.
+     marks with the author's answers. A question the author left unanswered keeps the answer
+     you proposed for it. A reply that accepts your proposals as a whole ("ok", "yes", "go
+     ahead", in any language) answers every question with its proposal.
+   - On a `${{ env.ASSUME_MODE }}` pass, nobody answered your last batch of questions in time, or the
+     author accepted it with a thumbs-up. Take each question's `${{ env.PROPOSED_TAG }}` answer as
+     given, except where the author or an assignee did answer in a comment: their answer wins.
+     Do not ask again: write the finished story. Add a section titled `Assumed without a reply`
+     at the end of the body, before any related links, listing each question in a short line
+     with the answer you took, so whoever reviews the pull request sees what nobody confirmed.
 
 3. **Explore and write the story.** Split the issue into work units first. If the issue body is
    a bullet list of distinct tasks, treat each bullet as its own work unit. Otherwise treat the
@@ -915,6 +946,14 @@ timeout-minutes: 90
    issue. At most ${{ env.MAX_SELF_QUESTIONS }} self-asked questions per work unit, and stop
    sooner once more exploring stops changing your understanding.
 
+   Answer your own questions from the codebase and the docs. Set one aside for the author when
+   it is a business or product decision the code cannot settle: which of two reasonable
+   behaviours the users want, who sees or may do something, a threshold or a limit, which figure
+   a calculation uses, what a message says to a customer. Choosing one of those yourself because
+   the code would allow either is not answering it; it is the question. A wrong guess costs a
+   pull request, a question costs a reply, and the author can accept every proposal with a
+   thumbs-up.
+
    Then classify the change complexity. A change is **trivial** only if every one of these
    holds: ${{ env.TRIVIAL_CRITERIA }}
 
@@ -1044,14 +1083,23 @@ timeout-minutes: 90
     The comment carries:
    1. `${{ env.REFINE_MARKER }}`
    2. `${{ env.SAFE_OUTPUT_COMMENT_PREFIX }}`
-   3. `I have some questions about this issue. Please reply in one comment and I'll process your answers.`
-   4. Every set-aside question, gathered from all work units, immediately below it, each answerable in a sentence.
+   3. `${{ env.QUESTIONS_LINE }}. Each one carries the answer I would take. Reply in one comment to change any of them, or react with 👍 to accept them all.`
+   4. Every set-aside question, gathered from all work units, as a numbered list, each answerable in a sentence.
+   5. A last line saying that if nobody replies the proposed answers stand and refinement carries on, except for any question that needs a decision.
+
+   Every question ends in one of two ways, on its own line under the question:
+
+   - `${{ env.PROPOSED_TAG }} <the answer you would take> -- <why, in one short clause: the convention, the existing behaviour or the issue text it follows>`. This is the usual case: you can name a sensible answer, and getting it wrong costs a change, not a loss.
+   - `${{ env.DECISION_TAG }} <why no answer can be assumed>`. Only for a question where a wrong assumption is hard to undo: data deleted or rewritten, money or prices, permissions or security, personal data, or a contract another team or system consumes. These are never assumed; refinement waits for a person.
 
    Write the questions in **plain business language, not technical jargon**. The person reading
    them is a domain expert, not an engineer.
 
     **The story is complete.** You answered every exploration question yourself and none remain
-    for the author. Call `update_issue` first, with the wrapped replacement body, and wait
+    for the author. A complete story has no open question anywhere in it: if the issue form has an
+    `Open questions` field, it says `None`, and a question you settled goes into the acceptance
+    criteria as the behaviour you chose. A question still open in the body is a question for the
+    author, so that is the outcome above, not this one. Call `update_issue` first, with the wrapped replacement body, and wait
     for it to come back. Send the whole body in that one call: it is the only thing this
     step has to get right.
 
@@ -1063,6 +1111,8 @@ timeout-minutes: 90
     - If the array includes the exact label `future`: `Refinement complete. The implement label has been added. Implementation is paused until the future label is removed.`
     - Otherwise: `Refinement complete. The implement label has been added and the implement workflow will start shortly.`
 
+    On a `${{ env.ASSUME_MODE }}` pass, add one sentence after that message: `The proposed answers were taken because nobody replied in time, and they are listed under "Assumed without a reply". If one is wrong, say so on the pull request.`
+
     If `update_issue` did not succeed, do not post either message: an issue that reads as
     refined with its body untouched is worse than one that says the run failed. Call
     `report_incomplete` with what the tool told you, and let the run be retried.

package/loops/workflows/shared/platform-defaults.md

@@ -1,53 +1,53 @@
----
-# Managed by @plainconceptsplatform/workflows. Source: loops/workflows/shared/platform-defaults.md. Update with `workflows update --force`; consumer edits may be overwritten.
-description: Shared network and safe-output defaults for catalog agent workflows, plus the verification rules every worker that builds or pushes has to follow. The body below is runtime-imported into each worker's prompt ahead of its own steps.
-
-network:
-  allowed:
-    - defaults
-    - forge.plainconcepts.com
-    # opencode fetches its model registry from models.opencode.ai at startup; without
-    # this host on the allowlist the fetch blocks bootstrap and the run stalls after
-    # "init" until the runner kills it. The apex "opencode.ai" is not enough.
-    - models.opencode.ai
-    - node
-    - github
-    - dotnet
-    - fonts
-    - login.microsoftonline.com
-    # centralised AgentMemory (App Service); the MCP shim needs it through the egress proxy
-    - agentmemory-pro-01.azurewebsites.net
-
-safe-outputs:
-  threat-detection: false
----
-
-## These runs are not interactive
-
-- Nothing resumes you. A turn that ends with text and no tool call ends the whole run, and the work
-  is discarded, whatever the text promised. "I'll read the context files first." as a last message
-  is a finished run: the Pliny-Bot merge gate did exactly that on #801, ended in twenty-three
-  seconds with exit code 0 and no outcome, and was retried twice before the pull request was handed
-  to a person for nothing.
-- So every message you write carries a tool call until the last one, which is the safe-output call
-  the task names. Say what you are about to do and do it in the same message. Never announce a step
-  and stop, never wait for a command, a reviewer or a "next turn".
-- A command the bash tool reports as moved to the background is still running: poll its output file
-  with tool calls (`sleep 40; tail -n 15 <file>`) until it shows an exit status, then go on.
-
-## Verification, for every worker that builds or pushes
-
-- Scope every check to the files you changed. This is the runner, not a preference: a
-  whole-repository lint, build or test run exhausts its memory and gets killed mid-run, which
-  fails the job with no useful output. Pass the changed paths to the linter (`pnpm exec biome
-  check <files>`), build only the projects containing them, and run only the test project that
-  covers them. Escalate to the full suite only after the scoped run passes and only when the
-  change crosses a project boundary.
-- Run nothing at all for a change that touches only documentation. A cold Release build on a
-  shared runner is minutes the run does not get back.
-- Never make a check pass by weakening it: not a deleted test, not a lowered threshold, not a
-  skipped step. Fix the cause and run it again.
-- Once the checks pass, run the project's lint fix command over the files you changed
-  (`pnpm lint:fix`, `pnpm exec biome check --write <changed-files>`, or its equivalent), or
-  correct what lint reports where no fix command exists. A branch that arrives with lint errors
-  gets sent back for them.
+---
+# Managed by @plainconceptsplatform/workflows. Source: loops/workflows/shared/platform-defaults.md. Update with `workflows update --force`; consumer edits may be overwritten.
+description: Shared network and safe-output defaults for catalog agent workflows, plus the verification rules every worker that builds or pushes has to follow. The body below is runtime-imported into each worker's prompt ahead of its own steps.
+
+network:
+  allowed:
+    - defaults
+    - forge.plainconcepts.com
+    # opencode fetches its model registry from models.opencode.ai at startup; without
+    # this host on the allowlist the fetch blocks bootstrap and the run stalls after
+    # "init" until the runner kills it. The apex "opencode.ai" is not enough.
+    - models.opencode.ai
+    - node
+    - github
+    - dotnet
+    - fonts
+    - login.microsoftonline.com
+    # centralised AgentMemory (App Service); the MCP shim needs it through the egress proxy
+    - agentmemory-pro-01.azurewebsites.net
+
+safe-outputs:
+  threat-detection: false
+---
+
+## These runs are not interactive
+
+- Nothing resumes you. A turn that ends with text and no tool call ends the whole run, and the work
+  is discarded, whatever the text promised. "I'll read the context files first." as a last message
+  is a finished run: the Pliny-Bot merge gate did exactly that on #801, ended in twenty-three
+  seconds with exit code 0 and no outcome, and was retried twice before the pull request was handed
+  to a person for nothing.
+- So every message you write carries a tool call until the last one, which is the safe-output call
+  the task names. Say what you are about to do and do it in the same message. Never announce a step
+  and stop, never wait for a command, a reviewer or a "next turn".
+- A command the bash tool reports as moved to the background is still running: poll its output file
+  with tool calls (`sleep 40; tail -n 15 <file>`) until it shows an exit status, then go on.
+
+## Verification, for every worker that builds or pushes
+
+- Scope every check to the files you changed. This is the runner, not a preference: a
+  whole-repository lint, build or test run exhausts its memory and gets killed mid-run, which
+  fails the job with no useful output. Pass the changed paths to the linter (`pnpm exec biome
+  check <files>`), build only the projects containing them, and run only the test project that
+  covers them. Escalate to the full suite only after the scoped run passes and only when the
+  change crosses a project boundary.
+- Run nothing at all for a change that touches only documentation. A cold Release build on a
+  shared runner is minutes the run does not get back.
+- Never make a check pass by weakening it: not a deleted test, not a lowered threshold, not a
+  skipped step. Fix the cause and run it again.
+- Once the checks pass, run the project's lint fix command over the files you changed
+  (`pnpm lint:fix`, `pnpm exec biome check --write <changed-files>`, or its equivalent), or
+  correct what lint reports where no fix command exists. A branch that arrives with lint errors
+  gets sent back for them.

package/loops/workflows/work-router.yml

@@ -83,6 +83,9 @@ run-name: >-
   && inputs.operation == 'audit'
   && format('Agent: Audit - manual{0}', '')
   || github.event_name == 'workflow_dispatch'
+  && inputs.operation == 'docs-audit'
+  && format('Agent: Docs Audit - manual{0}', '')
+  || github.event_name == 'workflow_dispatch'
   && inputs.operation == 'release'
   && format('Agent: Release{0}', '')
   || github.event_name == 'workflow_dispatch'
@@ -91,6 +94,9 @@ run-name: >-
   && github.event.schedule == '17 1 * * 1'
   && format('Agent: Audit - weekly{0}', '')
   || github.event_name == 'schedule'
+  && github.event.schedule == '47 2 1,15 * *'
+  && format('Agent: Docs Audit - fortnightly{0}', '')
+  || github.event_name == 'schedule'
   && github.event.schedule == '43 3 * * *'
   && format('Agentics: Audit Close - daily{0}', '')
   || github.event_name == 'schedule'
@@ -125,6 +131,9 @@ env:
   # first and the two of them consume the whole fleet. Pick a free slot per repository: see
   # "Scheduling across repositories" in the package README.
   AUDIT_CRON: "17 1 * * 1"
+  # The same idea for the documentation audit, if it is installed: see the same section of the
+  # package README. Two days a month, so a slot is a pair of days rather than a weekday.
+  DOCS_AUDIT_CRON: "47 2 1,15 * *"
   # The bot identities whose label changes and pull requests this router trusts. Space
   # separated, and every login the same account can present: GitHub reports an App as
   # `name[bot]` on some endpoints and `app/name` on others, so both spellings belong here.
@@ -185,6 +194,12 @@ env:
   # `pnpm run dev`, and a pull request with no plan costs one API call. Set it to "false" for a
   # repository whose app cannot start on a runner; operation=evidence still works by hand.
   EVIDENCE_ENABLED: "true"
+  # Working hours, Monday to Friday, that refine's questions wait for an answer. Every question
+  # carries the answer the bot would take; once this passes with no reply, or as soon as the
+  # author reacts with a thumbs-up, refine carries on with those answers and labels the issue
+  # `assumed`. A question marked as needing a decision is never assumed. "0" turns this off, and
+  # questions wait for a person however long that takes.
+  REFINE_ANSWER_TIMEOUT_HOURS: "24"
 
 on:
   issues:
@@ -221,6 +236,7 @@ on:
   # Cron to route mapping lives in .github/actions/classify-route/classify-route.sh.
   schedule:
     - cron: "17 1 * * 1" # audit slot, mirrored from env.AUDIT_CRON by the installer
+    - cron: "47 2 1,15 * *" # docs-audit slot, mirrored from env.DOCS_AUDIT_CRON by the installer
     - cron: "43 3 * * *"
     - cron: "0 6 * * *"
     - cron: "17 * * * *"
@@ -241,6 +257,7 @@ on:
           - merge-train
           - evidence
           - audit
+          - docs-audit
           - audit-close
           - cleanup-artifacts
           - reconcile-bot-pr-runs
@@ -256,12 +273,13 @@ on:
         required: false
         type: string
       mode:
-        description: "Refine mode: first or rerefine"
+        description: "Refine mode: first, rerefine or assume"
         required: false
         type: choice
         options:
           - first
           - rerefine
+          - assume
       ci-conclusion:
         description: "CI conclusion for merge-gate dispatch"
         required: false
@@ -684,7 +702,12 @@ jobs:
                             gh issue view "$feature" --repo "$REPO" --json body --jq '.body // ""' 2>/dev/null \
                               | grep -oiE 'blocked by #[0-9]+' | grep -oE '[0-9]+' || true
                           } | sort -u ); do
-                gh issue view "$b" --repo "$REPO" --json state --jq '.state' 2>/dev/null | grep -qix open || continue
+                # A feature's own children are not what the feature waits on. Refine's tracker lists them
+                # in the feature body as "#N ... Blocked by #M", and reading those lines as the feature's
+                # blockers held every child behind its siblings, and the first one behind itself.
+                info=$(gh issue view "$b" --repo "$REPO" --json state,body 2>/dev/null) || continue
+                printf '%s' "$info" | jq -e '(.state // "" | ascii_downcase) == "open"' >/dev/null || continue
+                printf '%s' "$info" | jq -r '.body // ""' | grep -qF "<!-- split-parent: ${feature} -->" && continue
                 waiting="$waiting #$b"
               done
             fi
@@ -741,6 +764,7 @@ jobs:
           gh issue edit "$ISSUE_NUMBER" --repo "$REPO" --remove-label bot-working >/dev/null 2>&1 || true
           marker='<!-- stack-held -->'
           if ! gh api "repos/$REPO/issues/$ISSUE_NUMBER/comments?per_page=100" --jq '.[].body' 2>/dev/null | grep -qF "$marker"; then
+            # shellcheck disable=SC2016
             printf '%s\nHeld until%s have landed on the default branch: this feature builds on them. It keeps `implement` and is released when they merge.\n' "$marker" "$waiting" > /tmp/held.md
             gh issue comment "$ISSUE_NUMBER" --repo "$REPO" --body-file /tmp/held.md >/dev/null || true
           fi
@@ -1148,6 +1172,24 @@ jobs:
       BOT_PRIVATE_KEY: ${{ secrets.BOT_PRIVATE_KEY }}
       AGENTMEMORY_SECRET: ${{ secrets.AGENTMEMORY_SECRET }}
 
+  call-docs-audit:
+    needs: classify
+    if: needs.classify.outputs.route == 'docs-audit'
+    uses: ./.github/workflows/agent-docs-audit.lock.yml
+    concurrency:
+      group: docs-audit
+      cancel-in-progress: false
+    permissions: write-all
+    with:
+      trigger-kind: ${{ needs.classify.outputs.trigger-kind }}
+    secrets:
+      OPENAI_API_KEY: ${{ secrets.FORGE_API_KEY }}
+      CODEX_API_KEY: ${{ secrets.FORGE_API_KEY }}
+      COPILOT_GITHUB_TOKEN: ${{ secrets.FORGE_API_KEY }}
+      BOT_APP_ID: ${{ secrets.BOT_APP_ID }}
+      BOT_PRIVATE_KEY: ${{ secrets.BOT_PRIVATE_KEY }}
+      AGENTMEMORY_SECRET: ${{ secrets.AGENTMEMORY_SECRET }}
+
   call-release:
     needs: [classify, authorize]
     if: needs.classify.outputs.route == 'release' && needs.authorize.outputs.trusted == 'true'
@@ -1298,6 +1340,7 @@ jobs:
                   # each cut from the same branch, and every landing left the others conflicting. The
                   # next landing releases the next child. A held child with no `Blocked by` of its
                   # own (held because a sibling was in flight) is free once it carries the hold marker.
+                  # shellcheck disable=SC2086
                   for child in $(printf '%s\n' $children | sort -n); do
                     [ "$child" = "$closed_issue" ] && continue
                     meta=$(gh issue view "$child" --repo "$REPO" --json state,labels,body 2>/dev/null || echo '{}')
@@ -1424,7 +1467,11 @@ jobs:
               gh api "repos/$REPO/issues/$1/dependencies/blocked_by" --jq '.[] | select(.state == "open") | .number' 2>/dev/null || true
               for b in $(gh issue view "$1" --repo "$REPO" --json body --jq '.body // ""' 2>/dev/null \
                            | grep -oiE 'blocked by #[0-9]+' | grep -oE '[0-9]+' | sort -u || true); do
-                gh issue view "$b" --repo "$REPO" --json state --jq '.state' 2>/dev/null | grep -qix open && echo "$b" || true
+                # The feature's own children, listed in its tracker with their own "Blocked by", are not blockers.
+                info=$(gh issue view "$b" --repo "$REPO" --json state,body 2>/dev/null) || continue
+                printf '%s' "$info" | jq -e '(.state // "" | ascii_downcase) == "open"' >/dev/null || continue
+                printf '%s' "$info" | jq -r '.body // ""' | grep -qF "<!-- split-parent: $1 -->" && continue
+                echo "$b"
               done
             } | grep -vx "$parent" | sort -u || true
           }
@@ -1476,6 +1523,7 @@ jobs:
             fi
             # One child per feature, the lowest-numbered free one; each landing on the feature branch
             # releases the next (land-stack-child), so siblings never build side by side.
+            # shellcheck disable=SC2086
             for child in $(printf '%s\n' ${next_children[$feature]} | sort -n); do
               own=$(gh issue view "$child" --repo "$REPO" --json body --jq '.body // ""' 2>/dev/null \
                 | grep -oiE 'blocked by #[0-9]+' | grep -oE '[0-9]+' | sort -u || true)
@@ -1645,6 +1693,75 @@ jobs:
                   gh api "repos/$REPO/actions/runs/$run_id/approve" --method POST
                 done
             done
+      # Refine's questions do not wait forever. Nine of the 21 batches that were really asked in
+      # Odyssey, Numa, Bots and DeliveryMetrics up to November 2026 never got a reply, and those
+      # issues stayed parked. Each question now carries the answer the bot would take, and once
+      # the working hours pass, or the author or an assignee reacts with a thumbs-up, refine runs
+      # again in assume mode and takes them. Batches written before the proposals existed, and any
+      # batch holding a question that needs a decision, still wait for a person.
+      - name: Take refine's proposed answers once nobody replied in time
+        if: env.REFINE_ANSWER_TIMEOUT_HOURS != '0'
+        env:
+          GH_TOKEN: ${{ steps.app-token.outputs.token }}
+          REPO: ${{ github.repository }}
+          REFINE_MARKER: "<!-- agent-refine -->"
+          QUESTIONS_LINE: "I have some questions about this issue"
+          PROPOSED_TAG: "**Proposed:**"
+          DECISION_TAG: "**Your decision needed:**"
+        run: |
+          set -euo pipefail
+          timeout_hours="${REFINE_ANSWER_TIMEOUT_HOURS:-24}"
+
+          # Hours since $1 that fall on a weekday, in UTC, counted up to the timeout and no further.
+          working_hours_since() {
+            local t now h=0
+            t=$(date -u -d "$1" +%s)
+            now=$(date -u +%s)
+            while [ "$t" -lt "$now" ] && [ "$h" -lt "$timeout_hours" ]; do
+              [ "$(date -u -d "@$t" +%u)" -le 5 ] && h=$((h + 1))
+              t=$((t + 3600))
+            done
+            echo "$h"
+          }
+
+          gh issue list --repo "$REPO" --state open --label refine --label review --limit 100 \
+            --json number,author,assignees,labels \
+            --jq '.[] | select([.labels[].name] | (index("bot-working") or index("assumed")) | not)
+                  | [.number, ([.author.login] + [.assignees[].login] | join(" "))] | @tsv' |
+            while IFS=$'\t' read -r issue people; do
+              [ -n "$issue" ] || continue
+              comments=$(gh api --paginate "repos/$REPO/issues/$issue/comments?per_page=100" | jq -s 'add // []')
+              asked=$(jq -c --arg marker "$REFINE_MARKER" --arg line "$QUESTIONS_LINE" '
+                [.[] | select(.user.type == "Bot" and (.body | contains($marker)) and (.body | contains($line)))]
+                | last // empty | {id, created_at, body}' <<<"$comments")
+              [ -n "$asked" ] || continue
+              asked_at=$(jq -r '.created_at' <<<"$asked")
+              body=$(jq -r '.body' <<<"$asked")
+
+              # A person spoke after the questions: that reply is refine's to read, not a silence.
+              replied=$(jq --arg at "$asked_at" '[.[] | select(.user.type != "Bot" and .created_at > $at)] | length' <<<"$comments")
+              [ "$replied" -eq 0 ] || continue
+              case "$body" in *"$DECISION_TAG"*) echo "#$issue waits for a decision; not assuming."; continue ;; esac
+              case "$body" in *"$PROPOSED_TAG"*) ;; *) continue ;; esac
+
+              accepted=false
+              thumbs=$(gh api "repos/$REPO/issues/comments/$(jq -r '.id' <<<"$asked")/reactions" \
+                --jq '[.[] | select(.content == "+1") | .user.login] | join(" ")' 2>/dev/null || true)
+              for login in $thumbs; do
+                case " $people " in *" $login "*) accepted=true ;; esac
+              done
+              hours=$(working_hours_since "$asked_at")
+              if [ "$accepted" = true ]; then
+                echo "#$issue: the proposed answers were accepted with a thumbs-up; refining with them."
+              elif [ "$hours" -ge "$timeout_hours" ]; then
+                echo "#$issue: no reply in ${timeout_hours} working hours; refining with the proposed answers."
+              else
+                continue
+              fi
+              gh api "repos/$REPO/actions/workflows/work-router.yml/dispatches" --method POST \
+                -f ref="$(gh api "repos/$REPO" --jq .default_branch)" \
+                -f "inputs[operation]=refine" -f "inputs[issue-number]=$issue" -f "inputs[mode]=assume"
+            done
 
   audit-close:
     needs: classify

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plainconceptsplatform/workflows",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "description": "Install and update Platform GitHub agentic workflows.",
   "keywords": [
     "github-actions",