unic / unic/unic-agents-plugins

bug(unic-archon-dlc): the summary's § "Checks this review did not run" is false when a sub-agent ran a declared command

Open
#487 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app:unic-archon-dlc bug needs-specs p2 wayfinder:grilling
Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
16h 43m
Merged PRs (30d)
19

Description

Observed

Run 3, unic-dlc-pr-review iteration 2, summary thread on PR 5881: § "Checks this review did not run" states "this review executed none of them" over the seven declared commands. The same summary's praise section says "pnpm check-types passes across all three packages". The events table shows the review sub-agent ran pnpm check-types 2>&1 | tail -25 and wrote "pnpm check-types (clean)"; a second sub-agent recorded the same.

Why it matters

That block is the one sentence a reader uses to know what the run measured. It is written from the Box's instruction ("runs no build, lint, type-check or test command"), not from what the sub-agents did, so it is a statement about the process presented as a statement about the run.

Evidence

Not decided

  • Whether the block should be derived from the sub-agents' actual tool calls, or the sub-agents forbidden from running declared commands, or both.

Filed 2026-09-17 by wayfinder-orchestrator-10 from run 3's measurements. needs-specs: grill before dispatch.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with docs/research/2026-08-31-dlc-run-2-findings.md, the dispatch record in issue #457, and the harvested tool_called events and transcripts named in this issue. Determine whether the summary should use actual sub-agent calls, enforce the declared restriction, or both; the issue is complete when that behavior is specified and the false statement can no longer be produced.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
devtools
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.