@lambdacurry/review-signals

Workflow-first CLI for Review Signals' durable control plane. It runs under Bun 1.3.1+ and Node/npm.

Use @latest together with Bun's --no-cache --force flags so every invocation refreshes registry metadata and reinstalls the selected executable instead of trusting a stale shared-cache entry. Verify the selected binary with bunx --no-cache --force @lambdacurry/review-signals@latest --version.

Start with:

bunx --no-cache --force @lambdacurry/review-signals@latest workflows help --json
bunx --no-cache --force @lambdacurry/review-signals@latest workflows list --json
bunx --no-cache --force @lambdacurry/review-signals@latest workflows show <workflow-id> --json

Read-only, code-owned workflows define required work and expose prose guidance about relevant command areas. Exact commands and options are discovered from live CLI help at runtime. Source groups are reusable collection briefs with immutable IDs, mutable keys, detailed instructions, enabled state, and independent pull freshness. Start with source-groups guidance --json when authoring one. Source identity is global by source type and external ID; associating an existing source with another source group adds provenance rather than changing ownership.

Goals use one durable lifecycle: proposed, approved, dismissed, or archived. goals list returns approved goals by default; use --status and --source-group to inspect proposal history. Goal-discovery workflows create proposals with source-group and origin-run provenance. Human review uses goals approve, goals dismiss, goals archive, and goals activate. New signals may reference approved goals only.

Before authoring or updating durable fields, load the selected code-owned workflow and follow its embedded template. Goal, signal, and recommendation detail output includes chronological append-only history; lifecycle history belongs there, not in mutable descriptions or bodies.

The CLI stores stable source identity, source-group provenance, signals, recommendations, goals, and execution outcomes. Command execution tracking is automatic and internal; agents use the main domain commands and inspect status --json for failed or interrupted attempts. Interrupted attempts have an unknown outcome and require durable-state verification before retrying. Agents fetch current source content at least once per relevant workflow; raw content and transient snapshots are not stored. A successful source-group pull advances only that group's last_successful_pull_at; failed and blocked pulls do not.

Use npx @lambdacurry/review-signals@latest when Bun is unavailable. Use --env-file <path> to explicitly load one environment file; process variables win. .env* files are read-only, and connection failures must not trigger a database fallback.