feat(integration): WS0-WS5 + activation wiring (context_provider + /new-task) #47

Merged
amoussa1229 merged 13 commits from feat/ws-activation-wiring into main 2026-06-23 19:50:29 +00:00
amoussa1229 commented 2026-06-23 16:39:18 +00:00 (Migrated from github.com)

Integration + activation wiring (DRAFT — holds for merge-order decision)

Combines WS0–WS5 (#43 #44 #45 #46) on one branch and adds the wiring that flips the safe seams ON in run-team.py serve. Opened to verify the four workstreams compose and the wiring works end-to-end before anything hits main.

What's wired live (safe, ungated)

  • WS1 bind_multi_invoker() — already called in _cmd_serve (in-process GPT-4.1/Gemini/DeepSeek invokers).
  • WS5 (D10) context_provider — injects the Sea Haven handbook conventions into the planner prompt (zero-arg handbook loader; fail-safe to "" when the dir is absent).
  • WS2 /new-task — an allowlisted Slack /new-task starts a task on this coordinator (set_new_task_callback → start_task; AUTHZ-01 owner allowlist gates it upstream).

Deliberately NOT wired

  • P3 dispatch_node / build_verify stays inert. Activating it correctly needs a per-task expected_run_id bound into gated_build_verify_wiring (plumbing that doesn't exist yet) and the CI trust-boundary /sh-security-review + GPT-4.1 re-review on the enabled workflow. Out of scope here.

Verification

  • Full agent-team suite: 1140 passed, ruff check + ruff format --check clean.
  • +5 activation-wiring tests proving each seam flips on without a live Slack socket.

Merge order (decision pending)

This branch contains the four WS merges + wiring. Options: (a) merge the 4 WS PRs first, then a wiring-only follow-up; (b) merge this integration branch as one. Held per request until decided.

🤖 Generated with Claude Code

## Integration + activation wiring (DRAFT — holds for merge-order decision) Combines WS0–WS5 (#43 #44 #45 #46) on one branch and adds the wiring that flips the **safe** seams ON in `run-team.py serve`. Opened to verify the four workstreams compose and the wiring works end-to-end before anything hits `main`. ### What's wired live (safe, ungated) - **WS1** `bind_multi_invoker()` — already called in `_cmd_serve` (in-process GPT-4.1/Gemini/DeepSeek invokers). - **WS5 (D10)** `context_provider` — injects the Sea Haven handbook conventions into the planner prompt (zero-arg handbook loader; fail-safe to `""` when the dir is absent). - **WS2** `/new-task` — an allowlisted Slack `/new-task` starts a task on this coordinator (`set_new_task_callback` → `start_task`; AUTHZ-01 owner allowlist gates it upstream). ### Deliberately NOT wired - **P3 `dispatch_node` / `build_verify`** stays inert. Activating it correctly needs a per-task `expected_run_id` bound into `gated_build_verify_wiring` (plumbing that doesn't exist yet) **and** the CI trust-boundary `/sh-security-review` + GPT-4.1 re-review on the enabled workflow. Out of scope here. ### Verification - Full agent-team suite: **1140 passed**, `ruff check` + `ruff format --check` clean. - +5 activation-wiring tests proving each seam flips on without a live Slack socket. ### Merge order (decision pending) This branch contains the four WS merges + wiring. Options: (a) merge the 4 WS PRs first, then a wiring-only follow-up; (b) merge this integration branch as one. Held per request until decided. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
This repo is archived. You cannot comment on pull requests.
No description provided.