@entelligentsia/forgecli 0.6.6 → 0.7.7

package/workflows/lead-qualifier/prompts/mark-cold.md

@@ -0,0 +1,38 @@
+# Role
+You are the `mark-cold` node. You run for leads with score < 4.
+You record a brief disposition note and tag the outcome as cold.
+
+# Inputs
+- Lead (with score and enrichment):
+{{loop.item}}
+
+# Your remit
+Write a 1-sentence rationale for why this lead is being deprioritized (e.g. "Industry
+mismatch", "Headcount too small", "Tech stack misalignment"). Set
+`leads.{{loop.item.id}}.outcome` to `{ "status": "cold", "rationale": "<one sentence>" }`.
+
+# Output protocol (MANDATORY)
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Marked {{loop.item.id}} cold",
+    "writes": {
+      "state": {
+        "leads.{{loop.item.id}}.outcome": { "status": "cold", "rationale": "..." }
+      }
+    }
+  }
+]
+```
+
+On failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-disposition", "details": "<why>" }
+]
+```

package/workflows/lead-qualifier/prompts/score.md

@@ -0,0 +1,45 @@
+# Role
+You are the `score` node of the per-lead pipeline.
+You assign a single integer fit score 1–5 to ONE lead.
+
+# Inputs
+- ICP / target description (from intake): see `state.entryPrompt`
+- Current lead (with enrichment already applied):
+{{loop.item}}
+
+# Your remit
+Score the lead's fit on a 1–5 integer scale:
+- 5 = ideal-fit, prioritize immediately
+- 4 = strong-fit, worth outreach
+- 3 = marginal, might warm up later
+- 2 = poor-fit
+- 1 = exclude
+
+The number MUST be a plain integer at `loop.item.score`. Downstream branching depends on
+this exact path. Do not nest it inside an object.
+
+# Output protocol (MANDATORY)
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Scored {{loop.item.id}} = <N>",
+    "writes": {
+      "state": {
+        "leads.{{loop.item.id}}.score": 4
+      }
+    }
+  }
+]
+```
+
+On failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-score", "details": "<why>" }
+]
+```

package/workflows/lead-qualifier/workflow.yaml

@@ -0,0 +1,95 @@
+id: lead-qualifier
+version: 1
+description: >
+  Per-lead pipeline demo. For each lead in state.leads: enrich → score → branch on score
+  (>=4: draft outreach; else: mark cold) → next lead. Final digest summarizes the cohort.
+  Exercises: (a) `loop.group` per-item pipeline, (b) `when:` conditional edges.
+
+nodes:
+  - id: intake
+    prompt: prompts/intake.md
+    expects:
+      success:
+        writes:
+          state: [leads]
+      failure: {}
+
+  - id: enrich
+    prompt: prompts/enrich.md
+    loop:
+      over:  leads
+      alias: loop.item
+      group: per-lead
+      head:  true
+    expects:
+      success:
+        writes:
+          state: ["leads.{loop.item.id}.enriched"]
+      failure: {}
+
+  - id: score
+    prompt: prompts/score.md
+    loop:
+      over:  leads
+      alias: loop.item
+      group: per-lead
+    expects:
+      success:
+        writes:
+          state: ["leads.{loop.item.id}.score"]
+      failure: {}
+
+  - id: draft-outreach
+    prompt: prompts/draft-outreach.md
+    loop:
+      over:  leads
+      alias: loop.item
+      group: per-lead
+    expects:
+      success:
+        writes:
+          artifact: { pattern: "artifacts/outreach/{loop.item.id}.md" }
+          state:    ["leads.{loop.item.id}.outcome"]
+      failure: {}
+
+  - id: mark-cold
+    prompt: prompts/mark-cold.md
+    loop:
+      over:  leads
+      alias: loop.item
+      group: per-lead
+    expects:
+      success:
+        writes:
+          state: ["leads.{loop.item.id}.outcome"]
+      failure: {}
+
+  - id: digest
+    prompt: prompts/digest.md
+    expects:
+      success:
+        writes:
+          artifact: { pattern: "artifacts/BRIEF.md" }
+      failure: {}
+
+edges:
+  - { from: intake,         on: success,    to: enrich }
+  - { from: intake,         on: failure,    halt: intake-failed }
+
+  - { from: enrich,         on: success,    to: score }
+  - { from: enrich,         on: failure,    advance: loop-or-next }
+  - { from: enrich,         on: exhausted,  to: digest }
+
+  # Conditional: warm leads (score >= 4) get an outreach draft; everyone else is marked cold.
+  - { from: score,          on: success,    when: "loop.item.score >= 4", to: draft-outreach }
+  - { from: score,          on: success,    to: mark-cold }
+  - { from: score,          on: failure,    advance: loop-or-next }
+
+  - { from: draft-outreach, on: success,    advance: loop-or-next }
+  - { from: draft-outreach, on: failure,    advance: loop-or-next }
+
+  - { from: mark-cold,      on: success,    advance: loop-or-next }
+  - { from: mark-cold,      on: failure,    advance: loop-or-next }
+
+  - { from: digest,         on: success,    terminal: complete }
+  - { from: digest,         on: failure,    halt: digest-failed }

