@plainconceptsplatform/workflows 1.13.1 → 1.14.1

package/loops/workflows/agent-refine.md

@@ -738,7 +738,20 @@ jobs:
             output_tokens=$(jq -r '.output_tokens // empty' usage-read/agent_usage.json 2>/dev/null || echo "")
           fi
           if [ -n "$output_tokens" ] && [ "$output_tokens" -gt 20000 ]; then
-            echo "truncated=This attempt consumed ${output_tokens} output tokens and still produced no outcome. That is what provider output truncation looks like, not an outage: the model hit the single-response cap mid-generation and every call it was writing was lost. If this repeats, split the issue or tighten its body." >> "$GITHUB_OUTPUT"
+            # A run that burned tokens and produced items the validator refused is not
+            # truncation: the agent finished, and the validator did not recognise the
+            # outcome shape (Bots #1336, run 42214146974: 50926 output tokens, 2 items,
+            # draft marker stripped by process_safe_outputs, questions line paraphrased).
+            # Only call it truncation when the agent spent tokens and produced nothing.
+            item_count=0
+            if [ -f usage-read/agent_output.json ]; then
+              item_count=$(jq '.items | length' usage-read/agent_output.json 2>/dev/null || echo 0)
+            fi
+            if [ "$item_count" -gt 0 ]; then
+              echo "truncated=This attempt consumed ${output_tokens} output tokens and produced ${item_count} item(s), but the validator could not recognise the outcome. The agent finished its work: check the run artifacts (agent_output.json, safeoutputs.jsonl) against the validator's expected shape before retrying." >> "$GITHUB_OUTPUT"
+            else
+              echo "truncated=This attempt consumed ${output_tokens} output tokens and still produced no outcome. That is what provider output truncation looks like, not an outage: the model hit the single-response cap mid-generation and every call it was writing was lost. If this repeats, split the issue or tighten its body." >> "$GITHUB_OUTPUT"
+            fi
           else
             echo "truncated=" >> "$GITHUB_OUTPUT"
           fi

package/loops/workflows/shared/opencode-ci.md

@@ -208,11 +208,10 @@ pre-agent-steps:
     # Two of the three run here. pc-system-reminders gates shell and edits on skills a CI
     # worker's prompt does not load, and has never run in CI; it stays off until it does.
     #
-    # The tier models come from AGENT_TIER_MODEL when a worker sets it. The AWF proxy refuses
-    # a model it has no AI credits price for; harness.json names carina-60b and quasar-438b,
-    # which had none until the `models.providers` prices at the top of this file (Atlas #2016).
-    # CI still pins every tier to one model, through the gitignored per-user override the
-    # plugin reads first, until a run on the newly priced models has passed.
+    # The tier models come from AGENT_TIER_MODEL when a worker sets it. The implement worker
+    # leaves it empty so harness.json drives: plan=glm-5-3, build/fast=glm-5-2. A repository
+    # whose CI account is not granted a tier model can still pin every tier to one model
+    # through the gitignored per-user override the plugin reads first.
     run: |
       set -euo pipefail
       if [ ! -f .opencode/package.json ]; then
@@ -246,6 +245,19 @@ pre-agent-steps:
       echo "Harness plugins: $(ls .opencode/plugins | tr '\n' ' ')"
       echo "Tier models: $(jq -c '.models' .opencode/harness.user.json 2>/dev/null || jq -c '.models' .opencode/harness.json)"
 
+  - name: Sync harness agents and print model routing
+    # The plugin writes these at startup, but OpenCode builds the task enum from what
+    # exists when it starts. Generating them here makes planner-sub and the tier
+    # variants visible from the first turn; the doctor is the audit line.
+    run: |
+      set -euo pipefail
+      if [ -f .opencode/scripts/sync-agents.mjs ] && [ -f .opencode/plugins/pc-subagent-tiers-core.js ]; then
+        node .opencode/scripts/sync-agents.mjs --strict
+      fi
+      if [ -f .opencode/scripts/harness-doctor.mjs ]; then
+        node .opencode/scripts/harness-doctor.mjs --strict
+      fi
+
   - name: Merge the CI-only OpenCode provider into opencode.jsonc
     env:
       GH_TOKEN: ${{ github.token }}

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/package.json

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