Unclassified

IntegrateWise — Round-Executable Action Sequence

Start state: commit 495a0295 on main, clean working tree
Canonical distribution: IW-Spine-Network MCP only; no separate plugin package
Public tool contract: exactly 19 tools
Execution paths: Dev Internal → Customer Zero → Product to Users

Round 1 — P0: Contract/Code Conflicts

Entry criteria: working tree clean at 495a0295
Exit criteria: all P0 #1–7 items verified end-to-end, no stale IW-Continuity-Bridge code references remain, tests pass

Actions

  1. P0 #1 Grep the widest sensible surface for the stale claim “MCP only; no Plugin package” and replace with the canonical phrasing: one MCP artifact in MCP marketplaces/registries, no separate plugin package. Update docs, README, marketplace specs, and any code comments/docs that still publish a Plugin artifact.
  2. P0 #2 Complete the live MCP identity rename from IW-Continuity-Bridge to IW-Spine-Network MCP in all runtime metadata, server names, worker names, route identifiers, platform catalog entries, and marketplace metadata. Do not break request-path compatibility unless explicitly required.
  3. P0 #3 Expand packages/spine-network/src/index.ts to the exact 19-tool frozen contract. Preserve the existing Gateway routing pattern and add any missing semantic tools.
  4. P0 #4 Audit every marketplace profile/app definition that exposes tools. Reduce or align any 9-tool/23-tool profiles to the frozen 19-tool contract.
  5. P0 #5 Rewrite the stale Spine Network distribution manifest/doc to separate Plugin and MCP artifacts, switch to Clerk/Gateway authentication, make human approval mandatory, and remove any ready_for_submission claims.
  6. P0 #6 Replace or archive the legacy iw-continuity-bridge marketplace entry. Do not delete if it is still referenced by runtime tests.
  7. P0 #7 Correct marketplace/apps/iw-spine-network.json: tool count must equal 19, requiresApproval must be true, metadata must match the canonical name.

Commit boundary

  • Commit message: chore: complete P0 contract/code alignment to IW-Spine-Network MCP
  • Must pass: pnpm run typecheck --filter packages/spine-network, targeted mcp-connector + gateway tests

Round 2 — P0: Infrastructure and Authentication

Entry criteria: Round 1 committed
Exit criteria: auth and DNS prerequisites explicit, no unknowns in config/keys, secrets placement verified

Actions

  1. P0 #8–9 Inventory current DNS and auth domain state. Produce an explicit remediation checklist for gateway, api, marketplace, workbench, status, and auth.integratewise.ai. Do not guess—state exact Cloudflare/Clerk actions required.
  2. P0 #10 Implement the single shared auth node in code/config: Clerk identity + OAuth + tenant/workspace resolution + marketplace installation identity. Wire Gateway and MCP connector service through it.
  3. P0 #11 Add an environment/tenancy manifest/checklist that proves Dev Internal / Customer Zero / Customer Production isolation.
  4. P0 #12 Review Neon migration 035 for correctness against live schema; add a verification query or test that proves table/column presence.
  5. P0 #13–14 Define strict connector_bindings / connector_schema_bindings. Audit D1, KV, R2, queues, secrets, audit log, and credential wall bindings; list exactly what is missing.

Commit boundary

  • May require multiple commits if external DNS/Clerk changes are needed
  • Code/config commits must pass targeted typecheck/tests

Round 3 — P1: Build IW-Spine-Network Plugin and MCP

Entry criteria: Round 2 committed
Exit criteria: both artifacts have working skeletons and canonical tooling

Actions

  1. P1 #15–21 Build the Plugin package:
    • Package, OAuth, consent, revocation, clean tenant activation flow
    • Sandboxed embedded UI surface
    • Widgets for active work, Spine status, entity/work search, capability picker, proposal/evidence, approval confirmation, execution progress, Open Workbench
  2. P1 #22–28 Build the MCP package:
    • Publish exact 19 tools from one canonical source
    • Generate valid versioned server.json
    • Add OAuth scopes, annotations, error/result schemas
    • Optional MCP App widgets for compatible clients
    • Open Workbench launch contract
  3. P1 #29–35 Implement discovery origins:
    • host_composed, host_delegated, iw_direct
    • Credential-scraping prevention
    • Duplicate detection and merge/precedence policy
    • Partial/degraded/revoked/duplicate state rendering

Commit boundary

  • Commit after each artifact is independently runnable

Round 4 — P1: Frontend and Platform Completion

Entry criteria: Round 3 committed
Exit criteria: frontend uses single API boundary, no direct backend access

Actions

  1. P1 #36 Audit and enforce NEXT_PUBLIC_IW_API_URL as the single frontend API boundary.
  2. P1 #37 Remove production localhost/direct-service fallbacks from apps/web.
  3. P1 #38 Deploy and verify /api/v1/workspace/discovery end-to-end.
  4. P1 #39 Connect /api/v1/marketplace/installations/* to Plugin and MCP activation flows.
  5. P1 #40 Verify RBAC projections use server-resolved identity.
  6. P1 #41 Complete browser Workbench launch and Gateway communication.
  7. P1 #42 Verify frontend never calls DB/provider/Hermes/credentials/MCP Pool directly.

Commit boundary

  • One commit per verified surface

Round 5 — P1: Customer Zero Testing Event

Entry criteria: Round 4 deployed to Customer Zero
Exit criteria: all acceptance tests pass, evidence records produced

Actions

  1. P1 #43–52 Execute clean-install and clean-connect acceptance tests:
    • Clean install Plugin into new tenant
    • Clean connect MCP from compatible client
    • Exactly 19 public tools
    • Cross-tenant/cross-environment denial
    • Host-connected app composition without credential inheritance
    • Duplicate provider connection handling
    • Governed action cycle end-to-end
    • Flow A/B/C/D, idempotency, retries, DLQ, replay, reconciliation, promotion, aging
    • Observability, audit, revocation, rollback, incident handling

Commit boundary

  • Do not include new features; record acceptance results and any bugfix commits

Round 6 — P2: Publication

Entry criteria: Rounds 1–5 complete, acceptance evidence recorded
Exit criteria: publicly listed/connected, monitoring operational

Actions

  1. P2 #53–55 Prepare submission assets and submit to Plugin marketplaces/directories and MCP registries/directories.
  2. P2 #56–58 Build/submit Vercel native package and inbound connector; add any required provider-native packages.
  3. P2 #59 Activate monitoring, support, versioning, rollback, deprecation operations.

Quick-Reference Order

Round 1: P0 contract/code alignment
Round 2: P0 infrastructure/auth
Round 3: P1 Plugin + MCP + discovery
Round 4: P1 frontend/platform completion
Round 5: P1 Customer Zero testing
Round 6: P2 publication