🤖 Agentic Desk Digest

[dpyc-agentic-desk]

🤖 Agentic Desk Digest — 2026-08-31T00:00:00Z

---

🚨 Needs a human

Repo	Issue/PR	Severity	Why it needs you
cypher-mcp	#70 check_authority_balance always fails	sev/high blocked/upstream	Cross-repo SDK bug — proof signed for check_balance but wire name is authority_check_balance. Affects cypher, schwab, weather (tollbooth-sample), excalibur. No upstream issue exists in tollbooth-dpyc yet. Fix is one line in authority_client.py:181.
thebrain-mcp	#234 Deploy did not land	sev/high agent/fix awaiting-funds	Factory out of LLM credits; canary re-runs on recovery. PR #235 (qa/pass) ready to merge once funds restore.
taxsort-mcp	#96 Deploy did not land	sev/high agent/fix awaiting-funds	Same factory credit exhaustion. Two dep-update PRs open (#97, #98).
excalibur-mcp	#341 Detached resolve never dispatches	sev/high	Every submit 409s on closure_b64=None, silently falls back in-process. Core ledger path broken.
excalibur-mcp	#546 CheckPriceResult declares fields check_price never returns	sev/low agent/retriage	Field mismatch — consumers cast around it. Re-triaged after funding outage.
cypher-mcp	#114 Same CheckPriceResult field mismatch	sev/low agent/retriage	Duplicate pattern as excalibur #546.
optionality-mcp	#116 Same CheckPriceResult field mismatch	sev/low agent/retriage	Duplicate pattern; consumers work around with casts.

---

🛫 In flight

Repo	Item	Status
thebrain-mcp	PR #235 Force fresh redeploy	qa/pass — merge when funds restore
tollbooth-dpyc	PR #181 Update to v0.89.0	Renovate dep update
tollbooth-authority	PR #158 Update to v0.89.0	Renovate dep update
taxsort-mcp	PR #97 / #98	Renovate dep updates (tollbooth-dpyc v0.89.0, frontend deps)
tollbooth-sample	PR #112 Update to v0.89.0	Renovate dep update
excalibur-mcp	PR #547 / #548	Renovate dep updates (setup-uv v10, frontend deps)

---

❌ Rejected this week

No issues closed with rejected/* label in the last 7 days across all 12 repos.

---

🔗 Escalation chains

Origin (blocked/upstream)	Upstream target	Upstream status	Chain state
cypher-mcp #70 check_authority_balance proof mismatch	tollbooth-dpyc (SDK)	NO ISSUE EXISTS	🔴 Broken chain — downstream filed blocked/upstream but upstream issue never created. Fix known: authority_client.py:181 sign for authority_check_balance not check_balance. Affects 4+ operators. Action: Create tollbooth-dpyc issue, fix, release, then downstream dep bumps.

---

📊 Repo snapshot (open counts)

Repo	Issues	PRs	Notable labels
tollbooth-dpyc	0	1	deps
schwab-mcp	0	0	—
thebrain-mcp	1	1	agent/fix, awaiting-funds, qa/pass
excalibur-mcp	2	2	sev/high, sev/low, agent/retriage, deps
cypher-mcp	2	0	sev/high blocked/upstream, sev/low agent/retriage
optionality-mcp	1	0	sev/low agent/retriage
taxsort-mcp	1	2	sev/high agent/fix awaiting-funds, deps
tollbooth-authority	0	1	deps
tollbooth-wasmcp	0	0	—
tollbooth-fermyon	0	0	—
dpyc-oracle	0	0	—
tollbooth-sample	1	1	type/question sev/low, deps

---

Generated by Agentic Desk Dispatcher. Sweep covers 12 repos under lonniev/*.

[dpyc-agentic-desk]

Triage note (Porter)

Issue #154 is not a triagable work item. It is an automated "Agentic Desk Digest" generated by app/dpyc-agentic-desk. Its content is operational telemetry summarizing the state of other repositories (tollbooth-sample, excalibur-mcp, tollbooth-dpyc). It contains:

• A "Needs a human" section pointing to issues in sibling repos
• An "In flight" item already labeled agent/fix
• Escalation chain summaries

Classification: None of type/*, sev/*, or area/* apply — this is a status digest, not a bug/feature/question/chore.

Disposition: This requires no routing action (agent/fix, rejected/*, blocked/upstream, needs-info). The digest is informational output from the Agentic Desk workflow itself.

Why graph tools were not called: The mandatory mcp__graph__cypher_* tools for record_triage/record_scope bookkeeping are not present in this execution environment. Per the give-up clause, this comment documents the exact limitation. No further action is appropriate for this digest issue.

The digest correctly surfaces that human attention is needed on the cross-repo escalations listed, but that work belongs in the target repos, not here.