@aion0/forge 0.6.1 → 0.8.0

package/.forge/mcp.json

@@ -3,6 +3,14 @@
     "forge": {
       "type": "sse",
       "url": "http://localhost:8406/sse?workspaceId=656c9e65-9d73-4cb6-a065-60d966e1fc78"
+    },
+    "chrome": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "-y",
+        "chrome-devtools-mcp"
+      ]
     }
   }
 }

package/.forge/worktrees/pipeline-0a33c50d/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-0a33c50d/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-2ba01c10/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-2ba01c10/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-3156a8b3/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-3156a8b3/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-316c6574/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-316c6574/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-44a94121/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-44a94121/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-4dd8dc2d/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-4dd8dc2d/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-d1757a50/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-d1757a50/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-d59c2fe2/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-d59c2fe2/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-d6a6ef23/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-d6a6ef23/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-e7f78b7a/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-e7f78b7a/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-e97c13c7/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-e97c13c7/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/.forge/worktrees/pipeline-ecd7cb0f/lib/help-docs/01-settings.md

@@ -102,14 +102,14 @@ Profiles are reusable configurations that extend a base agent with custom enviro
 
 ```yaml
 agents:
-  forti-k2:
+  forge-k2:
     base: claude
-    name: Forti K2
-    model: forti-k2
+    name: Forge K2
+    model: forge-k2
     env:
       ANTHROPIC_AUTH_TOKEN: sk-xxx
       ANTHROPIC_BASE_URL: http://my-server:7001/
-      ANTHROPIC_SMALL_FAST_MODEL: forti-k2
+      ANTHROPIC_SMALL_FAST_MODEL: forge-k2
       CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC: "true"
       DISABLE_TELEMETRY: "true"
 ```
@@ -142,7 +142,7 @@ In the agent configuration, set the `profile` field to link a profile:
 ```yaml
 agents:
   claude:
-    profile: forti-k2    # Claude will use forti-k2's env/model when launched
+    profile: forge-k2    # Claude will use forge-k2's env/model when launched
 ```
 
 This applies the profile's environment variables and model override whenever that agent is launched in a terminal.

package/.forge/worktrees/pipeline-ecd7cb0f/lib/help-docs/07-projects.md

@@ -61,7 +61,7 @@ There are two ways to open a terminal for a project:
 
 When selecting an agent or profile for a terminal:
 - **Base agents** (Claude, Codex, Aider): Use their default configuration
-- **Profiles** (e.g., Forti K2, Claude Opus): Apply the profile's environment variables and model override
+- **Profiles** (e.g., Forge K2, Claude Opus): Apply the profile's environment variables and model override
 - Environment variables are exported in the terminal before launching the CLI
 - Model is passed via `--model` flag (for claude-code agents)
 

package/CLAUDE.md

@@ -118,9 +118,9 @@ If a feature change affects user-facing behavior, update the corresponding help
 - GitHub: `github.com/aiwatching/forge`
 
 ## Obsidian Vault
-Location: /Users/zliu/MyDocuments/obsidian-project/Projects/Bastion
+Location: ~/Documents/obsidian/MyProject
 When I ask about my notes, use bash to search and read files from this directory.
-Example: find /Users/zliu/MyDocuments/obsidian-project -name "*.md" | head -20
+Example: find ~/Documents/obsidian -name "*.md" | head -20
 
 <!-- forge:template:obsidian-vault -->
 ## Obsidian Vault

package/RELEASE_NOTES.md

@@ -1,11 +1,107 @@
-# Forge v0.6.1
+# Forge v0.8.0
 
-Released: 2026-04-28
+Released: 2026-05-19
 
-## Changes since v0.6.0
+## Changes since v0.6.3
+
+### Features
+- feat: job preview auto-fill + forge worktree CLI + faster startup
+
+### Documentation
+- docs: example pipeline for a Forge Job driving Mantis → branch triage
+- docs: Jobs — scheduled connector polls that fan out to pipelines or chat
+- docs: connector declarative-extract spec + handoff + updated help doc
+- docs: connector packaging section + plugin category ADR
+- docs: ADR for browser-agent data architecture (Temper write strategy)
+- docs: RFC + implementation plan for browser-agent / connector system
 
 ### Other