package/workflows/research-brief/prompts/brief-synthesize.md

@@ -0,0 +1,43 @@
+# Role
+You are the `brief-synthesize` node — produce the final research brief.
+
+# Inputs
+- Original question: state.entryPrompt
+- Full state JSON:
+{{state}}
+
+# Your remit
+Read every source's summary (artifacts/sources/*.summary.md), its score, and its critique.
+Produce `artifacts/BRIEF.md` — a single document with:
+
+- TL;DR (3–5 sentences)
+- Findings (grouped, with inline source citations using the source ids)
+- Open questions (from the critiques)
+- Sources table (id, title, kind, score)
+
+# Output protocol (MANDATORY)
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Brief written",
+    "writes": {
+      "artifact": {
+        "path": "artifacts/BRIEF.md",
+        "content": "# Research Brief\n\n## TL;DR\n...\n\n## Findings\n...\n\n## Open Questions\n...\n\n## Sources\n| id | title | kind | score |\n|---|---|---|---|\n..."
+      }
+    }
+  }
+]
+```
+
+On failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-synthesize", "details": "<why>" }
+]
+```

package/workflows/research-brief/prompts/intake.md

@@ -0,0 +1,51 @@
+# Role
+You are the `intake` node of the `research-brief` workflow.
+
+# Inputs
+- Workflow instance: {{wf.instanceId}}
+- Working directory: {{wf.workingDir}}
+- Your node exec id: {{node.execId}}
+- Current state JSON:
+{{state}}
+
+# Your remit
+Read `state.entryPrompt` (the user's research question). Identify 2 to 4 plausible
+information sources that would help answer it. For each source, produce:
+- `id`: a short kebab-case identifier (e.g. "rfc-9001", "nist-pqc-report")
+- `url`: a real or representative URL
+- `title`: human-readable title
+- `kind`: one of "spec" / "paper" / "report" / "blog" / "doc"
+
+# Output protocol (MANDATORY)
+End your reply with a fenced ```json events block. The engine parses ONLY this block.
+Exactly two events: `started`, then `success` (or `failure` if the prompt is unintelligible).
+
+Example success:
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Identified 3 sources for post-quantum crypto adoption",
+    "writes": {
+      "state": {
+        "sources": [
+          { "id": "nist-pqc",   "url": "https://csrc.nist.gov/projects/post-quantum-cryptography", "title": "NIST PQC Project", "kind": "report" },
+          { "id": "rfc-9180",   "url": "https://www.rfc-editor.org/rfc/rfc9180", "title": "RFC 9180 (HPKE)", "kind": "spec" },
+          { "id": "cloudflare-pq", "url": "https://blog.cloudflare.com/pq-2024/", "title": "Cloudflare PQ rollout 2024", "kind": "blog" }
+        ]
+      }
+    }
+  }
+]
+```
+
+Example failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "unintelligible-prompt", "details": "entryPrompt was empty or not parseable as a research question" }
+]
+```

package/workflows/research-brief/prompts/source-critique.md

@@ -0,0 +1,38 @@
+# Role
+You are the `source-critique` node — identify gaps, biases, or follow-up questions for one source.
+
+# Inputs
+- Source (loop item):
+{{loop.item}}
+
+# Your remit
+Produce a short critique (1–3 bullets) and 1–2 follow-up questions.
+
+# Output protocol (MANDATORY)
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Critiqued {{loop.item.id}}",
+    "writes": {
+      "state": {
+        "sources.{{loop.item.id}}.critique": {
+          "concerns": ["..."],
+          "followUps": ["..."]
+        }
+      }
+    }
+  }
+]
+```
+
+On failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-critique", "details": "<why>" }
+]
+```

package/workflows/research-brief/prompts/source-score.md

@@ -0,0 +1,38 @@
+# Role
+You are the `source-score` node — assign quality scores to one source.
+
+# Inputs
+- Source (loop item):
+{{loop.item}}
+
+# Your remit
+Score the source on three axes, each 1–5:
+- `relevance`: how directly relevant to the research question (state.entryPrompt)
+- `recency`: how recent / current the source is
+- `authority`: how authoritative the source is
+
+# Output protocol (MANDATORY)
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Scored {{loop.item.id}}",
+    "writes": {
+      "state": {
+        "sources.{{loop.item.id}}.score": { "relevance": 5, "recency": 4, "authority": 5 }
+      }
+    }
+  }
+]
+```
+
+On failure:
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-score", "details": "<why>" }
+]
+```

package/workflows/research-brief/prompts/source-summarize.md

@@ -0,0 +1,54 @@
+# Role
+You are the `source-summarize` node of the `research-brief` workflow, executing for one source.
+
+# Inputs
+- Workflow instance: {{wf.instanceId}}
+- Your node exec id: {{node.execId}}
+- Current source (loop item):
+{{loop.item}}
+
+# Your remit
+Produce a structured summary of the source identified by `loop.item.url` / `loop.item.title`.
+You do not need to actually fetch the URL — write a plausible summary based on the title
+and what such a source typically contains. The summary should include:
+
+- thesis: ≤200 chars
+- key-claims: 3–7 bullet points
+- methodology: 1–3 sentences
+- limitations: 1–3 sentences
+
+# Output protocol (MANDATORY)
+End your reply with a fenced ```json events block. Exactly two events: `started`, then
+`success` carrying both the artifact (the full markdown summary) and a state write.
+
+The artifact path MUST be exactly `artifacts/sources/{{loop.item.id}}.summary.md`.
+
+Example:
+
+```json events
+[
+  { "type": "started" },
+  {
+    "type": "success",
+    "summary": "Summarized {{loop.item.id}}",
+    "writes": {
+      "artifact": {
+        "path": "artifacts/sources/{{loop.item.id}}.summary.md",
+        "content": "# Summary: <title>\n\n## Thesis\n...\n\n## Key Claims\n- ...\n\n## Methodology\n...\n\n## Limitations\n...\n"
+      },
+      "state": {
+        "sources.{{loop.item.id}}.summarized": true
+      }
+    }
+  }
+]
+```
+
+If you cannot summarize (e.g. source kind is unknown):
+
+```json events
+[
+  { "type": "started" },
+  { "type": "failure", "reason": "cannot-summarize", "details": "<why>" }
+]
+```

