@runfusion/fusion 0.77.0-beta.11 → 0.77.0-beta.12

package/dist/pi-claude-cli/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion/pi-claude-cli",
-  "version": "0.77.0-beta.11",
+  "version": "0.77.0-beta.12",
   "type": "module",
   "private": true,
   "main": "index.ts",

package/dist/plugin-sdk/index.d.ts

@@ -336,6 +336,10 @@ interface WorkflowStepResult {
     repositoryScopeRevision?: number;
     remediationArchivedAt?: string;
     remediationArchivedFromStatus?: WorkflowStepResult["status"];
+    remediationAttemptSignature?: string;
+    remediationAttemptOwner?: string;
+    remediationAttemptClaimedAt?: string;
+    remediationRefusedReason?: "no-actionable-findings" | "upstream-out-of-scope" | "unclassified-gate-no-reopen" | "appender-declined";
     notRunReason?: WorkflowStepNotRunReason;
     reviewInputFingerprint?: string;
     reviewedCommitSha?: string;
@@ -5823,6 +5827,10 @@ declare class TaskStore extends EventEmitter<TaskStoreEvents> {
     updateTaskAtomic(id: string, updater: (current: Task) => Parameters<TaskStore["updateTask"]>[1] | null | undefined | Promise<Parameters<TaskStore["updateTask"]>[1] | null | undefined>, runContext?: RunMutationContext): Promise<Task>;
     appendRemediationSteps(taskId: string, steps: readonly TaskStep[], options?: AppendRemediationStepsOptions): Promise<AppendRemediationStepsResult>;
     updateWorkflowStepResultsFenced(id: string, compute: WorkflowStepResultsFencedCompute): Promise<WorkflowStepResultsFencedUpdateResult>;
+    updateWorkflowStepResultsWithLogFenced(id: string, compute: (current: Task) => {
+        workflowStepResults: Task["workflowStepResults"];
+        logEntry: TaskLogEntry;
+    } | null): Promise<WorkflowStepResultsFencedUpdateResult>;
     dismissAiMergeReviewFinding(taskId: string, findingId: string, reason: string, actor?: string): Promise<Task>;
     linkTaskRecommendation(id: string, recommendationId: string, createdTaskId: string, completeColumns?: ReadonlySet<string>): Promise<Task>;
     normalizeWorkspaceTaskWorktreeMetadata(id: string): Promise<Task>;

package/dist/plugin-sdk/index.js

@@ -9029,6 +9029,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-acp-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14400,6 +14401,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;
@@ -37992,11 +37994,19 @@ async function authenticateAcpConnection(connection, opts) {
   return { methodId };
 }
 async function newAcpSession(connection, opts) {
-  const res = await connection.conn.newSession({
-    cwd: opts.cwd,
-    mcpServers: opts.mcpServers ?? [],
-    ...opts.meta && Object.keys(opts.meta).length > 0 ? { _meta: opts.meta } : {}
-  });
+  let res;
+  try {
+    res = await connection.conn.newSession({
+      cwd: opts.cwd,
+      mcpServers: opts.mcpServers ?? [],
+      ...opts.meta && Object.keys(opts.meta).length > 0 ? { _meta: opts.meta } : {}
+    });
+  } catch (error51) {
+    throw new Error(
+      `session/new failed (cwd ${opts.cwd}): ${describeAcpTurnError(error51)}`,
+      { cause: error51 }
+    );
+  }
   return { sessionId: boundIdentifier(res.sessionId), modes: res.modes ?? void 0 };
 }
 var RETRYABLE_JSONRPC_CODES = /* @__PURE__ */ new Set([

package/dist/plugins/fusion-plugin-acp-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/acp-runtime",
-  "version": "0.1.36-beta.11",
+  "version": "0.1.36-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-claude-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14400,6 +14401,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-claude-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/claude-runtime",
-  "version": "0.1.11-beta.11",
+  "version": "0.1.11-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-cli-printing-press/bundled.js

@@ -9148,6 +9148,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14512,6 +14513,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-cli-printing-press/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/cli-printing-press",
-  "version": "0.1.53-beta.11",
+  "version": "0.1.53-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-compound-engineering/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-compound-engineering/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/compound-engineering",
-  "version": "0.1.36-beta.11",
+  "version": "0.1.36-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-cursor-runtime/bundled.js

@@ -9031,6 +9031,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14395,6 +14396,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-cursor-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/cursor-runtime",
-  "version": "0.1.55-beta.11",
+  "version": "0.1.55-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-dependency-graph/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-dependency-graph/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/dependency-graph",
-  "version": "0.1.67-beta.11",
+  "version": "0.1.67-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-droid-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-droid-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/droid-runtime",
-  "version": "0.1.62-beta.11",
+  "version": "0.1.62-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-grok-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14400,6 +14401,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-grok-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/grok-runtime",
-  "version": "0.2.14-beta.11",
+  "version": "0.2.14-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-hermes-runtime/bundled.js

@@ -9031,6 +9031,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14395,6 +14396,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-hermes-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/hermes-runtime",
-  "version": "0.2.86-beta.11",
+  "version": "0.2.86-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-linear-import/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-linear-import/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/linear-import",
-  "version": "0.1.18-beta.11",
+  "version": "0.1.18-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-omp-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14400,6 +14401,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-omp-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/omp-runtime",
-  "version": "0.1.11-beta.11",
+  "version": "0.1.11-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-openclaw-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-openclaw-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/openclaw-runtime",
-  "version": "0.2.86-beta.11",
+  "version": "0.2.86-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-paperclip-runtime/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-paperclip-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/paperclip-runtime",
-  "version": "0.2.86-beta.11",
+  "version": "0.2.86-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-quality/bundled.js

@@ -9031,6 +9031,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14395,6 +14396,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-quality/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/quality",
-  "version": "0.1.11-beta.11",
+  "version": "0.1.11-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-reports/bundled.js

@@ -9148,6 +9148,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14512,6 +14513,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-reports/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/reports",
-  "version": "0.1.55-beta.11",
+  "version": "0.1.55-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-roadmap/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-roadmap/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/roadmap",
-  "version": "0.1.55-beta.11",
+  "version": "0.1.55-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-todos/bundled.js

@@ -9028,6 +9028,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -14392,6 +14393,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-todos/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/todos",
-  "version": "0.1.4-beta.11",
+  "version": "0.1.4-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/dist/plugins/fusion-plugin-whatsapp-chat/bundled.js

@@ -159966,6 +159966,7 @@ function planReviewOptionalGroupNode(column, options = {}) {
 
 // ../core/src/workflows/workflow-step-results.ts
 var PLAN_REVIEW_LEASE_STALENESS_MS = 15 * 60 * 1e3;
+var REMEDIATION_ATTEMPT_CLAIM_STALENESS_MS = 15 * 60 * 1e3;
 
 // ../core/src/merge/task-merge.ts
 var HARD_BLOCKING_TASK_STATUSES = /* @__PURE__ */ new Set([
@@ -165330,6 +165331,7 @@ Be specific: cite \`file:line\` for every finding and explain the concrete failu
 - APPROVE_WITH_NOTES: shippable. Use this when your findings are all P1/P2 \u2014 they are recorded and handed to the implementer without another remediation round.
 - REVISE: a correctness bug, regression, or contract break requires changes before merge. Requires at least one \`critical\` finding in \`findings\`; a REVISE without one will be treated as APPROVE_WITH_NOTES.
 - Every blocking issue MUST appear as an entry in \`findings\` with its severity and \`filePath\`/\`line\`. Prose in \`notes\` alone does not block.
+- Every REVISE finding is a required Fix-step record. Its \`id\`, \`title\`, \`body\`, \`filePath\`, \`line\`, and \`severity\` must be concrete enough for an executor to implement without asking what to fix. If you cannot name an affected file and correction, do not return REVISE: investigate until you can, or return the appropriate non-blocking verdict.
 - \`notes\` MUST contain one to three sentences naming what was checked and why the verdict was reached. An empty \`notes\` string is a protocol violation.
 - Final output: output exactly one trailing JSON object on the final line (no markdown fences, no surrounding prose):
 {"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"...","findings":[{"id":"stable-id","title":"concise issue","body":"concrete failure and remediation","filePath":"path/to/file.ts","line":1,"severity":"critical|high|medium|low","resolution":"open|resolved-in-review|superseded"}]}`;

package/dist/plugins/fusion-plugin-whatsapp-chat/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusion-plugin-examples/whatsapp-chat",
-  "version": "0.1.55-beta.11",
+  "version": "0.1.55-beta.12",
   "type": "module",
   "exports": {
     ".": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@runfusion/fusion",
-  "version": "0.77.0-beta.11",
+  "version": "0.77.0-beta.12",
   "license": "MIT",
   "description": "Fusion CLI: HTTP API server, daemon, dashboard launcher, and task tooling for the Fusion AI coding agent.",
   "homepage": "https://github.com/Runfusion/Fusion#readme",

package/dist/client/assets/channel-9ayksTsZ.js

@@ -1 +0,0 @@
-import{U as a,C as n}from"./mermaid.core-CRm31xPI.js";const t=(r,o)=>a.lang.round(n.parse(r)[o]);export{t as c};

package/dist/client/assets/classDiagram-4FO5ZUOK-6A8Tw1Fx.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as t,C as e}from"./chunk-727SXJPM-0xpHKXZs.js";import{_ as i}from"./mermaid.core-CRm31xPI.js";import"./vendor-reactflow-BlIeoTu4.js";import"./chunk-FMBD7UC4-DxjEMlOu.js";import"./chunk-ND2GUHAM-BGUlWNB6.js";import"./chunk-55IACEB6-r6YyDKyy.js";import"./chunk-2J33WTMH-BP1RbVtu.js";import"./index-CSZd8sbH.js";import"./vendor-react-SZ_qB27O.js";import"./vendor-i18n-Duky4gdQ.js";import"./vendor-codemirror-CcrtqoCy.js";import"./vendor-xterm-BNq00GSj.js";import"./step-yuy0qJer.js";var k={parser:t,get db(){return new e},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{k as diagram};

package/dist/client/assets/classDiagram-v2-Q7XG4LA2-6A8Tw1Fx.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as t,C as e}from"./chunk-727SXJPM-0xpHKXZs.js";import{_ as i}from"./mermaid.core-CRm31xPI.js";import"./vendor-reactflow-BlIeoTu4.js";import"./chunk-FMBD7UC4-DxjEMlOu.js";import"./chunk-ND2GUHAM-BGUlWNB6.js";import"./chunk-55IACEB6-r6YyDKyy.js";import"./chunk-2J33WTMH-BP1RbVtu.js";import"./index-CSZd8sbH.js";import"./vendor-react-SZ_qB27O.js";import"./vendor-i18n-Duky4gdQ.js";import"./vendor-codemirror-CcrtqoCy.js";import"./vendor-xterm-BNq00GSj.js";import"./step-yuy0qJer.js";var k={parser:t,get db(){return new e},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{k as diagram};