-- fix(server): daemonize standalones in \`forge server start\` (background)
+- feat(chat): local memory fallback + simplified /chat web page
+- feat(security): encrypt plugin secrets at rest + mask on API
+- feat(pipeline): print fetch-bug-details + download-attachments to task log
+- feat(mantis+pipeline): attachment download into worktree for vision analysis
+- fix(pipeline): push-and-mr detects revoked glab token + prints fix cmd
+- fix(pipeline): push-and-mr surfaces glab output + MR-list fallback
+- feat(pipeline/mantis): fetch-bug-details exposes ALL fields downstream
+- fix(pipeline-ui): fetch full pipeline on click — summary breaks detail view
+- feat(jobs): expose {{total_matching}} placeholder in chat summary mode
+- fix(mantis): regex escape — YAML | block passes backslashes verbatim
+- fix(time): normalize all SQLite datetimes to ISO Z + add settings.timezone
+- feat(jobs/mantis): target='main' chat dispatch + total_matching count
+- fix(mantis): reset all filter fields before applying — no session leak
+- feat(chat): persistent main session + clear-messages + fork
+- feat(jobs): chat 'summary' dispatch mode — bundle N items into 1 LLM analysis
+- perf(pipeline-ui): lazy-load runs per workflow, drop 5s full poll
+- perf(watcher): defer initial sync + skip entry_count on first pass
+- feat(pipeline-ui): 'Load older runs' button per workflow
+- perf(pipeline): default limit 100 + ?workflow / ?before cursor
+- perf(pipeline): mtime cache + summary mode for list — 1.6MB → <50KB
+- perf(init): instrument 5s gap + demote skills sync failure to warn
+- feat(teams): _probe diagnostic tool — DOM state in one call
+- fix(chat): unwrap Node fetch 'fetch failed' with concrete remediation
+- fix(teams): char-by-char typing for search input (keyboard events)
+- feat(teams): v0.8.0 — send_message 3-tier resolver (left-rail → expand groups → search)
+- feat(mantis): v0.4.3 — accurate filters via show_status + handler_id
+- fix(pipeline): real workdir support + worktree-setup emits path only
+- fix(pipeline): node tasks always start fresh Claude session
+- fix(jobs): warn loudly when input_template keys render to empty
+- feat(jobs): 'Force run' — reset dedup + run, one click
+- fix(jobs): drop dedup_key from triggerPipeline — UNIQUE blocked replay
+- feat(gitlab): full HTTP-API connector (32 tools) — replaces DOM scraping
+- fix(mantis): bug notes always carry an id — fallback strategies + hash
+- feat(chat): connector narrowing — /teams forces tool use; bare mention narrows tool list
+- fix(chat): connector tools always surfaced + stronger 'use the tool' prompt
+- fix(notify-test): explain 'fetch failed' (corp SSL / proxy / DNS)
+- fix(notify-test): drop Markdown parse_mode + split chat_id + surface real reason
+- fix(mantis): search_bugs — fix_schedule (version) filter + auto-pagination
+- fix(mantis): search_bugs honours status + project_id, drops broken query syntax
+- feat(health): startup probe + Pipelines banner for missing CLIs (glab/gh/git/jq)
+- feat(pipeline): mantis-bug-fix-and-mr builtin + connector-tool API
+- feat(mantis): notes carry stable note_id so Jobs can dedup on them
+- feat(jobs): per-run verbose execution log persisted to job_runs.log
+- feat(web): Jobs first in Automation, deep-link to logs filtered by job id
+- fix(web): Automation sub-tabs squished header; new sub-toolbar row fix(terminal): Split Right/Down → SVG icons; mouse hint to tooltip feat(jobs): notes column — backfill + items_path mismatch surfaced
+- feat(web): Automation hub — merge Tasks/Pipelines nav + add Jobs view
+- feat(jobs): trace flow — Dashboard deep-link + CLI dispatches view
+- feat(jobs): Jobs backend — scheduled connector polls + dispatch
+- fix(settings): don't overwrite agent apiKey with masked placeholder
+- feat(chat): port Temper memory to Forge — pinned blocks + memory_* tools
+- feat(chat): reuse API agent profiles + add baseUrl (LiteLLM support)
+- feat(bridge): drop pairing — bridge auths with the user's Forge token
+- feat(connectors): Phase 3 — multi-protocol runtime (http, shell)
+- feat(chat): Phase 5 part 3 — Telegram /chat command
+- feat(chat): Phase 5 part 2 — forge chat CLI subcommand
+- feat(chat): Phase 5 part 1 — chat-standalone (8408) + Next proxy
+- fix(bridge): spawn browser-bridge from lib/init.ts too
+- feat(chat): Phase 2 part 3 — HTTP API + WS push streaming
+- feat(chat): Phase 2 part 2 — tool dispatcher + agent loop
+- feat(chat): Phase 2 part 1 — chat backend foundation
+- feat(bridge): Phase 1 — Forge↔Extension WebSocket bridge
+- feat(connectors): teams v0.7.1 — send_message no longer requires confirmation
+- feat(connectors): teams v0.7.0 — robust wait + send_message by name
+- feat(connectors): teams v0.6.0 — read_chat + read_channel by name
+- feat(connectors): teams v0.5.0 — channels support (list + read posts)
+- feat(connectors): pmdb v0.2.0 — read-only Fortinet PMDB connector
+- feat(connectors): teams v0.4.0 — send_message (destructive)
+- feat(connectors): teams v0.3.0 — rewritten from real DOM probe
+- feat(connectors): multi-runner — manifest declares execution context
+- feat(connectors): teams (Microsoft Teams) — first-cut declarative manifest
+- chore(connectors): bump gitlab to 0.2.0
+- feat(connectors): gitlab — declarative manifest with 6 tools
+- feat(connectors): declarative extract — manifest carries page + script
+- chore(connectors): bump mantis to 0.2.0 — full tool set landed
+- feat(mcp): user-managed external MCP servers in .mcp.json
+- feat(connectors): mantis probe — auto-copy JSON result to clipboard
+- fix(connectors): mantis probe — support 1.x classic URL + checkbox row marker
+- feat(connectors): mantis selector probe sibling script
+- chore(connectors): bump mantis + gitlab-browser to 0.1.1
+- docs(connectors): DOM extraction is the default path, not REST APIs
+- feat(ui): dedicated Connectors panel separate from Plugins
+- fix(connectors-api): rely on middleware auth, drop explicit token check
+- feat(api): connectors discovery + per-user settings endpoints
+- feat(plugins): connector category + browser-side mode, mantis + gitlab manifests
+- feat(gitlab): \`gitlab-issue-fix-and-review\` pipeline + scanner
+- fix(mcp): mirror .forge/mcp.json to project root so claude picks it up
 
 
-**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.6.0...v0.6.1
+**Full Changelog**: https://github.com/aiwatching/forge/compare/v0.6.3...v0.8.0

package/app/api/auth/check/route.ts

@@ -0,0 +1,18 @@
+/**
+ * POST /api/auth/check — validate an X-Forge-Token.
+ *
+ * Used by other Forge processes (e.g. bridge-standalone) to verify a
+ * token without re-implementing the token store. Returns 200 on valid,
+ * 401 otherwise. Body is ignored — the token must be in the
+ * X-Forge-Token header (or forge-api-token cookie).
+ */
+
+import { NextResponse } from 'next/server';
+import { isValidToken } from '../verify/route';
+
+export async function POST(req: Request) {
+  if (!isValidToken(req)) {
+    return NextResponse.json({ ok: false }, { status: 401 });
+  }
+  return NextResponse.json({ ok: true });
+}