@moretea-labs/forge 1.7.0 → 1.7.2

package/AGENTS.md

@@ -43,6 +43,8 @@ Treat ChatGPT as the controller and Forge as its repository execution layer. Cha
 
 ## Operating Rules
 
+- Default to end-to-end execution and minimize avoidable human intervention. Continue through reversible, policy-allowed setup, implementation, verification, cleanup, and delivery steps without asking the user to babysit the workflow; stop only at a genuinely user-only identity, legal/contract, financial authorization, strong-confirmation, or irreversible decision boundary.
+- For authenticated browser work, preserve the user's existing browser identity: reuse the already-running signed-in Google Chrome via attach-preferred, native-auto, Chrome-only, fail-closed routing. Preserve its cookies, tokens, sessions, and settings; never silently launch or switch to a managed, isolated, Vivaldi, or otherwise unauthenticated browser/profile. Managed or isolated browser modes require an explicit task/action request. If the user Chrome cannot be attached safely, fail closed and surface the concrete blocker instead of creating a replacement login state.
 - After a managed repository change is verified and committed/merged, push the delivered target branch to its configured remote promptly. Do not leave a successfully delivered commit only on local refs unless the user explicitly requested local-only delivery or the push is blocked by safety, permissions, authentication, or branch policy; surface the exact blocker when a push cannot complete.
 - Treat the Google Cloud `forge-cloud` VM experiment as retired infrastructure. Do not restart or reuse that VM for Forge Cloud. Any future remote Forge maintainer must use a separately evaluated host/transport and must demonstrate better latency and reliability than the local Forge path before adoption.
 - Sync `tasks/` whenever substantive repo changes are made.

package/CHANGELOG.md

@@ -4,6 +4,32 @@ All notable public Forge changes are recorded here. Release entries are tied to
 
 ## Unreleased
 
+## 1.7.2 - 2026-08-30
+
+### Runtime lifecycle reliability
+
+- Restart an already-active Linux/systemd Runtime after immutable package activation so the running process cannot remain fenced behind a newer release-authority revision.
+- Avoid duplicate systemd process-group shutdown signals from the package launcher, allowing controlled Runtime restarts to terminate cleanly.
+
+### Work and Controller authority
+
+- Promote effect Work to repository-change authority before governed source mutation and add narrowly fenced reconciliation for already-delivered historical effect Work.
+- Preserve authenticated explicit Controller session capability across MCP transport rotation while keeping same-principal conversations isolated.
+- Make the Windows worker-stderr path assertion platform-correct without changing production path behavior.
+
+## 1.7.1 - 2026-08-30
+
+### Runtime and lifecycle stabilization
+
+- Prevent effect-only Work from losing repository source deltas during finalization, and recognize successful trusted Work-bound `git push` Process receipts as remote-effect completion authority.
+- Harden controller continuation and terminalization across MCP/session rollover while keeping unrelated conversations isolated, and add stable Requirement-backed business-goal identity so stale continuation cannot silently revive superseded goals.
+- Add bounded post-deadline external Codex claim settlement plus precise Work checkout-mismatch diagnostics, preserving fail-closed fencing without false launcher timeouts.
+
+### Browser and release closure
+
+- Converge Browser/desktop automation on the signed Forge Desktop Operator boundary, retain Runtime packaging for the browser handoff host, and close historical capability/permission drift without granting privileged macOS access to Runtime.
+- Re-run the full main, MCP compatibility, package, public-surface, open-source, tarball-install, Runtime Recovery, schedule, and tool-surface release contracts before publication.
+
 ## 1.7.0 - 2026-08-27
 
 ### Persistent autonomous control

package/CLAUDE.md

@@ -43,6 +43,8 @@ Treat ChatGPT as the controller and Forge as its repository execution layer. Cha
 
 ## Operating Rules
 
