@eforge-build/eforge-plan 0.8.0

package/package.json

@@ -0,0 +1,72 @@
+{
+  "name": "@eforge-build/eforge-plan",
+  "version": "0.8.0",
+  "description": "First-party eforge planning extension with backlog, session-plan, recommendation, and workstation contributions.",
+  "license": "Apache-2.0",
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "types": "./dist/index.d.ts",
+  "files": [
+    "dist/",
+    "prompts/",
+    "workstation-assets/",
+    "README.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/eforge-build/eforge.git"
+  },
+  "homepage": "https://eforge.build",
+  "keywords": [
+    "eforge",
+    "extension",
+    "planning",
+    "backlog",
+    "workstation"
+  ],
+  "dependencies": {
+    "@sinclair/typebox": "0.34.50",
+    "yaml": "^2.9.0",
+    "@eforge-build/extension-sdk": "0.8.0",
+    "@eforge-build/client": "0.8.0",
+    "@eforge-build/input": "0.8.0"
+  },
+  "devDependencies": {
+    "@types/node": "^26.1.1",
+    "tsup": "^8.5.1",
+    "typescript": "^6.0.3",
+    "@eforge-build/eforge-plan-workstation": "0.0.0"
+  },
+  "author": "Schaake Solutions LLC",
+  "eforge": {
+    "extension": {
+      "name": "eforge-plan",
+      "entrypoint": "./dist/index.js",
+      "capabilities": [
+        {
+          "name": "eforge.plan.planning-workstation",
+          "version": "1.0.0"
+        }
+      ]
+    }
+  },
+  "scripts": {
+    "build": "pnpm run build:workstation && pnpm run build:runtime",
+    "build:runtime": "tsup",
+    "build:workstation": "pnpm --dir workstation-src/plans build",
+    "type-check": "tsc --noEmit"
+  }
+}

package/prompts/eforge-plan-backlog-curation-item-audit.md

@@ -0,0 +1,71 @@
+# eforge-plan Backlog Curation Item Audit
+
+You are auditing exactly one validated backlog item for map/reduce backlog curation. Your job is to determine the item's current truth by inspecting the repository with read-only tools.
+
+You may use read-only repository tools such as file reads, directory/file discovery, text search, and read-only git inspection. Do not write files, edit files, run mutating commands, install dependencies, start servers, or use network access. Your only accepted final output channel is the submission tool.
+
+## Identity
+
+- Target item id: {{itemId}}
+- Source fingerprint: {{sourceFingerprint}}
+- Packet SHA-256: {{packetSha256}}
+- Prompt version: {{promptVersion}}
+- {{runtimeIdentityInstruction}}
+
+```json
+{{runtimeIdentityJson}}
+```
+
+## Packet JSON
+
+The packet is a bounded work order, not the entire evidence universe. Use it for item metadata, acceptance criteria/section summaries, dependency facts, historical navigation hints, recommendation signals, and precondition hashes. Historical hints are search leads only and have `closureAuthority: false`.
+
+```json
+{{packetJson}}
+```
+
+## Progress reporting
+
+You MAY call `{{progressTool}}` for telemetry-only progress. Progress never replaces the final submission.
+
+## Audit rules
+
+- Audit only the target item id shown above. Do not infer facts from any other backlog item except when dependency facts are directly relevant.
+- Inspect current source directly. Search for item ids, title terms, command/action/route/component names, changed paths or PR hints from historical hints, and likely product-surface entry points.
+- Current source is the authority for shipped, superseded, partial, still-needed, and stale/invalid conclusions. Historical git/PR/lifecycle hints may guide where to look but are not standalone closure authority.
+- Treat shipped as proven only when current source shows both implementation/replacement logic and user/product-surface wiring, or when the item is explicitly docs/config-only and the relevant committed docs/config surface is present.
+- Treat superseded as proven only when current source or current docs show a replacement/current direction that makes the original item obsolete.
+- Treat partial as useful: cite what exists and summarize what remains.
+- Treat still-needed as useful when you checked likely locations and did not find implementation.
+- Use needs-input only for true product/user decisions, not for missing source evidence.
+- Do not include raw evidence dumps, raw item bodies, or unrelated context in your output.
+- Keep the finding compact. Include only source citations and checked paths that explain the verdict.
+- Preserve `itemId`, `sourceFingerprint`, `bodySha256`, `packetSha256`, and `promptVersion` exactly.
+- If the server provided runtime identity above, do not include `runtimeIdentity`; the runner injects the authoritative runtime identity. If it is `null`, include a valid `runtimeIdentity` in the submission.
+
+## Output contract
+
+You MUST call `{{submitTool}}` exactly once with a compact finding matching the shared `BacklogCurationMapReduceFinding` shape:
+
+- `schemaVersion`: `1`
+- `itemId`: `{{itemId}}`
+- `sourceFingerprint`: `{{sourceFingerprint}}`
+- `packetSha256`: `{{packetSha256}}`
+- `bodySha256`: copy exactly from the packet
+- `promptVersion`: `{{promptVersion}}`
+- `disposition`: one of `change`, `recheck`, `skip`, or `needs-input`
+- `verdict`: one of `shipped`, `superseded`, `partial`, `still-needed`, `stale-invalid`, `needs-product-input`, or `skip`
+- `closureEvidenceRoles`: include `implementation` or `replacement` plus `product-surface` when proposing `shipped` or `superseded`; include `supporting` for tests/docs/config evidence.
+- `checkedPaths`: compact list of source paths inspected and why they mattered.
+- `summary` and `rationale`: concise, no raw evidence dump
+- `citations`: current-source citations from files you inspected. For shipped/superseded, include at least one implementation/replacement citation and one product-surface citation unless the item is explicitly docs/config-only.
+- `recommendationSignals` and `diagnostics`: bounded arrays only
+
+Disposition guidance:
+
+- `shipped` or `superseded` verdicts should usually use `disposition: "change"` so the reducer can propose a status update.
+- `partial`, `still-needed`, or `stale-invalid` should use `change` when concrete backlog text/metadata should change, otherwise `recheck`.
+- `needs-product-input` should use `needs-input`.
+- `skip` should be exceptional.
+
+Submit exactly once. Do not finish with prose. The submission tool is the only accepted output channel.

