finos/architecture-as-code

Bug Report Steps to Reproduce: Build @calmstudio/diagram (calm-studio/packages/web-component). Call renderELKDiagram(arch, { flow: 'f' }) from dist/render.cjs, where arch has a flow that is valid for CALM 1.2: { "nodes": [ { "unique-id": "a", "node-type": "service", "name": "A", "description": "A" }, { "unique-id": "b", "node-type": "service", "name": "B", "description": "B" } ], "relationships": [ { "unique-id": "a-to-b", "relationship-type": { "connects": { "source": { "node": "a" }, "destination": { "node": "b" } } } } ], "flows": [ { "unique-id": "f", "name": "F", "description": "F", "transitions": [{ "relationship-unique-id": "a-to-b", "sequence-number": 1, "description": "A calls B" }] } ] } The same happens for <CalmDiagram src="..." flow="f" /> in the docs site. Expected Result: The diagram renders with the flow overlay. Each badge tooltip shows the transition description. Actual Result: TypeError: Cannot read properties of undefined (readin

Feature Proposal Target Project: calm-hub-ui, with small changes in calm-hub. Description of Feature: A node can point to a more detailed architecture with details.detailed-architecture. When that reference points to a document in the same CALM Hub instance, CALM Hub must open that document in the visualiser. This must work for every architecture in the Hub, and for every URL that users use to open the UI. Two parts of this are done: The UI drill-down, the breadcrumbs and the broken-reference view shipped in #2799 and #2841 (#2616). The user-facing API (#2653) makes $id equal to the canonical URL {calm.hub.base-url}/calm/namespaces/{ns}/{type}/{name}/versions/{version}. This issue covers the gaps that remain between the two. It supersedes #2581. User Stories: As an architect, I want to open the detailed architecture of a node in CALM Hub, so that I can move through a layered design without leaving the tool. As a platform owner, I want CALM Hub to identify its own documents by its co

Feature Proposal Target Project: calm-lab Description of Feature: Replace the custom terminal in calm-lab/src/lab/Terminal.tsx with xterm.js, so that the lab shows real CLI output such as ANSI colour. This is item 2 of #3206. User Stories: As a learner, I want the lab terminal to look and act like a real terminal, so that what I learn transfers to the CLI on my machine. Current Limitations: Terminal.tsx is one input line with command history, tab completion and paste. It renders each output line as plain text, so it cannot show colour. Proposed Implementation: Use xterm.js. Lazy-load it, so the lab chunk stays small. Keep the TerminalProps contract with src/shell.ts (cwd, onRun, onComplete, chromeless), command history, tab completion and paste. Turn on the xterm.js screenReaderMode option. Screen readers can read the current terminal because it is plain DOM text. xterm.js output needs this option to give the same result. Keep the terminal readable in light and dark mode. Alternative

Feature Proposal Target Project: calm-lab Description of Feature: Replace the <textarea> in calm-lab/src/lab/Editor.tsx with CodeMirror 6, with CALM schema autocomplete and inline validation errors. This is item 1 of #3206. User Stories: As a learner, I want autocomplete and inline errors in the editor, so that I learn the CALM schema while I type. Current Limitations: The editor is a <textarea> with a line-number gutter and a regex highlight overlay (tokenizeJson). It has no autocomplete, and validation errors show only in the terminal. Proposed Implementation: Use CodeMirror 6 with its JSON language package. Get autocomplete and errors from the CALM meta-schemas that the lab bundles (src/schemas.ts). Do not fetch schemas at run time. Lazy-load the editor, so the lab chunk stays small. Keep the EditorProps contract (value, dirty, onChange, onSave, chromeless), Cmd/Ctrl+S to save, Tab to indent, and light and dark mode. Alternatives Considered: Monaco. It is much larger, and the lab

Bug Report Steps to Reproduce: Use the two documents from #3210: b.json adds a second ADR, changes the security control config-url, and changes the metadata owner. Run calm diff -a a.json -b b.json -f summary. Expected Result: The summary lists which ADRs and controls changed, the same way it lists node and relationship IDs under Nodes added: etc. Actual Result: Since #3213, the summary shows only counts: Nodes: +0 -0 ~0 ↔0 =1 Relationships: +0 -0 ~0 ↔0 =0 ADRs: +1 -0 =1 Controls: +0 -0 ~1 Metadata: +1 -1 ~0 A CI log shows that a control changed, but not which one. Environment: upstream/main (4d875eb), Node 26, macOS. Additional Context: Add ADRs added: / ADRs removed: (ADR content) and Controls added: / Controls removed: / Controls modified: (control IDs) lists in formatDiff in shared/src/commands/diff/diff-core.ts, after Relationships renamed:. Metadata items have no ID, so the count line is enough. Test gap: the diffDocuments cases in