[JUM-905][Fix] Dark canvas, sidebar and anchored mini-map on the Architecture tab

[web2solutions]

Summary

The Architecture tab now renders on the designer's dark surfaces: its canvas and sidebar no longer resolve --jtx-surface to white, and its mini-map overlays the canvas instead of falling below it as a white strip. Links now join the facing card edges at mid-height instead of running through both titles, and the link list names services instead of internal ids (service-import-2).

Problem Statement

Measured in the running app (1440×900): #architecture-canvas computed background-color: rgb(255, 255, 255) and the sidebar rgb(255, 255, 255) — the designer is dark by its own literal palette and never sets :root.dark, so --jtx-surface stays #ffffff. .architecture-mini-map { position: relative; height: 80px } overrode .mini-map's absolute anchoring.

• Related issue(s): JUM-905
• Related PR(s): none
• Related check run(s): none yet

Project Tracking (Required)

• Linear Project: Jumentix (https://linear.app/jumentix)
• Focused epic link: https://linear.app/jumentix/project/epicdocs-unified-jumentix-documentation-9981763642b6
• Epic milestone: Audience-clean docs and refreshed website visuals — 2026-10-31
• Primary task nature: fix
• Epic-delegated agent ID: claude-code-opus5-001
• Child task issue link: https://linear.app/jumentix/issue/JUM-905/fix-architecture-tab-renders-a-white-canvas-and-an-unanchored-mini-map
• Project Update: https://linear.app/jumentix/project/epicdocs-unified-jumentix-documentation-9981763642b6/activity#project-update-1238dbd9
• Linear Project link(s): https://linear.app/jumentix/project/epicdocs-unified-jumentix-documentation-9981763642b6
• Linear Issue link(s): https://linear.app/jumentix/issue/JUM-905/fix-architecture-tab-renders-a-white-canvas-and-an-unanchored-mini-map
• Linear Issue ID list (comma separated): JUM-905
• Item status at PR creation: In Progress
• Target cycle (Start date -> End date): 2026-09-26 -> 2026-09-29
• Priority group for this PR (P0 / P1 / P2): P2
• This PR contains tasks from only one priority group.

Branch Promotion Path (Required)

• Source branch: claude/fix/JUM-905-architecture-canvas-dark
• Target branch: dev
• Required PR title format: [JUM-XXXX][Nature] <concise outcome>
• The leading JUM-XXXX matches the single Linear Issue declared above.
• This task PR targets dev.
• If this PR targets main, it is a release promotion sourced from dev, references the task PRs/issues already merged into dev, and introduces no unreviewed changes.
• This PR is not a direct task/topic branch promotion to main.

Bidirectional Traceability (Required)

• Every linked issue already contains this PR URL.
• Every linked issue already contains commit hash/range evidence.
• PR description includes mapping of task -> commit(s).
• Task -> commit(s) mapping:
  • JUM-905: cb75239, 7e892ff

Scope of Change

Domain / Business Rules

• None.

Application / Use Cases

• None.

Adapters / Infrastructure

• apps/service-management/styles.css: architecture canvas uses the Domain Designer canvas colour and grid; sidebar uses the Domain Designer sidebar colour; .architecture-shell .canvas-workspace { position: relative }; mini-map styled as the Domain Designer overlay.
• apps/service-management/test/unit/architectureCanvasTheme.test.ts: style contract (3 tests).
• apps/service-management/src/ui/architectureCanvas.js: architectureLinkGeometry / architectureLinkLabel (exported, pure) used by the canvas and the link list.

API / Contracts (OpenAPI, DTOs, handlers, controllers)

• None.

Detailed Technical Changes

Found while capturing JUM-896 screenshots; verified visually by injecting the rules into the running app before committing. Component owner (kimi-code-primary-001, Req 126) holds accountability, not exclusive edit rights (.agents/COMPONENT-OWNERSHIP.md).

Architecture and Design Alignment

• Domain logic remains inside domain/application layers.
• Controllers/handlers do not instantiate repositories/services directly.
• Ports/adapters boundaries are respected.
• No new circular dependencies introduced.
• Event publishing/listening flow remains consistent.

Security Impact

• Security impact: No security impact.
• Secrets handling reviewed: [ ] Yes [ ] No [x] N/A
• Input/output sanitization reviewed: [ ] Yes [ ] No [x] N/A
• AuthN/AuthZ impact: [ ] Yes [x] No
• Data exposure risk (password/salt/token/PII): [ ] Yes [x] No
• Sonar security findings addressed or unaffected: [x] Yes [ ] No

Data and Migration Impact

• Data model impact: none.
• Migration required: [ ] Yes [x] No
• Rollback strategy: revert the PR.

Breaking Changes

None.

Acceptance Criteria

• Feature/bug behavior matches expected functional outcome.
• Error paths and edge cases are covered.
• API contract changes (if any) are documented and validated.
• Architecture boundaries remain enforced.
• No regression in existing workflows.

Test Plan (Evidence)

• bun test apps/service-management/test/unit/architectureCanvasTheme.test.ts — 5 pass
• bun run test:unit — task gate: Tests: 2204 passed, 2204 total

Extra evidence:

getComputedStyle(#architecture-canvas).backgroundColor → rgb(255, 255, 255)   # before
rgb(7, 7, 7)                                                              # after

Feedback Resolution (Required)

• Every GitHub review thread is resolved natively.
• Every general comment has a visible resolution response by the PR author or a repository maintainer.
• Each resolution response uses exactly one marker and, for resolved, a SHA from this PR.

Coverage

• Project coverage >= 95%: [x] Yes [ ] No
• Patch coverage >= 95%: [x] Yes [ ] No
• Codecov status passing: [ ] Yes [ ] No (pending CI)

SonarQube Cloud

• Quality Gate passing: [ ] Yes [ ] No (pending CI)
• New vulnerabilities introduced: [ ] Yes [x] No
• New security hotspots reviewed: [ ] Yes [ ] No [x] N/A

Performance / Reliability Impact

No measurable impact.

Observability

• Logs updated: [ ] Yes [x] No
• Metrics/Tracing updated: [ ] Yes [ ] No [x] N/A

Deployment and Rollout

• Deployment notes: none.
• Feature flag needed: [ ] Yes [x] No
• Rollout strategy: merge to dev, promote with the next release.
• Rollback steps: revert the PR.

Risks and Mitigations

1. Risk: none material.\n Mitigation: n/a.

Documentation Updates

• README updated (if needed)
• Additional docs updated (if needed)
• Changelog untouched; GitHub Actions synchronizes it only after the validated main merge

Reviewer Checklist

• Changes are clear and scoped.
• Acceptance criteria are testable and satisfied.
• Tests are sufficient for risk level.
• Security and data impacts are addressed.
• CI checks pass fully.

🤖 Generated with Claude Code

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3a86d051-0397-4080-ae8e-64c3c436c47b)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_b6edf2be-452d-4393-88be-d5bc174c8df3)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_dece22e9-5169-4e76-9c34-74e19901a442)