package/prompts/eforge-plan-backlog-curation-reducer.md

@@ -0,0 +1,61 @@
+# eforge-plan Backlog Curation Reducer
+
+You are reducing capped backlog-curation map outcomes into the existing eforge-plan planning draft result shape. Do not use repository, filesystem, shell, network, or mutation tools. Use only the reducer input JSON and any validation errors shown here.
+
+## Requested output sections
+
+{{requestedOutputSections}}
+
+## Reducer input JSON
+
+This input is capped and contains global summaries, dependency/recommendation summaries, diagnostics, and compact per-item outcomes. Item findings may include source-backed verdicts produced by read-only item agents. It intentionally excludes raw backlog packets, raw item bodies, raw `gitDelta`, and raw `fullImplementationAudit` evidence.
+
+```json
+{{reducerInputJson}}
+```
+
+## Prior validation errors for this repair attempt
+
+If this array is non-empty, repair the previous submission by addressing each bounded validation error. Do not ask for raw packets or raw evidence.
+
+```json
+{{validationErrors}}
+```
+
+## Progress reporting
+
+You MAY call `{{progressTool}}` for telemetry-only progress. Progress never replaces the final submission.
+
+## Output contract
+
+You MUST call `{{submitTool}}` exactly once with a JSON payload matching this existing planning draft result schema:
+
+```yaml
+{{resultSchema}}
+```
+
+The payload MUST include:
+
+1. `summary` — concise curation summary.
+2. `assumptionsOpenQuestions` — bounded assumptions/open questions; use an empty array only when there are truly none.
+3. A ready result with `backlogCurationDraft`, `recommendations`, or both when the capped outcomes support it; otherwise emit the top-level `decision: "needs-input"` shape with non-empty `clarificationQuestions` and `rationale`.
+
+## Reduction rules
+
+- Preserve the reducer input `sourceFingerprint` exactly in any `backlogCurationDraft`.
+- Engine emits, consumers apply: do not claim that backlog records were written, updated, shipped, or persisted.
+- Item audit findings are source-backed verdicts. Convert them into structured patches when the finding contains a safe rationale and current-source citations.
+- For `verdict: "shipped"`, create an item change setting `metadata.status: "shipped"` when citations/roles show implementation plus product-surface wiring, or when the finding explains the item is explicitly docs/config-only and cites that current surface.
+- For `verdict: "superseded"`, create an item change setting `metadata.status: "superseded"` when citations/roles show replacement/current direction plus product-surface or docs/config authority.
+- Closed-status item changes must include durable evidence strings beginning with `Shipped evidence: current source — ` or `Superseded evidence: current source — `. Include role labels in those evidence strings, e.g. `implementation: path`, `replacement: path`, and `product-surface: path`, so apply-time validation can verify both roles.
+- For `partial`, `still-needed`, or `stale-invalid`, prefer concrete open-item curation/recommendations over generic no-op rechecks.
+- Use `noOpRechecks` only when the finding says no backlog mutation is warranted after source inspection.
+- Historical hints and recommendation summaries may guide recommendations but are not standalone closure authority.
+- If reducer input diagnostics include `code: "reducer-input-protected-terminal-omitted"`, do not submit a normal complete/apply-ready curation that silently ignores them. Either emit top-level `decision: "needs-input"` split guidance that names every omitted item id and verdict from those diagnostics, or include `backlogCurationDraft.needsInput` rows that name every omitted item id and verdict from those diagnostics.
+- Protected terminal omission handling must be fully named. Do not use aggregate/unnamed split guidance for omitted shipped or superseded candidates.
+- Keep `skipped` exceptional. Use `needsInput` only for true product/user decisions that cannot be resolved from supplied summaries and findings, plus the named protected-terminal omission diagnostics above.
+- Recommendations must target the prospective post-curation backlog state. Do not recommend closed items or epics. Items whose current or same-draft prospective status is `active` belong only in `activeWork`; do not place active items in ready candidates, next sequence, safe-parallel groups, or blocked-chain target lanes.
+- `blockedChains[].blockedBy` accepts only known open backlog item ids. Do not put product-decision placeholders, questions, labels, or synthetic ids there; put those in `rationale`, `rationaleAndAssumptions`, `assumptionsOpenQuestions`, or draft `needsInput` instead.
+- Do not include raw evidence, raw item bodies, raw packets, raw `gitDelta`, or raw `fullImplementationAudit` text in the submission.
+
+Submit exactly once. Do not finish with prose. The submission tool is the only accepted output channel.

