[Track A] Structural cleanup of calm-suite (no behaviour change)

# [Track A] Structural cleanup of calm-suite (no behaviour change)

_Sub-task of #2600 — Track A._

## Goal

Land the lowest-risk structural cleanup of the `calm-suite/` contribution: remove vestigial config, hackathon artefacts, promote `calm-guard`/`calm-studio` to top-level workspaces, and unify tooling — **with no behaviour change**.

## Scope (A1–A5 from #2600)

- [ ] **A1.** Delete vestigial config: dead `calmstudio-workspace` package.json, `@calmstudio/calmscript` stub, per-package `.releaserc.json` files, and `vercel.json`. Replace deep relative `file:` deps with bare workspace resolution.
- [ ] **A2.** Remove hackathon artefacts:
- `docs/docs/calm-studio/adrs/*`
- `calm-suite/calm-studio/docs/{AIGF_CATALOGUE.json, CALM_1.2_CONTROLS_SCHEMA.md, REQ_fluxnova_aigf_integration.md}`
- Bundled demo architectures: `examples/*`, `apps/studio/static/demos/*`
- **Retain** genuine user docs under `docs/docs/calm-studio/` (folded into D1)
- [ ] **A3.** `git mv calm-guard` and `calm-studio` to top level. Update:
- Root `workspaces` globs
- CI workflow paths
- `repository.directory` fields
- Remove `calm-suite/`
- [ ] **A4.** Reconcile remaining identities to FINOS:
- In-app "Report an issue" link → `finos/architecture-as-code`
- Docs deploy URL
- Remove `DEPLOYMENT-RECONCILIATION.md` once actioned
- [ ] **A5.** Unify tooling: single husky/commitlint/lint-staged at root; align vitest/eslint/vite; one coverage gate.

## Why this first

Per #2600 critical path: Track A → B1 → B2 → B3 → B4. A is no-behaviour-change and unblocks every downstream track by collapsing the directory layout and removing dead config that would otherwise compound conflicts in B and C.

## Out of scope

- Capability convergence (Track B)
- Studio behaviour changes (Track C)
- Docs site consolidation (Track D — D1 picks up A2-retained user docs)

## Acceptance criteria

- `calm-suite/` directory removed; `calm-guard/` and `calm-studio/` are top-level workspaces
- All workspaces resolve via bare names (no `file:../../../`)
- Single root tooling regime (husky/commitlint/lint-staged/vitest/eslint)
- `npm run build` and `npm test` pass at root with no behaviour change
- CI workflows reference new paths
- No vestigial config, no hackathon artefacts

## References

- Parent: #2600
- Depends on: none (lowest-risk, can start immediately)
- Blocks: Track B (B1–B4), Track C (C2 onward), Track D