bump-default-chat — Workgraph live mirror

Metadata

Status	done
Assigned	`agent-920`
Agent identity	`3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3`
Created	2026-04-28T20:16:08.078856901+00:00
Started	2026-04-28T20:19:07.976181994+00:00
Completed	2026-04-28T20:34:03.300282900+00:00
Tags	`eval-scheduled`
Eval score	0.82
└ blocking impact	0.86
└ completeness	0.80
└ coordination overhead	0.87
└ correctness	0.82
└ downstream usability	0.83
└ efficiency	0.83
└ intent fidelity	0.79
└ style adherence	0.81

Description

dispatcher.max_coordinators defaults to 4. User wants 16 as the new default. Tiny config-default change.

Steps

Find every place the default is hardcoded (src/dispatch/, wg config init, wg setup, hard-coded fallback when no config exists).
Change to 16.
Update any docs / comments that reference '4' as the cap.

Out of scope

Migrating existing user configs (their explicit value wins; only changing the default)
Removing the cap entirely (separate question; keeping the knob)
Renaming the config key (still max_coordinators for now even though terminology is migrating to 'chat')

Validation

All hardcoded '4' default occurrences for the chat cap updated to 16
Fresh wg init in a new dir produces a config with cap=16 (or no entry; falling back to 16 in code)
Existing configs with explicit max_coordinators = 4 are NOT silently rewritten — user's explicit value still wins
cargo build + cargo test pass

## Description

`dispatcher.max_coordinators` defaults to 4. User wants 16 as the new default. Tiny config-default change.

### Steps
1. Find every place the default is hardcoded (`src/dispatch/`, `wg config init`, `wg setup`, hard-coded fallback when no config exists).
2. Change to 16.
3. Update any docs / comments that reference '4' as the cap.

### Out of scope
- Migrating existing user configs (their explicit value wins; only changing the default)
- Removing the cap entirely (separate question; keeping the knob)
- Renaming the config key (still `max_coordinators` for now even though terminology is migrating to 'chat')

## Validation

- [ ] All hardcoded '4' default occurrences for the chat cap updated to 16
- [ ] Fresh `wg init` in a new dir produces a config with cap=16 (or no entry; falling back to 16 in code)
- [ ] Existing configs with explicit `max_coordinators = 4` are NOT silently rewritten — user's explicit value still wins
- [ ] cargo build + cargo test pass

Depends on

done .assign-bump-default-chat

Required by

(none)

Log

2026-04-28T20:16:08.036894943+00:00 Task paused
2026-04-28T20:17:34.570848476+00:00 Task published
2026-04-28T20:19:07.976185721+00:00 Spawned by coordinator --executor claude --model opus
2026-04-28T20:19:19.280046033+00:00 Starting: searching for max_coordinators defaults
2026-04-28T20:33:23.678983014+00:00 Updated default_max_coordinators 4→16 in src/config.rs and CLI/doc references. Verified: fresh wg init produces max_coordinators=16; existing explicit max_coordinators=4 in user config is preserved; cargo build OK.
2026-04-28T20:33:55.205157224+00:00 Committed: cc1756659 — pushed to remote
2026-04-28T20:34:03.300287519+00:00 Task pending eval (agent reported done; awaiting `.evaluate-*` to score)
2026-04-28T20:37:24.347949102+00:00 PendingEval → Done (evaluator passed; downstream unblocks)