+- Default to end-to-end execution and minimize avoidable human intervention. Continue through reversible, policy-allowed setup, implementation, verification, cleanup, and delivery steps without asking the user to babysit the workflow; stop only at a genuinely user-only identity, legal/contract, financial authorization, strong-confirmation, or irreversible decision boundary.
+- For authenticated browser work, preserve the user's existing browser identity: reuse the already-running signed-in Google Chrome via attach-preferred, native-auto, Chrome-only, fail-closed routing. Preserve its cookies, tokens, sessions, and settings; never silently launch or switch to a managed, isolated, Vivaldi, or otherwise unauthenticated browser/profile. Managed or isolated browser modes require an explicit task/action request. If the user Chrome cannot be attached safely, fail closed and surface the concrete blocker instead of creating a replacement login state.
 - After a managed repository change is verified and committed/merged, push the delivered target branch to its configured remote promptly. Do not leave a successfully delivered commit only on local refs unless the user explicitly requested local-only delivery or the push is blocked by safety, permissions, authentication, or branch policy; surface the exact blocker when a push cannot complete.
 - Treat the Google Cloud `forge-cloud` VM experiment as retired infrastructure. Do not restart or reuse that VM for Forge Cloud. Any future remote Forge maintainer must use a separately evaluated host/transport and must demonstrate better latency and reliability than the local Forge path before adoption.
 - Sync `tasks/` whenever substantive repo changes are made.

package/THIRD_PARTY_NOTICES.md

@@ -1,6 +1,6 @@
 # Third-party notices
 
-This inventory covers the direct runtime and development dependencies declared by `@moretea-labs/forge@1.7.0`.
+This inventory covers the direct runtime and development dependencies declared by `@moretea-labs/forge@1.7.2`.
 
 License values come from `package-lock.json` where available. For lock entries without a license field, the declared license was verified from package metadata during release preparation. This file is informational and does not replace the license text distributed by each dependency.
 

package/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "forge"
   short_description: "Operate Forge workflows for repository planning, execution, verification, migration, audit, and repair"
-  default_prompt: "Use Forge to inspect this repository, choose the smallest appropriate workflow, and carry out or plan the requested work with bounded evidence and verification. After verified repository delivery, promptly push the committed/merged target branch to its configured remote unless the user explicitly requested local-only delivery or the push is blocked; report any blocker precisely."
+  default_prompt: "Use Forge to inspect this repository, choose the smallest appropriate workflow, and carry the requested work through implementation, verification, cleanup, and delivery with bounded evidence while minimizing avoidable human intervention. Continue reversible policy-allowed steps autonomously and stop only at a genuinely user-only identity/legal/financial/strong-confirmation/irreversible boundary. For authenticated browser work, reuse the user's already-running signed-in Google Chrome with attach-preferred, native-auto, Chrome-only, fail-closed routing; preserve its cookies/tokens/sessions/settings and never silently launch or switch to a managed, isolated, Vivaldi, or otherwise unauthenticated profile unless the task explicitly requests that mode. After verified repository delivery, promptly push the committed/merged target branch to its configured remote unless the user explicitly requested local-only delivery or the push is blocked; report any blocker precisely."

package/assets/partials-agents/02-operating-mode.partial.md

@@ -8,6 +8,8 @@
 - Claude runtime expectation: `{{CLAUDE_POLICY}}`.
 - Codex runtime expectation: `{{CODEX_POLICY}}`.
 - Do not implement until the user explicitly asks to implement.
