feat(claude): add /board-triage and fix org + WIQL handling in azure-boards-organiser

[jinyeow]

Adds a /board-triage command, and fixes two defects that made the existing commands unrunnable on this machine.

What /board-triage does

Answers "what's in flight, what's next, am I overloaded" from live data instead of a stale snapshot. It queries ADO for items assigned to me that are in the In Development Kanban column or in state Blocked, joins each to its matching initiative in a separate project-brain repo, then reports a load band and exactly three ranked recommendations.

Two deliberate constraints:

• Read-only against ADO. It reports; it never changes work-item or PR state.
• It never writes a priority snapshot back into the brain. ADO is the system of record for item state; a second copy goes stale within days, which is the failure mode the command exists to avoid.

Bug fixes to existing commands

Multi-line WIQL here-strings break az boards query on Windows. The --wiql value is truncated at the first newline, so every flag after it — including --organization — never reaches az, and it fails with --organization must be specified. That reads like an auth problem and is not. Verified against four queries: all four failed un-flattened, all four succeeded flattened. Fix is -replace '\s*\r?\n\s*', ' '.

Org was documented as coming from az devops configure --list, which can be empty. Now a required org key in config.json, passed explicitly as --organization on every call. --org is not an accepted abbreviation and fails the same misleading way.

Review

Reviewed by Codex and a Claude subagent independently. Both found the load classification non-deterministic — the rule list and its fallback could both fire on one item and disagree, changing the reported colour band. Fixed as an ordered, first-match-wins, exhaustive procedure with the staleness trust gate above every content-reading rule.

Codex additionally found that two of the four prioritisation criteria rank on pull-request state and unanswered work-item questions, which no step fetched — so they were being inferred from prose. This was not hypothetical: the first live run ranked an item on "a reviewer is waiting" when that item has zero external commenters. Fixed with a read-only shortlist-only enrichment step plus an evidence-or-skip rule, so a criterion applies only with a citable fact and ties are reported as ties.

Also closed: exactly-one-match required per join pass (ambiguous joins are reported, never resolved by iteration order); a child item can no longer inherit blockers from a parent initiative that never mentions it; deterministic truncation limits and ordering.

Verified live

• The full triage query, returning 15 real items.
• Linked-PR discovery via ArtifactLink relations (vstfs:///Git/PullRequestId/..., URL-decoded).
• az repos pr show returning the status / mergeStatus / reviewers[].vote triple.
• Work-item comments via the REST tier — the skill's first worked az rest example.
• All four previously-broken sibling queries, flattened.

Follow-up

The other 9 commands still carry both defects and are tracked in #46. Not in scope here.