mirror of
https://github.com/ruvnet/ruflo.git
synced 2026-09-14 14:01:28 +08:00
402b701a9d
* fix(security): ADR-165 Phase 1 — close all critical CVEs, refresh registry, add CI gate Closes ADR-165 Phase 1. Both workspaces pass `npm audit --audit-level=critical`. ## Before (2026-06-29) | Workspace | Critical | High | Moderate | Total | |-----------|----------|------|----------|-------| | Root | **1** | 6 | 31 | 38 | | v3 | **4** | 33 | 57 | 97 | ## After | Workspace | Critical | High | Moderate | Total | |-----------|----------|------|----------|-------| | Root | **0** | 0 | 31 | 31 | | v3 | **0** | 27 | 58 | 88 | All 5 critical advisories closed (vitest GHSA-5xrq, handlebars prototype-pollution, protobufjs constructor-pollution, plus 2 more in v3). 12 of 39 high advisories closed via overrides; the remaining 27 v3 highs are deeper transitive chains that would require breaking-change major bumps — flagged for ADR-165 Phase 2. ## Changes ### Root workspace overrides (package.json) - `vitest`: `^1.0.0` → `^3.2.6` (closes critical GHSA-5xrq CVSS 9.8) - `hono`: `>=4.11.4` → `>=4.12.25` (closes 6 hono advisories) - `undici`: `>=7.18.0` → `>=8.5.0` (closes 7 undici advisories — bumps the stale pin that ADR-165 flagged as still-in-vulnerable-range) - `vite`: `>=6.4.6` → `>=8.0.16` (closes 2 vite advisories) - NEW `@grpc/grpc-js`: `>=1.14.4` - NEW `form-data`: `>=4.0.6` - NEW `http-proxy-middleware`: `>=3.0.7` - `@hono/node-server`: `>=1.19.10` → `>=1.19.14` ### v3 workspace overrides (v3/package.json + pnpm.overrides) - `vitest`: `^4.0.16` → `^4.1.0` (and `@vitest/coverage-v8` matched) - Top-level + pnpm overrides: `handlebars: >=4.7.9`, `protobufjs: >=8.6.0` - 27 sub-package `package.json` updated to `vitest ^4.1.0` ### CVE registry refresh (v3/@claude-flow/security/src/CVE-REMEDIATION.ts) Rewritten from 5 stale Jan-2026 entries to 16 total: 15 fixed, 1 open (ADR165-OPEN-01 — PII pipeline wiring per ADR-164 §6.1 not yet on dispatch-layer). `SECURITY_SUMMARY` is now computed dynamically from the registry; `validateRemediation()` correctly returns `allFixed: false` with 1 issue. ADR-165 §5 flagged this as THE Phase 2 priority — now closed. ### New CI gate `.github/workflows/cve-audit.yml`: - `audit-root` — `npm audit --audit-level=critical` in root, blocking - `audit-v3` — same in v3, blocking - `audit-high-report` — warn-only summary on high-severity drift - Triggers: PR, push to main, daily cron ### ADR-165 §9 evidence ledger addendum Captures AFTER-remediation `npm audit --json` metadata for both workspaces. The diff between BEFORE (already in §9) and AFTER makes Phase 1 verifiable. Also CORRECTED one prior surprise in §9: the `validate-input.ts` in `mcp-tools/` is NOT a 9-line shim. It's 269 lines of real implementation. (That was an inaccurate findings note from the initial audit.) ### §7.3 research items resolved - `protobufjs` v3 chain confirmed gone after override pins - `handlebars` v3 chain confirmed not user-reachable on the workflow path (toolchain-only; override sufficient) - `validate-input.ts` confirmed real implementation, not a shim (registry entry corrected) - CORS surface check: no `cors()` / `app.use(cors` call sites — the hono CORS-wildcard advisory is not exploitable on the current server - ADR-164 §6.1 PII pipeline NOT wired in current agentbbs dispatch — recorded as ADR165-OPEN-01 (Phase 3 work) ## Gates (all PASS) - `npm audit --audit-level=critical` root: exit 0 (was non-zero) - `npm audit --audit-level=critical` v3: exit 0 (was non-zero) - vitest suites: 105/109 pass (4 skip-conditional — same as before) - ADR-112 audit: 352/352 tools with guidance - business-pods smoke: 11/11 PASS - agentbbs smoke: 8/8 PASS - agenticow smoke: 8/8 PASS - cli build: clean (tsc) ## Phase 2+ deferred The 27 v3 high-severity advisories that remain are transitive chains with no patched-in-range version. ADR-165 §6 Phase 2 picks these up after the `cve-watch.yml` automation in §6 lands (NEW PR — not in scope here). Co-Authored-By: RuFlo <ruv@ruv.net> Claude-Session: https://claude.ai/code/session_01WbBa4nccx5aGhXphoHxcni * chore(lock): regen v3/pnpm-lock.yaml after override updates (PR #2508 CI fix) PR #2508 added handlebars + protobufjs to v3 overrides + bumped vitest pin, but v3/pnpm-lock.yaml wasn't regenerated. CI surfaced ERR_PNPM_LOCKFILE_CONFIG_MISMATCH on every install step. Same pattern as the previous lockfile-drift fixes on PR #2500 and #2503. * fix(ci): cve-audit.yml jq-only + regen witness manifests for #1609 marker drift Two PR #2508 CI failures fixed: 1. Static-regression-guard tripped on cve-audit.yml line 52: the static YAML strict-parser sees `if high > 0:` inside the `run: |` block as a YAML block-mapping key indicator. Refactored all 3 inline-python blocks to use jq (preinstalled on ubuntu-latest) — no embedded `if x > 0:` lines, so the YAML guard passes. 2. Witness marker drift smoke flagged fix-marker #1609 — the Phase 1 vitest bump (4.0.16 → 4.1.0) drifted the cited marker string in v3/@claude-flow/aidefence/package.json. Updated `marker` field in all 3 platform manifests + `desc` to reference ADR-165 Phase 1, then re-signed via plugins/ruflo-core/scripts/witness/regen.mjs. Co-Authored-By: RuFlo <ruv@ruv.net>
@claude-flow/claims
Issue claiming and work coordination for human-agent collaboration.
What is this?
This package provides a complete system for coordinating work between humans and AI agents:
- Issue Claiming - Claim issues to work on, preventing conflicts
- Handoffs - Transfer work between humans and agents seamlessly
- Work Stealing - Automatically reassign stalled work
- Load Balancing - Distribute work evenly across agents
Installation
npm install @claude-flow/claims
Or install via Claude Flow CLI:
npx claude-flow plugins install @claude-flow/claims
Quick Start
Claim an Issue
import { ClaimsService } from '@claude-flow/claims';
const claims = new ClaimsService();
// Human claims an issue
await claims.claim({
issueId: 'ISSUE-123',
claimant: 'human:alice',
context: 'Working on the authentication fix'
});
// Agent claims an issue
await claims.claim({
issueId: 'ISSUE-456',
claimant: 'agent:coder-1:coder',
context: 'Implementing new feature'
});
Release a Claim
await claims.release({
issueId: 'ISSUE-123',
claimant: 'human:alice',
reason: 'Completed the work'
});
Handoff Between Human and Agent
// Human hands off to agent
await claims.handoff({
issueId: 'ISSUE-123',
from: 'human:alice',
to: 'agent:coder-1:coder',
reason: 'Need AI to continue implementation',
progress: 40
});
// Agent accepts handoff
await claims.acceptHandoff({
issueId: 'ISSUE-123',
claimant: 'agent:coder-1:coder'
});
Update Claim Status
await claims.updateStatus({
issueId: 'ISSUE-123',
status: 'review-requested',
progress: 80,
note: 'Ready for code review'
});
MCP Tools (17 Tools)
Core Claiming (7 tools)
| Tool | Description |
|---|---|
claims_claim |
Claim an issue for work |
claims_release |
Release a claimed issue |
claims_handoff |
Request handoff to another claimant |
claims_accept-handoff |
Accept a pending handoff |
claims_status |
Update claim status |
claims_list |
List claims by criteria |
claims_board |
Visual board view of all claims |
Work Stealing (4 tools)
| Tool | Description |
|---|---|
claims_mark-stealable |
Mark issue as available for stealing |
claims_steal |
Steal a stealable issue |
claims_stealable |
List all stealable issues |
claims_contest-steal |
Contest a steal attempt |
Load Balancing (3 tools)
| Tool | Description |
|---|---|
claims_load |
Get agent load information |
claims_rebalance |
Suggest or apply load rebalancing |
claims_swarm-overview |
Overview of swarm workload |
Additional (3 tools)
| Tool | Description |
|---|---|
claims_history |
Get claim history for an issue |
claims_metrics |
Get claiming metrics |
claims_config |
Get/set claims configuration |
Claim Statuses
| Status | Description |
|---|---|
active |
Currently being worked on |
paused |
Temporarily paused |
blocked |
Blocked by external dependency |
review-requested |
Ready for review |
handoff-pending |
Handoff requested, awaiting acceptance |
stealable |
Available for other agents to take |
completed |
Work finished |
Work Stealing
When work stalls, issues can be marked as stealable:
// Mark issue as stealable
await claims.markStealable({
issueId: 'ISSUE-123',
reason: 'overloaded',
preferredTypes: ['coder', 'reviewer'],
context: 'Need someone to continue the implementation'
});
// Another agent steals the issue
await claims.steal({
issueId: 'ISSUE-123',
stealer: 'agent:coder-2:coder'
});
Steal Reasons
timeout- Work has been idle too longoverloaded- Current owner has too much workblocked- Work is blocked and owner can't proceedvoluntary- Owner voluntarily releasingrebalancing- System rebalancing workloadabandoned- Owner is no longer available
Load Balancing
Automatically distribute work across agents:
// Get current agent loads
const loads = await claims.getAgentLoads();
// Preview rebalancing suggestions
const suggestions = await claims.rebalance({ dryRun: true });
// Apply rebalancing
await claims.rebalance({
dryRun: false,
targetUtilization: 0.7
});
Event Sourcing
All claim operations are event-sourced (ADR-007):
// Events emitted
- ClaimCreated
- ClaimReleased
- ClaimStatusUpdated
- HandoffRequested
- HandoffAccepted
- HandoffRejected
- ClaimMarkedStealable
- ClaimStolen
- ClaimContested
CLI Commands
# Claim an issue
npx claude-flow claims claim --issue ISSUE-123 --claimant "human:alice"
# Release a claim
npx claude-flow claims release --issue ISSUE-123
# View claims board
npx claude-flow claims board
# List stealable issues
npx claude-flow claims stealable
# Rebalance workload
npx claude-flow claims rebalance --dry-run
Configuration
# claude-flow.config.yaml
claims:
autoExpiration:
enabled: true
idleTimeout: 3600000 # 1 hour
checkInterval: 300000 # 5 minutes
workStealing:
enabled: true
contestWindow: 30000 # 30 seconds
loadBalancing:
targetUtilization: 0.7
maxIssuesPerAgent: 5
License
MIT