package/prompts/eforge-plan-planning-draft.md

@@ -0,0 +1,125 @@
+# eforge-plan Planning Draft Task
+
+You are drafting planning content for the first-party `eforge-plan` workstation. This is a daemon-owned, single-shot task. Do not use or request mutation-capable tools.
+
+## Task inputs
+
+- Planning goal (the request to plan for, not a title): {{topic}}
+- Session: {{session}}
+- Planning type: {{planningType}}
+- Planning depth: {{planningDepth}}
+- Requested output sections: {{requestedOutputSections}}
+- sessionPlanCreationReadiness:
+
+```json
+{{sessionPlanCreationReadiness}}
+```
+
+## Source text
+
+{{sourceText}}
+
+## Existing session plan
+
+{{existingSessionPlan}}
+
+## Progress reporting
+
+You MAY call `{{progressTool}}` before or after drafting each major session-plan section to report telemetry-only progress. Pass `currentSection`, `coveredSections`, and `remainingSections`, plus an optional short `message`. This reporting is advisory only: it never replaces the final submission, is not used to judge readiness, and does not affect whether the result can be applied. Reporting progress is optional and you may produce a complete result without ever calling it.
+
+## Optional Mermaid diagrams
+
+You MAY include fenced `mermaid` diagrams only when a diagram would clarify flows, dependencies, architecture, or sequencing. Mermaid diagrams are optional; do not include a diagram when prose or lists are clearer, and do not treat diagrams as required for every generated plan.
+
+## Output contract
+
+You MUST call `{{submitTool}}` exactly once with a JSON payload matching this schema:
+
+```yaml
+{{resultSchema}}
+```
+
+The payload MUST include:
+
+1. `summary` — concise human-readable summary of the proposed planning draft. For session-plan creation drafts, this becomes the persisted `## Executive Summary`; make it useful for fast scope review and sign-off without reading every readiness section. Specifically cover changed surfaces, intended direction, out-of-scope boundaries, and validation/build confidence.
+2. `assumptionsOpenQuestions` — an array of assumptions or open questions. Use an empty array only when there are truly none.
+3. Exactly one of the following result shapes:
+   - **A ready result** when you can produce the requested output. Include at least one applicable output section:
+     - `recommendations` for generated backlog recommendation model updates.
+     - `backlogCurationDraft` for structured backlog curation patches the extension may validate and apply later.
+     - `handoffDraft` or `handoffDrafts` for draft promotion selections the user may apply.
+     - `planDrafts` for eforge plan-file draft content.
+     - `sessionPlanPatch` for updates to an existing session plan.
+     - `planRevisionTurn` for an answer-only or patch-bearing revision turn against an existing session plan.
+     - When `sessionPlanCreationDraft` is requested, set `decision: "ready"` and include a `sessionPlanCreationDraft` object carrying `session`, `topic`, `planningType`, `planningDepth`, and one or more generated `sections`. `topic` MUST be a concise, human-readable plan title — a short noun phrase naming the work (for example, `Annotation-driven plan revisions`). Do NOT copy the planning goal verbatim and do NOT begin it with `Draft a session plan for`. `planningType` must be one of `bugfix`, `feature`, `refactor`, `architecture`, `docs`, `maintenance`, `unknown`; `planningDepth` must be one of `quick`, `focused`, `deep`. Optionally include `profile` (one of `errand`, `excursion`, `expedition`) and `agentProfile` (a string) when the appropriate planning profile or agent profile is known. Use `sessionPlanCreationDraft.sections[].dimension` and `skippedDimensions[].dimension` only for exact readiness dimension ids from the contract below.
+   - **A needs-input result** when you cannot produce a ready requested output. Set `decision: "needs-input"`, include a non-empty `clarificationQuestions` array of structured questions, and a `rationale` explaining what is blocking a ready draft. Do not emit `planRevisionTurn`, `sessionPlanPatch`, `sessionPlanCreationDraft`, or any other output section in this case.
+
+## Session-plan creation draft readiness guidance
+
+When the requested output sections include `sessionPlanCreationDraft`:
+
+- Read the `sessionPlanCreationReadiness` JSON. If `resolved` exists, copy `resolved.planningType` and `resolved.planningDepth` into the draft and use exactly `resolved.requiredDimensions` as the required readiness ids. If `resolved` is absent, choose `planningType` and `planningDepth`, then use the matching entry in `dimensionContract`.
+- For `sections[].dimension` and `skippedDimensions[].dimension`, use only exact kebab-case readiness dimension ids from the selected contract entry; cover or explicitly skip every required id. A skip must include a non-empty reason.
+- Do not submit display-heading aliases as dimension ids. Do not submit `Goal`, `Scope`, `Context and Evidence`, `Implementation Plan`, `Validation`, `Risks and Guardrails`, or other display headings as dimension ids.
+- If a ready draft cannot be produced using the exact ids, emit `needs-input` rather than submitting a not-ready creation draft.
+
+## Plan revision turn guidance
+
+When the requested output sections include `planRevisionTurn`:
+
+- Emit `planRevisionTurn` for bounded revision-session responses against the provided existing session plan.
+- Always copy the provided `basePlanFingerprint` exactly. If section hashes are provided, copy the relevant `baseSectionHashes` values exactly for sections you discuss or propose changing.
+- Use `assistantMessage` for the user-facing answer. Answer-only turns are valid: include `noPatchReason` when you are explaining, answering a question, or declining to propose edits.
+- For patch-bearing turns, include `proposedPatch.sections` entries with the target `dimension`, replacement `content`, and an optional `rationale`. Use structured edits only for sections you are proposing to change.
+- Use `proposedPatch.metadata.openQuestions` for open questions that can be carried with the proposal, and `proposedPatch.skippedDimensions` for dimensions you intentionally did not revise.
+- If a safe revision cannot be drafted without more user input, emit the top-level `needs-input` result instead of `planRevisionTurn`.
+- Do not claim that the session plan was modified, applied, saved, or persisted. This task only drafts an answer or structured proposal; the extension applies validated changes later.
+
+## Backlog curation guidance
+
+When the requested output sections include `backlogCurationDraft` in this generic single-shot task:
+
+- Preserve the provided `sourceFingerprint` exactly in the draft.
+- Emit structured `itemChanges`, `epicChanges`, `noOpRechecks`, `skipped`, and `needsInput` arrays. Use empty arrays when a category has no entries.
+- Every material entry in `itemChanges` and `epicChanges` must include a non-empty `rationale` explaining why the patch is safe and necessary.
+- Prefer `noOpRechecks: []`. Do not emit no-op rechecks just to prove every unchanged record was analyzed.
+- Emit a `noOpRechecks` entry only when the record is actually due for review (`stale_after` is before the source `generatedAt` date) or lacks freshness metadata, and the rationale adds useful freshness context. Keep these entries rare and focused.
+- For materially unchanged records that are already fresh, omit them from the draft entirely.
+- Treat `skipped` as exceptional, not normal: use it only for corrupt records, unavailable required source/context, or tooling failures that prevent review. For records that were investigated and should remain open without mutation, omit them from the draft and summarize the coverage instead. Use `needsInput` only for true product decisions that cannot be resolved from source, backlog context, or recommendation strategy.
+- Do not claim that backlog records were written or updated. This task only drafts structured output; the extension applies validated patches later.
+- Do not mark work shipped, superseded, or stale without durable evidence text in the relevant patch.
+- Treat `source.gitDelta.affectedItemCandidates` as deterministic range-aware context from the baseline git-delta scan. Use it to understand affected open items, matched signals, commit hashes, PR numbers, branch hints, changed paths, and bounded excerpts; do not invent evidence or infer a closed status from an affected candidate alone.
+- In `scanMode: "full-implementation-audit"`, this is an agentic source-first curation pass. Current source remains the closure authority for `shipped` and `superseded`, but ambiguous precomputed evidence is a lead to resolve, not a reason to skip. Use the full supplied item body, current-source excerpts, git/PR/lifecycle/session navigation hints, dependency details, roadmap context, and recommendation strategy to produce a complete ready-to-apply draft.
+- In source-first mode, closed-status patches must still be backed by current-source evidence from `source.fullImplementationAudit.sourceFirstResults` / `closureCandidates`; git history, PR metadata, lifecycle traces, branch hints, changed paths, and session-plan traces are navigation hints that help interpret source, not standalone closure authority.
+- Source-first shipped-status patches must cite a strong `source-shipped` result when one is supplied and evidence text must start exactly with `Shipped evidence: current source — ...`.
+- Source-first superseded-status patches must cite a strong `source-superseded` result when one is supplied and evidence text must start exactly with `Superseded evidence: current source — ...`.
+- If source-first evidence is partial, first decide whether the item can be updated forward instead of skipped: clarify remaining work in the item body, fix stale metadata, adjust priority/dependencies/tags, move it to the appropriate open status, or include it in recommendations as follow-up work. Keep items open when closure is not proven, but make the draft actionable.
+- Source-first evidence should include compact current-source citations for both core implementation/replacement and product-surface wiring (export, route/action registry, command registration, UI surface, provider registry, or package entrypoint) before proposing a closed status. If wiring is missing, keep the item open and patch the backlog record or recommendations toward the missing wiring work rather than emitting a generic skip.
+- Epic changes are allowed when they can be justified from backlog/item-level source-first findings, dependency state, roadmap context, or recommendation strategy. Do not emit epic skipped rows merely because source-first preview metadata is item-scoped.
+- Use `needsInput` only when a user/product decision is genuinely required after this investigation. Use `skipped` only for exceptional review failures such as corrupt records or missing required context.
+- Do not claim exhaustive validation unless the supplied source-first caps, diagnostics, and current-source citations explicitly support that wording.
+- `source.shippedEvidenceCandidates` may include compact lifecycle/git/PR historical navigation hints. In source-first curation these hints can guide investigation and recommendations, but they must not be used as standalone closed-status authority.
+- `source.shippedEvidenceCandidates[].evidenceSource` is one of `lifecycle`, `git-history`, `pr-history`, or `combined`.
+- Evidence entries for lifecycle-derived shipped patches must start exactly with `Shipped evidence: lifecycle trace — ...`.
+- Evidence entries for strong git/PR-inferred shipped patches must start exactly with `Shipped evidence: inferred from git/PR history — ...`.
+- Evidence entries for lifecycle-derived superseded patches must start exactly with `Superseded evidence: lifecycle trace — ...`.
+- Evidence entries for strong git/PR-inferred superseded patches must start exactly with `Superseded evidence: inferred from git/PR history — ...`.
+- Ambiguous shipped candidates are not enough for a shipped-status patch; route them to `needsInput` or `skipped` with evidence text that starts exactly with `Ambiguous shipped candidate: needs input — ...`.
+- Ambiguous superseded candidates are not enough for a superseded-status patch; route them to `needsInput` or `skipped` with evidence text that starts exactly with `Ambiguous superseded candidate: needs input — ...`.
+- Never convert ambiguous shipped or ambiguous superseded evidence into a closed-status patch, and never substitute a shipped prefix for superseded evidence or a superseded prefix for shipped evidence.
+
+## Recommendation guidance
+
+When emitting `recommendations`:
+
+- Generate recommendations against the prospective post-curation backlog state: apply the status changes you propose in `backlogCurationDraft` mentally before choosing recommendation targets.
+- Recommendation target fields may reference only open item/epic ids. Treat closed dependencies as satisfied historical context, not active recommendation targets.
+- Specifically, `activeWork`, `readyCandidates`, `recommendedNextSequence`, `safeParallelizableGroups.itemIds`, `safeParallelizableGroups.epicIds`, `blockedChains.itemIds`, and `blockedChains.blockedBy` may reference only open targets.
+- Same-draft recommendation exclusion: when your `backlogCurationDraft` proposes closing an item or epic (for example with `metadata.status: "shipped"`), do not include that item or epic id anywhere in generated recommendation target arrays in the same result.
+- Generate recommendations against the prospective post-curation backlog state, not the pre-curation state. If the same result includes a `backlogCurationDraft`, first mentally apply its recommendation-relevant metadata changes, then place recommendation targets.
+- Same-draft active items belong only in `activeWork`; do not also list them in `readyCandidates`, `recommendedNextSequence`, `safeParallelizableGroups.itemIds`, or `blockedChains.itemIds`.
+- Same-draft planned or candidate items belong in ready/next/group lanes when recommended. Do not place draft-planned or draft-candidate items in `activeWork` unless lifecycle evidence in the source shows they are already active, queued, building, or PR-open.
+- Place items that your same draft proposes as `active` only in `activeWork`, not in ready/next/group/blocking target lanes.
+- Place items that your same draft proposes as `planned` or `candidate` in `readyCandidates`, `recommendedNextSequence`, `safeParallelizableGroups.itemIds`, or appropriate blocking context rather than `activeWork`.
+
+Submit exactly once. Do not finish with prose. The submission tool is the only accepted output channel.

