Content methods, view families, infographics, and one scorecard apply across tasks.
runtime.entry=squad triages through Agent-Squad. Simple work is one kernel step. The default stays direct.
Switching the default waits for paired scores and a first-token latency within 3 seconds.
Test plan
go test ./... -count=1
house-style unittest for visual summaries
## Summary
- Content methods, view families, infographics, and one scorecard apply across tasks.
- runtime.entry=squad triages through Agent-Squad. Simple work is one kernel step. The default stays direct.
- Switching the default waits for paired scores and a first-token latency within 3 seconds.
## Test plan
- [x] go test ./... -count=1
- [x] house-style unittest for visual summaries
Why: Layout rules alone do not produce conclusion-first documents, extra views, or infographics, and nothing scored a deliverable before it was returned.
Evidence: go test ./internal/prompts/ ./internal/quality/ ./internal/tools/ ./internal/squadadapter/ ./eval/ -count=1 and the house-style unittest passed in the previous session.
Impact: Every task inherits content rules. Meetings, reports, and comparisons can name a view family. Long documents without a visual summary warn. quality_review and the squad checker share one scorecard.
Refs: deliverable-quality-system A1-A5
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Squad steps previously ran without tools, and the product had no way to make the squad the conversation entry without losing streaming, cards, or the deliverable guard.
Evidence: go test ./... -count=1 passed, including streaming, cardflow, false-deliverable rejection, tool allowlist, model routing, usage, cancel, and turn and tool budgets.
Impact: runtime.entry defaults to direct. squad uses one kernel step for simple work and the leader for the rest. squad_orchestrate is hidden in that mode. The default is not switched.
Refs: deliverable-quality-system B3-B5
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit e50905dcee into main2026-10-01 09:35:55 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan