spec: finalize wealth-ledger SDD migration

openspec/schemas/wealth-ledger-sdd-v2/templates/design.md

@@ -0,0 +1,67 @@
+# Engineering Design
+
+## Context and Constraints
+
+## Technical Goals / Non-Goals
+
+## Implementation Impact Map
+
+### main
+
+### frontend
+
+### backend
+
+### qa
+<!-- Use only after a real QA/E2E repository exists. -->
+
+## Decisions
+
+### main
+
+### frontend
+
+### backend
+
+### qa
+
+## Cross-cutting Implementation
+
+## Data / Storage Changes
+
+## Contract Implementation
+
+## Developer Verification Strategy
+
+## UI/UX Package
+
+<!-- Choose new/changed, reuse or N/A with reason. For applicable UI include
+     package revision, screens, states, interactions, responsive/a11y behavior.
+     For reuse give immutable store ID + path from OpenSpec root, reused part
+     and differences. Keep materials accessible after archive. Inline Markdown
+     needs no self-hash; mutable external-only URLs are not an approved package. -->
+
+**Applicability and scope:**
+
+**Package revision:**
+
+**Screens, states and interactions:**
+
+**Responsive behavior:**
+
+**Reused source and differences:**
+
+<!-- If local PNG/SVG exports are needed, list each under visuals/ with a
+     relative path, purpose and SHA-256. SVG must be self-contained (no scripts,
+     handlers, external fonts/assets). Otherwise remove the table and state
+     that the package is fully inline. One Design approval covers all materials. -->
+
+| Material ID | Relative path | Screen/state and purpose | SHA-256 |
+| --- | --- | --- | --- |
+| <!-- id --> | <!-- visuals/file.png --> | <!-- purpose --> | <!-- digest --> |
+
+## Risks / Trade-offs
+
+## Migration / Rollout / Rollback
+
+## Solution Assessment

openspec/schemas/wealth-ledger-sdd-v2/templates/docs-impact.md

@@ -0,0 +1,16 @@
+# Documentation Impact
+
+## Summary
+
+## Documentation Changes
+
+| Action | Target | Category | Resulting AS-IS | Source | Verification |
+|---|---|---|---|---|---|
+
+## Diagram Promotion
+
+## ADR Decision
+
+## Glossary / Navigation Impact
+
+## No-Change Rationale

openspec/schemas/wealth-ledger-sdd-v2/templates/proposal.md

@@ -0,0 +1,23 @@
+# Proposal
+
+## Why
+
+## What Changes
+
+## Scope
+
+### In Scope
+
+### Out of Scope / Non-Goals
+
+## Capabilities
+
+### New Capabilities
+
+### Modified Capabilities
+
+## Impact
+
+## Success Criteria
+
+## Assumptions / Dependencies

openspec/schemas/wealth-ledger-sdd-v2/templates/qa-analysis.md

@@ -0,0 +1,25 @@
+# QA Analysis
+
+## Verification Scope
+
+### In Scope
+
+### Out of Scope
+
+## Coverage Matrix
+
+## Cross-system Verification
+
+## Risk-based Priorities
+
+## Test Data and Environment Needs
+
+## Manual / Exploratory Scope
+
+## Automation Candidates
+
+## Observability Verification
+
+## Regression Impact
+
+## Gaps / Blockers

openspec/schemas/wealth-ledger-sdd-v2/templates/spec.md

@@ -0,0 +1,18 @@
+<!--
+Choose only the sections this delta needs; delete this guide before approval.
+
+New capability only: add `## Purpose` with 1–2 sentences (50+ characters).
+Existing capability: do not add Purpose.
+
+Supported operations:
+- `## ADDED Requirements`: new complete Requirement blocks.
+- `## MODIFIED Requirements`: full existing Requirement blocks with every
+  surviving Scenario, then edited behavior; heading matches exactly.
+- `## REMOVED Requirements`: Requirement heading plus **Reason** and **Migration**.
+- `## RENAMED Requirements`: `FROM:` and `TO:` heading pairs only.
+
+Every normative Requirement uses BCP 14 (RFC 2119 + RFC 8174) uppercase
+SHALL/MUST deliberately, and at least one `#### Scenario:` with `- **WHEN**`
+and `- **THEN**`. Lowercase must/should/may are ordinary language.
+Do not leave empty operation sections or a sample Requirement.
+-->

openspec/schemas/wealth-ledger-sdd-v2/templates/system-analysis.md

@@ -0,0 +1,27 @@
+# System Analysis
+
+## Requirement Coverage
+
+## Systems and Responsibilities
+
+## Interaction Flows
+
+<!-- Store Mermaid sequence sources in system-analysis/sequences/*.mmd -->
+
+## Contracts
+
+<!-- Store OpenAPI/AsyncAPI/Proto/JSON Schema in system-analysis/contracts/ -->
+
+## Data and State Semantics
+
+## Error and Recovery Semantics
+
+## Observability Semantics
+
+## Security and NFR at System Boundaries
+
+## Compatibility / Migration
+
+## Durable Documentation Candidates
+
+## Open Questions

openspec/schemas/wealth-ledger-sdd-v2/templates/tasks.md

@@ -0,0 +1,9 @@
+# Tasks
+
+## 1. <delivery phase>
+
+- [ ] 1.1 [backend] <action + independently reviewable outcome>
+  - **Covers:** `N/A` — <reason or exact capability/requirement>
+  - **Source:** <approved artifact section>
+  - **Verification:** <command / observable check / delivered artifact>
+  - **Depends on:** none