package/workstation-assets/plans/assets/abnfDiagram-VRR7QNED-78B0yOEK.js

@@ -0,0 +1 @@
+import{m as e,t}from"./mermaid-parser.core-Z7aCdDC3.js";import{n}from"./chunk-Y2CYZVJY-DsF7k-Jl.js";import{m as r}from"./src-YX8hbnqp.js";import"./chunk-WYO6CB5R-BlOpSQhB.js";import"./chunk-VAUOI2AC-BbIlIF2a.js";import{n as i,r as a,t as o}from"./chunk-MOJQB5TN-Dwkjcsly.js";import{t as s}from"./chunk-JWPE2WC7-DVXcaiue.js";var c=e().RailroadAbnf.parser.LangiumParser,l=n(e=>{let t=e.alternatives.map(u);return t.length===1?t[0]:{type:`choice`,alternatives:t}},`transformAlternation`),u=n(e=>{let t=e.elements.map(f);return t.length===1?t[0]:{type:`sequence`,elements:t}},`transformConcatenation`),d=n(e=>{if(e.includes(`*`)){let[t,n]=e.split(`*`);return{min:t?parseInt(t,10):0,max:n?parseInt(n,10):1/0}}let t=parseInt(e,10);return{min:t,max:t}},`parseRepeat`),f=n(e=>{let t=p(e.primary);if(!e.repeat)return t;let{min:n,max:r}=d(e.repeat);return n===0&&r===1?{type:`optional`,element:t}:{type:`repetition`,element:t,min:n,max:r}},`transformElement`),p=n(e=>{switch(e.$type){case`AbnfStringLiteral`:return{type:`terminal`,value:e.value};case`AbnfNumVal`:return{type:`terminal`,value:e.value};case`AbnfRuleName`:return{type:`nonterminal`,name:e.name};case`AbnfGroup`:return l(e.element);case`AbnfOptionalGroup`:return{type:`optional`,element:l(e.element)};default:throw Error(`Unsupported ABNF primary node: ${e.$type}`)}},`transformPrimary`),m=n(e=>({name:e.name,definition:l(e.definition)}),`transformRule`),h=n(e=>{s(e,o),e.title&&o.setTitle(e.title),e.rules.map(e=>o.addRule(m(e)))},`populateDb`),g={parser:{parse:n(e=>{o.clear(),r.debug(`[ABNF Parser] Starting Langium parse`);let n=c.parse(e);if(n.lexerErrors.length>0||n.parserErrors.length>0)throw new t(n);let i=n.value;r.debug(`[ABNF Parser] Parsed rules:`,i.rules.length),h(i),r.debug(`[ABNF Parser] Parse complete`)},`parse`),parser:{yy:o}},db:o,renderer:a,styles:i};export{g as diagram};

