|
| 1 | +# calm-suite — Deployment Reconciliation TODO |
| 2 | + |
| 3 | +> **For the agent/owner wiring up calm-suite deployments.** |
| 4 | +> |
| 5 | +> Context: `calm-suite` (CALM Guard + CALM Studio) was contributed to FINOS and now |
| 6 | +> lives in `finos/architecture-as-code`. A separate pass |
| 7 | +> (`chore/reconcile-calm-suite-ownership`) corrected **ownership/repository |
| 8 | +> pointers** (package metadata, repo links, license links, CI badges, Docusaurus |
| 9 | +> `organizationName`/`projectName`) to `finos/architecture-as-code`. |
| 10 | +> |
| 11 | +> That pass deliberately **left deployment-specific values alone**, because new |
| 12 | +> deployment plans are in flight and those values are yours to set. They are |
| 13 | +> listed here so they don't get lost. Each still points at OpsFlow's old, |
| 14 | +> now-defunct infrastructure. |
| 15 | +
|
| 16 | +## Items left untouched (need a deployment decision) |
| 17 | + |
| 18 | +### 1. CALM Guard docs site — Docusaurus deploy URL |
| 19 | +**File:** `calm-suite/calm-guard/docs/docusaurus.config.ts` (lines 17–18) |
| 20 | + |
| 21 | +```ts |
| 22 | +url: 'https://finos-labs.github.io', |
| 23 | +baseUrl: '/dtcch-2026-opsflow-llc/', |
| 24 | +``` |
| 25 | + |
| 26 | +`organizationName`/`projectName` in the same file were already repointed to |
| 27 | +`finos`/`architecture-as-code`. These two URL fields define where the site |
| 28 | +actually publishes and were left for the deployment decision (GitHub Pages under |
| 29 | +`finos/architecture-as-code`, an S3/`calm.finos.org` sub-path, or elsewhere). Set |
| 30 | +them consistently with the corrected org/project. |
| 31 | + |
| 32 | +### 2. CALM Studio VS Code extension — Marketplace publisher |
| 33 | +**File:** `calm-suite/calm-studio/packages/vscode-extension/package.json` (line 3) |
| 34 | + |
| 35 | +```json |
| 36 | +"publisher": "opsflow", |
| 37 | +``` |
| 38 | + |
| 39 | +This is the VS Code Marketplace publisher identity — changing it requires an owned |
| 40 | +Marketplace publisher account, so it's a publishing decision, not a metadata |
| 41 | +rename. For reference, the other FINOS VS Code extension |
| 42 | +(`calm-plugins/vscode`) ships under publisher `"FINOS"`. |
| 43 | + |
| 44 | +### 3. CALM Studio web app — hardcoded fallback URL |
| 45 | +**Files:** |
| 46 | +- `calm-suite/calm-studio/packages/vscode-extension/src/openInStudio.ts` (line 22) |
| 47 | +- `calm-suite/calm-studio/packages/vscode-extension/src/test/openInStudio.test.ts` (line 72) |
| 48 | + |
| 49 | +`openInCalmStudio()` hardcodes `https://calmstudio.opsflow.io` as the web fallback |
| 50 | +when the desktop app isn't installed (no env-var override today). That deployment |
| 51 | +is OpsFlow's. Update the fallback URL — and the matching test assertion — to the |
| 52 | +new canonical Studio deployment URL once it exists. |
| 53 | + |
| 54 | +## NOT stale — do NOT change |
| 55 | + |
| 56 | +These reference a real, separate FINOS-Labs project (AIGF reference patterns), not |
| 57 | +the old hackathon repo: |
| 58 | +- `calm-suite/calm-studio/packages/mcp-server/src/tools/guide.ts:130,259` |
| 59 | +- `calm-suite/calm-studio/docs/REQ_fluxnova_aigf_integration.md:27` |
| 60 | + |
| 61 | +→ all point at `finos-labs/ai-reference-architecture-library`, which is correct. |
| 62 | + |
| 63 | +## Intentionally kept (historical attribution — do NOT "fix") |
| 64 | + |
| 65 | +Legitimate provenance/credit, not an ownership claim: |
| 66 | +- `calm-suite/calm-guard/README.md:61` — link to the hackathon presentation PDF |
| 67 | +- `calm-suite/calm-guard/README.md:463` — "Built for DTCC/FINOS Innovate.DTCC AI Hackathon 2026" |
| 68 | +- `calm-suite/calm-guard/docs/docs/intro.md:65` — "built by Team OpsFlow at the DTCC/FINOS Innovate AI Hackathon" |
| 69 | +- `calm-suite/calm-studio/docs/CALM_1.2_CONTROLS_SCHEMA.md:436` — ecosystem-layering prose mentioning CalmSentry/OpsFlow |
0 commit comments