+- Once the user asks to execute, minimize avoidable human intervention: continue reversible, policy-allowed implementation, verification, cleanup, and delivery autonomously, stopping only at a genuinely user-only identity/legal/financial/strong-confirmation/irreversible boundary.
+- For authenticated browser work, reuse the user's already-running signed-in Google Chrome with attach-preferred, native-auto, Chrome-only, fail-closed routing. Preserve cookies, tokens, sessions, and settings; never silently switch to a managed, isolated, Vivaldi, or otherwise unauthenticated profile unless the task explicitly requests that mode.
 - Stable product truth: `docs/spec.md`.
 - Research reports: `docs/researches/`.
 - Deferred-goal ledger: `tasks/todos.md` (active execution stays in the plan's `## Task Breakdown`).

package/assets/plugin-registry.v1.json

@@ -4,12 +4,12 @@
     {
       "id": "desktop_operator",
       "name": "Forge Desktop Operator",
-      "version": "0.2.1",
+      "version": "0.2.3",
       "description": "Native macOS desktop automation provider for Forge.",
       "repository": "https://github.com/moretea-labs/forge-desktop-operator.git",
-      "ref": "v0.2.1",
+      "ref": "v0.2.3",
       "installer": "forge-plugin-install.mjs",
-      "providerVersion": "0.2.1",
+      "providerVersion": "0.2.3",
       "protocolVersion": "1.0",
       "platforms": [
         "darwin"

package/assets/skill-version.json

@@ -1,6 +1,6 @@
 {
-  "version": "1.7.0",
-  "templateVersion": "1.7.0",
+  "version": "1.7.2",
+  "templateVersion": "1.7.2",
   "skillName": "forge",
   "contractId": "tasks-first-harness-v1",
   "compatibility": {

package/assets/templates/helpers/check-architecture-sync.sh

@@ -212,6 +212,23 @@ if ! bash scripts/architecture-queue.sh reindex --check >/dev/null; then
   exit 1
 fi
 
+if [[ -f "docs/architecture/current/README.md" ]]; then
+  if [[ ! -f "docs/architecture/CURRENT.md" ]]; then
+    echo "[ArchitectureSync] architecture baseline failed: missing required file docs/architecture/CURRENT.md" >&2
+    exit 1
+  fi
+
+  if ! grep -Fq "Runtime Authority" "docs/architecture/CURRENT.md"; then
+    echo "[ArchitectureSync] architecture baseline failed: docs/architecture/CURRENT.md must contain: Runtime Authority" >&2
+    exit 1
+  fi
+
+  if ! grep -Fq "Not Runtime Authority" "docs/architecture/current/README.md"; then
+    echo "[ArchitectureSync] architecture baseline failed: docs/architecture/current/README.md must contain: Not Runtime Authority" >&2
+    exit 1
+  fi
+fi
+
 if [[ "$mode" == "off" ]]; then
   case "$format" in
     json) printf '{"mode":"off","changed_capabilities":0,"blocking":0}\n' ;;

package/assets/templates/helpers/inspect-project-state.ts

@@ -270,11 +270,13 @@ function renderText(result: InspectionResult): string {
   return lines.join("\n");
 }
 
-const { repo, format } = parseArgs(process.argv.slice(2));
-const result = inspectRepo(repo);
+if (import.meta.main) {
+  const { repo, format } = parseArgs(process.argv.slice(2));
+  const result = inspectRepo(repo);
 
-if (format === "text") {
-  console.log(renderText(result));
-} else {
-  console.log(JSON.stringify(result, null, 2));
+  if (format === "text") {
+    console.log(renderText(result));
+  } else {
+    console.log(JSON.stringify(result, null, 2));
+  }
 }

package/assets/templates/helpers/migrate-workflow-docs.ts

@@ -403,11 +403,13 @@ function renderText(summary: MigrationSummary): string {
   return lines.join("\n");
 }
 
-const { repo, mode, format } = parseArgs(process.argv.slice(2));
-const summary = migrate(repo, mode);
-
-if (format === "json") {
-  console.log(JSON.stringify(summary, null, 2));
-} else {
-  console.log(renderText(summary));
+if (import.meta.main) {
+  const { repo, mode, format } = parseArgs(process.argv.slice(2));
+  const summary = migrate(repo, mode);
+
+  if (format === "json") {
+    console.log(JSON.stringify(summary, null, 2));
+  } else {
+    console.log(renderText(summary));
+  }
 }

package/assets/templates/helpers/workflow-contract.ts

@@ -65,6 +65,10 @@ export type WorkflowContract = {
   helpers: {
     runtimeDirectory?: string;
     compatibilityDirectory?: string;
+    /** Legacy manifest field retained for installed contract compatibility. */
+    dir?: string;
+    /** Legacy runtime-source discriminator still present in v1 manifests. */
+    runtimeSource?: string;
     scripts: string[];
   };
   artifacts: {
@@ -185,7 +189,7 @@ export function getHelperScripts(contract: WorkflowContract): string[] {
 }
 
 export function getHelperRuntimeDir(contract: WorkflowContract): string {
-  return contract.helpers.dir ?? "scripts";
+  return contract.helpers.runtimeDirectory ?? contract.helpers.dir ?? contract.helpers.compatibilityDirectory ?? "scripts";
 }
 
 export function getRequiredDirectories(contract: WorkflowContract): string[] {

package/docs/architecture/CURRENT.md

@@ -92,6 +92,11 @@ Explicit **Scale** is the opt-in coordination form of this existing model, not a
 - Durable Process owns persisted command/check lifecycle only when the selected lane is durable.
 - Runtime release/recovery state owns Forge service availability and immutable release activation; it is separate from ordinary command recovery. The canonical OS service executes an atomic byte-identical mirror of the selected signed Runtime entrypoint from the fixed physical `runtime/service/active-forge-runtime` path, while release resources and identity remain manifest-bound. The stable physical path prevents macOS TCC from treating every immutable release directory as a new responsible-process principal.
 - Historical Issue/Task/Local Job and compatibility projections must not become second mutable authorities.
+- Work lifecycle policy is separated from persistence: `work-state-machine.ts` owns legal phase/dispatch/evidence/completion transitions, while `work-contract-store.ts` owns locked persistence and applies that policy. Work completion projection is centralized in `work-completion-authority.ts`, and Work verification execution/evidence is centralized in `work-verification-service.ts`. Transports may submit requests and encode results but must not reimplement these rules.
+- Work delivery/finalization is also an application service: `work-finalization-service.ts` owns the commit/merge/cleanup/receipt transaction and `work-execution-support.ts` owns shared exact identity/cleanup primitives. MCP `execution-tools.ts` and `rh_work` compatibility glue may prepare arguments or reconcile legacy handles, but they must enter that same finalization authority rather than perform Git delivery themselves.
+- Work preparation/adoption is an application service as well: `work-preparation-service.ts` owns managed-workspace selection, WorkContract admission/reuse, exact successor-HEAD adoption and Controller ownership binding. MCP `execution-tools.ts` only decodes `work_prepare` / repository-bind requests and delegates; it must not recreate workspace admission or WorkHandle/WorkContract preparation transitions.
+- Work command execution and validation live in `work-operation-service.ts`. Both MCP Gateway and Durable Worker call this application service directly; Workers must never dynamic-import MCP transport to obtain Work semantics. The architecture gate also forbids any `runtime/control-plane` source from depending back on `runtime/gateway`.
+- Production Browser session persistence is Controller-home SQLite `BrowserSessionAuthority`. Compatibility JSON may be imported or used only when no Controller authority is available; handoff sidecars return interaction results and never write BrowserSession state directly.
 
 ## Runtime and MCP boundary
 
@@ -100,7 +105,8 @@ Explicit **Scale** is the opt-in coordination form of this existing model, not a
 - The default Controller MCP schema is the stable **19-tool** surface.
 - `core` and `advanced` expose that same stable surface.
 - `toolset=full` is an explicit compatibility profile and may contain historical definitions; current default schema construction must not depend on those legacy definitions.
-- Current schemas/handlers should live with their owning module. Legacy compatibility may delegate but must not independently own current business rules.
+- Current schemas/handlers should live with their owning module. Legacy compatibility may delegate but must not independently own current business rules. Shared transport contracts and tool definitions belong in neutral contract/definition modules so the dependency direction remains transport -> application/domain authority rather than transport implementations importing one another.
+- Work-attributed verification is an application service, not an MCP/Local Bridge implementation detail: all Work verification resolves the Work checkout/check registry, runs through Process Runtime, validates terminal receipt identity, and records Work evidence through the same `work-verification-service.ts`.
 
 ### Controller facade and handoff boundary
 
@@ -131,15 +137,17 @@ Browser providers are selected by declared capability. Common DOM and typed brow
 
 Foreground presentation is an explicit effect reserved for capabilities that truly require physical pointer/keyboard input or human handoff. Browser `trusted_input` never silently activates a background tab or converts CSS viewport coordinates into desktop coordinates. If the native broker lacks the required trusted-input capability, Browser fails with a typed capability error; an explicitly requested Desktop Operator foreground/physical action remains a separate authority boundary. Mutating provider actions are complete only when their declared postconditions are verified; transport, Apple Events, Accessibility, socket, or CGEvent success alone is not semantic completion.
 
-The public Browser action surface remains compatible across Playwright/CDP/native providers. Current native compatibility may omit optional broker methods such as global tab inventory while preserving exact-ref lifecycle safety. DOM automation through Chrome/Vivaldi Apple Events still requires the browser's JavaScript-from-Apple-Events permission; missing permission fails closed instead of weakening the provider contract.
+The public Browser action surface remains compatible across Playwright/CDP/native providers. Current native compatibility may omit optional broker methods such as global tab inventory while preserving exact-ref lifecycle safety. DOM automation through Chrome/Vivaldi Apple Events still requires the browser's JavaScript-from-Apple-Events permission; missing permission fails closed instead of weakening the provider contract. Browser replay safety is derived from the Browser Runtime transaction contract rather than an adapter-local action allowlist, and native session liveness/reconciliation is centralized outside the plugin composition root. A human-handoff host may persist its own InteractionSession result, but BrowserSession mutation returns to the canonical Runtime authority.
 
 ## Testing and verification
 
 Tests are verification evidence, not an alternate architecture authority.
 
-- Development/task gate: typecheck + static architecture + manifest validity + affected tests.
+- Development/task gate: typecheck + static architecture + generated-authority drift + source-duplication classification + controller-UI reproduction + manifest validity + affected tests.
 - Main candidate: task gate + core regression + Runtime smoke.
 - Release candidate: main gate + full regression + release packaging/readiness.
+- Static architecture additionally requires the production `src/**/*.ts` relative-import graph to be acyclic. Neutral contracts may break dependency direction; dynamic imports must not be used merely to conceal a static architecture cycle.
+- Source-duplication governance permits only classified distribution/template projections, guidance aliases, and placeholders; unclassified exact duplicates fail the gate. Generated copies may exist for packaging, but manual implementation duplication is not an accepted source-authoring model.
 - Test governance validates registration, resource classification, selection and execution isolation; it does not impose arbitrary global test-line or resource-count budgets.
 - Prefer a small number of architectural invariants, focused module tests and essential integration/E2E coverage. Delete implementation-coupled or retired-compatibility tests when the underlying obligation is removed.
 
@@ -163,7 +171,7 @@ Research notes, tasks, reviews, archived architecture pages, plans and Git histo
 
 ## Intentionally retained compatibility debt
 
-- Explicit `toolset=full` remains a supported legacy compatibility boundary for now.
+- Explicit `toolset=full` remains a supported legacy compatibility boundary for now. Issue/Task/project-board writers are migration-only compatibility and are permanently retired after the SQLite requirement-portfolio cutover marker; they must not become a second current control plane.
 - Some large runtime modules still aggregate multiple responsibilities and should be decomposed only when a clear ownership boundary is available.
 - CodeGraph may be structurally stale between index refreshes; current raw source and changed-file overlays remain authoritative.
 

package/docs/forge-plugin-management.md

@@ -10,7 +10,7 @@ forge plugin catalog
 
 | Plugin ID | Product | Pinned release | Platforms |
 | --- | --- | --- | --- |
-| `desktop_operator` | [Forge Desktop Operator](https://github.com/moretea-labs/forge-desktop-operator) | `v0.2.1` | macOS |
+| `desktop_operator` | [Forge Desktop Operator](https://github.com/moretea-labs/forge-desktop-operator) | `v0.2.3` | macOS |
 | `design` | [Forge Design](https://github.com/moretea-labs/forge-design) | `v0.3.0` | macOS, Linux, Windows |
 | `personal_knowledge` | [Personal Knowledge Assistant](https://github.com/moretea-labs/personal-knowledge-assistant) | `v0.2.1` | macOS, Linux, Windows |
 

package/docs/operations/controller-performance-and-502.md

@@ -120,6 +120,25 @@ Corrected invariants:
    reason and restart/failure counters) so incident review can distinguish "Recovery
    never fired" from "Recovery fired and the client observed the bounded outage".
 
+## Recurring Connection Failure Ledger
+
+Keep these failure signatures distinct. A public `502` identifies the failed
+hop; it does not identify the failed owner or authorize a whole-Runtime
+rollback.
+
+| Signature | Verified evidence | Correct recovery owner |
+| --- | --- | --- |
+| Runtime activation/port conflict | `RUNTIME_RELEASE_AUTHORITY_MISMATCH`, port `8767` already in use, or orphaned `mcp serve` | Whole-Runtime Recovery transaction; see the 2026-08-23 incident above. |
+| Connector/release binding drift | Runtime `ready=true`, but Connector loopback/public MCP fails or returns `5xx` | Connector Recovery reconciles the active immutable release, then verifies local ownership and the public endpoint. |
+| Connector launched with a Recovery-role binary | Connector plist starts `forge-recovery-gateway` or `forge-recovery-watchdog`; stderr repeats `RECOVERY_*_ROLE_ONLY` | Repair the Connector with the absolute interpreter recorded by Runtime activation. A Connector launch spec must reject a Recovery-role binary. |
+| Connector outage misclassified as a Runtime outage | Runtime status and local active Gateway are healthy while the Watchdog records `restart_primary_runtime` for a Connector probe failure | Count and restart the Connector under its own bounded budget; do not consume the Runtime restart/rollback budget. |
+
+The launch interpreter is part of the Connector's immutable release binding:
+detached activation passes its recorded absolute `nodeExecutable` to candidate
+and rollback Connector installs, and Recovery services retain the same explicit
+interpreter for later binding repair. Regression coverage must exercise a
+failed Connector while the Canonical Runtime remains healthy.
+
 ## Session Continuation Fails With 404 MCP_TOOL_SURFACE_CHANGED (2026-08-23)
 
 Second incident on the same day, different failure mode. After a session is

package/docs/operations/homebrew.md

@@ -6,8 +6,8 @@ Homebrew is planned as a convenience layer after the first stable npm/GitHub rel
 
 Do not publish a formula until all of the following are true:
 
-- `@moretea-labs/forge@1.7.0` exists on npm;
-- Git tag and GitHub Release `v1.7.0` exist and point to the tested commit;
+- `@moretea-labs/forge@1.7.2` exists on npm;
+- Git tag and GitHub Release `v1.7.2` exist and point to the tested commit;
 - the npm tarball has an immutable checksum;
 - macOS installation and `forge --version` / `forge doctor` tests pass;
 - upgrade and uninstall behavior is documented.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@moretea-labs/forge",
-  "version": "1.7.0",
+  "version": "1.7.2",
   "description": "Local-first action assistant for software work with resumable execution, bounded tools, and reviewable evidence",
   "license": "MIT",
   "author": "Moretea Labs contributors",
@@ -106,6 +106,8 @@
     "test:coverage": "bun test --coverage",
     "check:type": "bun x tsc --noEmit",
     "check:runtime-architecture": "node scripts/check-runtime-architecture.mjs",
+    "check:generated-authority": "node scripts/sync-generated-authority.mjs --check",
+    "check:source-duplication": "node scripts/check-source-duplication.mjs",
     "check:executable-modes": "bun scripts/repair-executable-modes.ts --check",
     "repair:executable-modes": "bun scripts/repair-executable-modes.ts",
     "check:test-governance": "bun scripts/test-governance.ts validate",
@@ -151,7 +153,8 @@
     "test:bun": "bun -e 'console.error(\"[tests] test:bun is deprecated; running explicit test:full\")' && bun run test:full",
     "test:node-smoke": "node --test tests/node/*.test.mjs",
     "check:ci:portable": "FORGE_ALLOW_NODE_ONLY=1 bash scripts/check-ci.sh",
-    "dev:controller-ui": "vite --config src/cli/local-bridge/frontend/vite.config.ts"
+    "dev:controller-ui": "vite --config src/cli/local-bridge/frontend/vite.config.ts",
+    "prepack": "node scripts/sync-generated-authority.mjs --check"
   },
   "devDependencies": {
     "@colbymchenry/codegraph": "1.0.1",