package/workstation-assets/plans/assets/arc-XmhKxjV7.js

@@ -0,0 +1 @@
+import{n as e,t}from"./path-BWPyau1x.js";import{a as n,c as r,d as i,f as a,i as o,l as s,m as c,n as l,o as u,p as d,r as f,u as p}from"./dist-BN7f1r-d.js";function m(e){return e.innerRadius}function h(e){return e.outerRadius}function g(e){return e.startAngle}function _(e){return e.endAngle}function v(e){return e&&e.padAngle}function y(e,t,n,r,i,a,o,s){var c=n-e,l=r-t,u=o-i,d=s-a,f=d*c-u*l;if(!(f*f<1e-12))return f=(u*(t-a)-d*(e-i))/f,[e+f*c,t+f*l]}function b(e,t,n,r,i,a,o){var c=e-n,l=t-r,u=(o?a:-a)/d(c*c+l*l),f=u*l,p=-u*c,m=e+f,h=t+p,g=n+f,_=r+p,v=(m+g)/2,y=(h+_)/2,b=g-m,x=_-h,S=b*b+x*x,C=i-a,w=m*_-g*h,T=(x<0?-1:1)*d(s(0,C*C*S-w*w)),E=(w*x-b*T)/S,D=(-w*b-x*T)/S,O=(w*x+b*T)/S,k=(-w*b+x*T)/S,A=E-v,j=D-y,M=O-v,N=k-y;return A*A+j*j>M*M+N*N&&(E=O,D=k),{cx:E,cy:D,x01:-f,y01:-p,x11:E*(i/C-1),y11:D*(i/C-1)}}function x(){var s=m,x=h,S=e(0),C=null,w=g,T=_,E=v,D=null,O=t(k);function k(){var e,t,m=+s.apply(this,arguments),h=+x.apply(this,arguments),g=w.apply(this,arguments)-r,_=T.apply(this,arguments)-r,v=l(_-g),k=_>g;if(D||=e=O(),h<m&&(t=h,h=m,m=t),!(h>1e-12))D.moveTo(0,0);else if(v>c-1e-12)D.moveTo(h*u(g),h*a(g)),D.arc(0,0,h,g,_,!k),m>1e-12&&(D.moveTo(m*u(_),m*a(_)),D.arc(0,0,m,_,g,k));else{var A=g,j=_,M=g,N=_,P=v,F=v,I=E.apply(this,arguments)/2,L=I>1e-12&&(C?+C.apply(this,arguments):d(m*m+h*h)),R=p(l(h-m)/2,+S.apply(this,arguments)),z=R,B=R,V,H;if(L>1e-12){var U=o(L/m*a(I)),W=o(L/h*a(I));(P-=U*2)>1e-12?(U*=k?1:-1,M+=U,N-=U):(P=0,M=N=(g+_)/2),(F-=W*2)>1e-12?(W*=k?1:-1,A+=W,j-=W):(F=0,A=j=(g+_)/2)}var G=h*u(A),K=h*a(A),q=m*u(N),J=m*a(N);if(R>1e-12){var Y=h*u(j),X=h*a(j),Z=m*u(M),Q=m*a(M),$;if(v<i)if($=y(G,K,Z,Q,Y,X,q,J)){var ee=G-$[0],te=K-$[1],ne=Y-$[0],re=X-$[1],ie=1/a(f((ee*ne+te*re)/(d(ee*ee+te*te)*d(ne*ne+re*re)))/2),ae=d($[0]*$[0]+$[1]*$[1]);z=p(R,(m-ae)/(ie-1)),B=p(R,(h-ae)/(ie+1))}else z=B=0}F>1e-12?B>1e-12?(V=b(Z,Q,G,K,h,B,k),H=b(Y,X,q,J,h,B,k),D.moveTo(V.cx+V.x01,V.cy+V.y01),B<R?D.arc(V.cx,V.cy,B,n(V.y01,V.x01),n(H.y01,H.x01),!k):(D.arc(V.cx,V.cy,B,n(V.y01,V.x01),n(V.y11,V.x11),!k),D.arc(0,0,h,n(V.cy+V.y11,V.cx+V.x11),n(H.cy+H.y11,H.cx+H.x11),!k),D.arc(H.cx,H.cy,B,n(H.y11,H.x11),n(H.y01,H.x01),!k))):(D.moveTo(G,K),D.arc(0,0,h,A,j,!k)):D.moveTo(G,K),!(m>1e-12)||!(P>1e-12)?D.lineTo(q,J):z>1e-12?(V=b(q,J,Y,X,m,-z,k),H=b(G,K,Z,Q,m,-z,k),D.lineTo(V.cx+V.x01,V.cy+V.y01),z<R?D.arc(V.cx,V.cy,z,n(V.y01,V.x01),n(H.y01,H.x01),!k):(D.arc(V.cx,V.cy,z,n(V.y01,V.x01),n(V.y11,V.x11),!k),D.arc(0,0,m,n(V.cy+V.y11,V.cx+V.x11),n(H.cy+H.y11,H.cx+H.x11),k),D.arc(H.cx,H.cy,z,n(H.y11,H.x11),n(H.y01,H.x01),!k))):D.arc(0,0,m,N,M,k)}if(D.closePath(),e)return D=null,e+``||null}return k.centroid=function(){var e=(+s.apply(this,arguments)+ +x.apply(this,arguments))/2,t=(+w.apply(this,arguments)+ +T.apply(this,arguments))/2-i/2;return[u(t)*e,a(t)*e]},k.innerRadius=function(t){return arguments.length?(s=typeof t==`function`?t:e(+t),k):s},k.outerRadius=function(t){return arguments.length?(x=typeof t==`function`?t:e(+t),k):x},k.cornerRadius=function(t){return arguments.length?(S=typeof t==`function`?t:e(+t),k):S},k.padRadius=function(t){return arguments.length?(C=t==null?null:typeof t==`function`?t:e(+t),k):C},k.startAngle=function(t){return arguments.length?(w=typeof t==`function`?t:e(+t),k):w},k.endAngle=function(t){return arguments.length?(T=typeof t==`function`?t:e(+t),k):T},k.padAngle=function(t){return arguments.length?(E=typeof t==`function`?t:e(+t),k):E},k.context=function(e){return arguments.length?(D=e??null,k):D},k}export{x as t};

package/workstation-assets/plans/assets/architecture-TIHT7OUA-NvwveMWr.js

@@ -0,0 +1 @@
+import"./chunk-KEIR6QF5-Dj-OpFgW.js";import{M as e}from"./mermaid-parser.core-Z7aCdDC3.js";export{e as createArchitectureServices};