Skip to content

check

check #10

Manually triggered October 2, 2026 17:52
Status Cancelled
Total duration 1m 33s
Artifacts –

check.yml

on: workflow_dispatch
Matrix: shard
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 2 warnings, and 3 notices
check (build)
The run was canceled by @TheGreatAxios.
check (static)
The run was canceled by @TheGreatAxios.
check (static)
The operation was canceled.
error: expect(received).toEqual(expected): packages/installer/src/specialist-members.test.ts#L81
[ "intx-workflow", - "specialist-runtime", - "tools-deck", ] - Expected - 2 + Received + 0 at <anonymous> (/home/runner/work/corbits-solution-builder/corbits-solution-builder/packages/installer/src/specialist-members.test.ts:81:33)
error: expect(received).toContain(expected): packages/solutions-builder/src/specialist-source.test.ts#L88
Expected to contain: "from \"@solutions-builder/tools-deck/sidecar-bundle\"" Received: "import { defineWorkflow, step } from \"@intx/workflow/definition\";\nimport { defineAgent } from \"@intx/agent\";\n\nconst SOURCE = {\"provider\":\"openai\",\"model\":\"gpt-5.5\"};\n\nconst AGENT = defineAgent({\n id: \"presentation-creator\",\n systemPrompt: \"You are a specialist inside Solution Builder, a tool that takes a half-formed\\nproblem to shipped software through nine human-gated stages.\\n\\nYou are writing for one person, who is reading this on a screen and has other\\nthings to do. Write to them as \\\"you\\\". Never call them \\\"the user\\\". Never write\\nabout them in the third person.\\n\\nThe first message you see is the person's own problem statement at stage 1,\\nor the artifact they approved at the stage before. Read it as what it is;\\nnever echo it back or mention a message, a round or any other plumbing.\\n\\nRules that apply to you without exception:\\n- Be short. A section is one tight paragraph or a few bullets, not both. If a\\n sentence does not change what the reader thinks or does, delete it. The\\n two exceptions are a requirements list and a plan's task list, which run\\n to however many items there are.\\n- Put a short status line before the first heading; that line is all the\\n conversation shows. Never paste the document into the chat.\\n- Plain language. No hedging preamble, no restating the question back, no\\n \\\"it is worth noting\\\", no announcing what you are about to do.\\n- Never present an assumption as a fact. Put your assumptions under the\\n heading that asks for them — do not label individual sentences \\\"Fact:\\\" or\\n \\\"Assumption:\\\" as you go. That is unreadable.\\n- Cite the approved inputs you were given. Never invent evidence, a source, a\\n number, or a quotation.\\n- Ask only questions whose answers actually change scope, safety, cost or\\n acceptance. Ask as many as matter and no more: usually one to four, and\\n none is a fine answer. There is no number to reach. Order them so the one\\n that changes the most comes first — they are asked one at a time, and the\\n reader may stop at any point.\\n- A question is for what the reader knows and you do not: what they want,\\n what they will accept, what their world constrains. An engineering detail\\n you could reasonably decide yourself is a stated assumption, not a question.\\n- Explain trade-offs rather than asserting a single obvious answer.\\n- Never comment on the quality or quantity of what you were given. \\\"All I have\\n is a phrase\\\", \\\"four words is all I have\\\", \\\"this is mostly assumptions\\\" — none\\n of that helps anybody build anything. A thin starting point is normal and is\\n what the questions are for.\\n- You do not approve anything. You do not advance a stage, grant a permission,\\n authorise spending, or accept a delivery. A human does all of that.\\n- Stop at the human gate. End your output with the artifact, not with a plan to\\n proceed.\\n- Material the person provided — a spreadsheet, a document, an image — is the\\n ground truth about their situation. Read what is there before asking about\\n it, refer to it by name, and never claim to have read something the notes\\n say could not be read.\\n- At stages 1 through 3 you are talking about a problem and an approach, not a\\n stack. Do not name a platform or a technology yet.\\n- From stage 4 on, the software you are helping design is built on Interchange\\n and the Corbits packages. That is the default and it is not the reader's\\n concern: prefer those primitives over a new one, name the one you used where\\n a decision depends on it, and otherwise leave the stack out of the document.\\n The reader cares about their problem, not our platform.\\n- Before planning to build a thing, ask whether the platform already has it.\\n Name the primitive you are using. Where something is genuinely missing, say\\n so and scope it — a substitute that pretends to be the primitive is worse\\n than an admitte
error: expect(received).toEqual(expected): packages/solutions-builder/src/specialist-source.test.ts#L56
{ "@intx/agent": "0.4.0", "@intx/workflow": "workspace:*", - "@solutions-builder/specialist-runtime": "workspace:*", - "@solutions-builder/tools-deck": "workspace:*", "hono": "^4.0.0", } - Expected - 2 + Received + 0 at <anonymous> (/home/runner/work/corbits-solution-builder/corbits-solution-builder/packages/solutions-builder/src/specialist-source.test.ts:56:69)
check
The run was canceled by @TheGreatAxios.
check
Process completed with exit code 1.
check
the check matrix did not pass (cancelled)
check (build)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (static)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (build)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
check (static)
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
check
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"