package/workflows/research-brief/workflow.yaml

@@ -0,0 +1,66 @@
+id: research-brief
+version: 1
+description: Multi-source research brief synthesis — 5-node PoC with 3 loop-body nodes.
+
+nodes:
+  - id: intake
+    prompt: prompts/intake.md
+    expects:
+      success:
+        writes:
+          state: [sources]
+      failure: {}
+
+  - id: source-summarize
+    prompt: prompts/source-summarize.md
+    loop:
+      over:  sources
+      alias: loop.item
+    expects:
+      success:
+        writes:
+          artifact: { pattern: "artifacts/sources/{loop.item.id}.summary.md" }
+          state:    ["sources.{loop.item.id}.summarized"]
+      failure: {}
+
+  - id: source-score
+    prompt: prompts/source-score.md
+    loop:
+      over:  sources
+      alias: loop.item
+    expects:
+      success:
+        writes:
+          state: ["sources.{loop.item.id}.score"]
+      failure: {}
+
+  - id: source-critique
+    prompt: prompts/source-critique.md
+    loop:
+      over:  sources
+      alias: loop.item
+    expects:
+      success:
+        writes:
+          state: ["sources.{loop.item.id}.critique"]
+      failure: {}
+
+  - id: brief-synthesize
+    prompt: prompts/brief-synthesize.md
+    expects:
+      success:
+        writes:
+          artifact: { pattern: "artifacts/BRIEF.md" }
+      failure: {}
+
+edges:
+  - { from: intake,           on: success, to: source-summarize }
+  - { from: intake,           on: failure, halt: intake-failed }
+  - { from: source-summarize, on: success, advance: loop-or-next, next: source-score }
+  - { from: source-summarize, on: failure, halt: source-summarize-failed }
+  - { from: source-score,     on: success, advance: loop-or-next, next: source-critique }
+  - { from: source-score,     on: failure, halt: source-score-failed }
+  - { from: source-critique,  on: success, advance: loop-or-next, next: brief-synthesize }
+  - { from: source-critique,  on: failure, halt: source-critique-failed }
+  - { from: brief-synthesize, on: success, terminal: complete }
+  - { from: brief-synthesize, on: failure, halt: brief-failed }

package/dist/extensions/forgecli/session-monitor-widget.d.ts

@@ -1,37 +0,0 @@
-import type { Component } from "@entelligentsia/pi-tui";
-import type { Theme } from "@entelligentsia/pi-coding-agent";
-interface WidgetDeps {
-    theme: Theme;
-    requestRender: () => void;
-    onClose: () => void;
-    /** Called once after the widget instance is constructed. The session-monitor
-     * controller uses this to capture a reference for onTerminalInput routing. */
-    onMount?: (widget: SessionMonitorWidget) => void;
-}
-/**
- * Build the widget factory expected by ctx.ui.setWidget.
- * The factory captures dependencies (theme, render hook, close hook) and
- * returns a fresh Component on each setWidget() call.
- */
-export declare function buildSessionMonitorWidget(deps: Omit<WidgetDeps, "theme">): (tui: unknown, theme: Theme) => Component & {
-    dispose?(): void;
-};
-export declare class SessionMonitorWidget implements Component {
-    private registry;
-    private listener;
-    private focusedPane;
-    private selectedTaskId?;
-    private selectedEventIndex;
-    private sessionsList;
-    private eventsList;
-    private deps;
-    private disposed;
-    constructor(deps: WidgetDeps);
-    dispose(): void;
-    invalidate(): void;
-    handleInput(data: string): void;
-    render(width: number): string[];
-    private refreshSessions;
-    private rebuildEvents;
-}
-export {};