Files

Fusion 0c241b017f feat(FN-2855): route scheduled tasks using effective node resolution

- Add an effective node resolver with task override, project default, and local fallback precedence.
- Wire scheduler dispatch to persist effectiveNodeId/effectiveNodeSource and log resolved node routing.
- Add coverage for effective node resolution and scheduler node routing integration behavior.
- Stabilize workspace test resolution by adding @fusion/core and @fusion/plugin-sdk aliases across Vitest configs.

2026-04-28 14:25:55 -07:00

src

feat(FN-1916): add plugin UI slots system for extensibility

2026-04-16 10:48:57 -07:00

CHANGELOG.md

chore(release): v0.7.1

2026-04-28 00:36:24 -07:00

package.json

chore(release): v0.7.1

2026-04-28 00:36:24 -07:00

README.md

feat(FN-1114): merge fusion/fn-1114 (auto-resolved)

2026-04-09 19:04:12 -07:00

tsconfig.json

feat(FN-1114): merge fusion/fn-1114 (auto-resolved)

2026-04-09 19:04:12 -07:00

vitest.config.ts

feat(FN-2855): route scheduled tasks using effective node resolution

2026-04-28 14:25:55 -07:00

README.md

CI Status Plugin

Polls CI status for branches and provides a custom API to query results. Useful for tracking the build status of feature branches created for Fusion tasks.

Features

Branch Tracking: Automatically tracks branches when tasks move to in-progress
Periodic Polling: Polls CI status at configurable intervals
Custom API: Provides REST endpoints to query branch status
Automatic Cleanup: Stops tracking branches when tasks are completed

Installation

Option 1: Copy to plugins directory

cp -r fusion-plugin-ci-status ~/.fusion/plugins/

Option 2: Install via CLI

fn plugin install /path/to/fusion-plugin-ci-status

Configuration

Settings Reference

Field	Type	Required	Default	Description
`ciUrl`	string	Yes	—	Base URL for CI API
`pollIntervalMs`	number	No	`30000`	How often to poll CI status (milliseconds)
`branchPrefix`	string	No	`fusion/`	Only poll branches with this prefix

API Endpoints

The plugin provides the following REST endpoints at /api/plugins/fusion-plugin-ci-status:

GET /status

Returns status of all tracked branches.

{
  "branches": [
    {
      "branch": "fusion/fn-001",
      "status": "pending",
      "lastChecked": "2024-01-01T00:00:00.000Z",
      "url": "https://ci.example.com/builds/123"
    }
  ]
}

GET /status/:branch

Returns status of a specific branch.

{
  "branch": "fusion/fn-001",
  "status": "success",
  "lastChecked": "2024-01-01T00:00:00.000Z",
  "url": "https://ci.example.com/builds/123"
}

If the branch is not found, returns a 404 error.

POST /refresh

Triggers an immediate CI status refresh for all tracked branches.

{
  "branches": [...],
  "refreshed": true
}

How It Works

Branch Creation: When a task moves to "in-progress", the plugin creates a branch name using the configured prefix (default: fusion/) combined with the task ID (lowercased)
CI Polling: At the configured interval, the plugin polls the CI API to get status updates for all tracked branches
CI Integration: The plugin sends a POST request to {ciUrl}/status with the list of branch names
Branch Cleanup: When a task moves to "done" or "archived", the branch is removed from tracking

CI API Integration

The plugin expects your CI system to expose a /status endpoint that accepts:

{
  "branches": ["fusion/fn-001", "fusion/fn-002"]
}

And returns:

{
  "statuses": [
    {
      "branch": "fusion/fn-001",
      "status": "success",
      "url": "https://ci.example.com/builds/123"
    }
  ]
}

Supported Status Values

pending — Initial state when branch is first tracked
running — CI is building
success — CI passed
failed — CI failed
cancelled — CI was cancelled

Development

# Install dependencies
pnpm install

# Run tests
pnpm test

# Build
pnpm build

License

MIT