chore(repo): initial baseline import (docs v0.9.2 + bootstrap)

Imports the v0.9.2 documentation baseline and the bootstrap files required by docs/governance/repository-bootstrap-plan.md v0.1.0 §3, minus the justfile (added in the next commit). This commit establishes the git history for the project. All previous work lived only as filesystem state with no version control.
2026-05-14 12:25:33 +08:00
commit f1bc9a6c85
51 changed files with 14510 additions and 0 deletions
@@ -0,0 +1,375 @@
+
+# Chanora SWE.4 Software Unit Verification Plan
+
+**Document type:** Software Unit Verification Plan  
+**Process alignment:** ASPICE SWE.4 Software Unit Verification  
+**Version:** 0.9.2
+**Status:** Baseline Candidate  
+**Language:** English  
+**Product:** Chanora  
+**Verification object:** Software units defined by SDD  
+**Direct source layer:** SDD only  
+
+**Repo path:** `docs/verification/swe4-unit-verification-plan.md`  ---
+
+## 1. Purpose
+
+This document defines the software unit verification strategy for Chanora. It verifies that software units implement the Software Detailed Design.
+
+This document is downstream of SDD and shall not bypass the document hierarchy.
+
+```text
+SysRS -> SysDes -> SRS -> SAD -> SDD -> SWE.4 Unit Verification
+```
+
+Direct source rule:
+
+```text
+SWE.4 unit verification items shall link directly to SDD only.
+```
+
+## 2. Verification Scope
+
+In scope:
+
+- Flutter unit tests
+- Flutter widget-level unit verification where a widget is treated as a software unit
+- Dart static analysis
+- Dart code review
+- Rust unit tests
+- Rust static analysis
+- Rust code review
+- Unit-level regression verification
+- Unit-level interface boundary tests
+- Unit-level localization, Unicode, design-token, and diagnostics verification
+
+Out of scope:
+
+- Software integration verification across components; handled by SWE.5.
+- Fully integrated software verification against SRS; handled by SWE.6.
+- System integration verification against SysDes; handled by SYS.4.
+
+## 3. Unit Verification Strategy
+
+| Verification type | Applies to | Purpose |
+|---|---|---|
+| Static analysis | Dart, Rust | Detect structural, lint, safety, style, and maintainability issues |
+| Code review | Dart, Rust, build scripts | Confirm design compliance and maintainability |
+| Unit tests | Dart, Rust | Verify individual units against SDD behavior |
+| Widget tests | Flutter widgets | Verify component rendering, semantics, and state behavior |
+| Golden tests | Design-system components | Verify stable UI rendering where appropriate |
+| Localization tests | Localization service and accessibility labels | Verify fallback, keys, and localized display strings |
+| Unicode tests | Protocol/bridge/text-boundary units | Verify UTF-8 and multilingual content handling |
+| Regression tests | Changed units | Confirm unchanged behavior remains valid after modifications |
+
+## 4. Entry Criteria
+
+| Criterion | Description |
+|---|---|
+| SDD baseline available | Unit design items and source SAD links are available. |
+| Unit implementation available | The unit exists in source code or executable test double form. |
+| Unit test environment available | Flutter and/or Rust test infrastructure is configured. |
+| Verification measure defined | Test, review, or static analysis objective is defined. |
+| Pass/fail criteria defined | Expected result is objective and reviewable. |
+
+## 5. Exit Criteria
+
+| Criterion | Description |
+|---|---|
+| Selected unit verification measures executed | Tests, reviews, and analyses required for the release scope are complete. |
+| Results recorded | Verification results are stored in test reports or review records. |
+| Nonconformances recorded | Failures are recorded for problem resolution. |
+| Traceability complete | Each unit verification item traces to SDD and result evidence. |
+| Regression scope complete | Changed units have selected regression measures executed. |
+
+## 6. Unit Verification Measures
+
+**SWE4-UV-001**: Verify `ChanoraApp` initialization order.
+
+- Source SDD: SDD-001, SDD-045
+- Verification method: Flutter unit/integration test
+- Pass criteria: Theme, localization, platform services, routing, and adaptive shell initialize before feature rendering.
+- Evidence: Test result
+
+**SWE4-UV-002**: Verify `ChanoraThemeFactory` Material 3 theme creation.
+
+- Source SDD: SDD-002, SDD-003
+- Verification method: Dart unit test
+- Pass criteria: Light and dark Material 3 ThemeData objects are created with valid ColorScheme and TextTheme values.
+- Evidence: Test result
+
+**SWE4-UV-003**: Verify `ChanoraSemanticColors` connection token behavior.
+
+- Source SDD: SDD-004, SDD-006
+- Verification method: Dart unit test
+- Pass criteria: All connection semantic roles are present and do not require feature-screen hardcoding.
+- Evidence: Test result
+
+**SWE4-UV-004**: Verify voice semantic token behavior.
+
+- Source SDD: SDD-005, SDD-006
+- Verification method: Dart unit test
+- Pass criteria: Speaking, muted, deafened, and push-to-talk active states are available through semantic tokens.
+- Evidence: Test result
+
+**SWE4-UV-005**: Verify feature widgets use theme accessors rather than hardcoded semantic values.
+
+- Source SDD: SDD-010
+- Verification method: Static inspection
+- Pass criteria: Feature widgets do not construct product semantic token values directly.
+- Evidence: Review record
+
+**SWE4-UV-006**: Verify adaptive shell window classification.
+
+- Source SDD: SDD-011, SDD-012
+- Verification method: Dart unit test
+- Pass criteria: Compact, medium, and expanded classes are selected deterministically.
+- Evidence: Test result
+
+**SWE4-UV-007**: Verify `CompactShell` layout behavior.
+
+- Source SDD: SDD-013
+- Verification method: Flutter widget test
+- Pass criteria: Compact shell renders a single-column layout and mobile navigation entry points.
+- Evidence: Test result
+
+**SWE4-UV-008**: Verify `MediumShell` layout behavior.
+
+- Source SDD: SDD-014
+- Verification method: Flutter widget test
+- Pass criteria: Medium shell renders side navigation or navigation rail behavior.
+- Evidence: Test result
+
+**SWE4-UV-009**: Verify `ExpandedShell` persistent pane behavior.
+
+- Source SDD: SDD-015
+- Verification method: Flutter widget test
+- Pass criteria: Expanded shell renders persistent side pane and VoiceBar slot.
+- Evidence: Test result
+
+**SWE4-UV-010**: Verify connection status presentation uses non-color-only cues.
+
+- Source SDD: SDD-016, SDD-022
+- Verification method: Dart unit test, widget test
+- Pass criteria: The presenter exposes label, icon, semantic label, and severity token.
+- Evidence: Test result
+
+**SWE4-UV-011**: Verify `ChanoraVoiceBar` exposed properties.
+
+- Source SDD: SDD-017, SDD-018
+- Verification method: Flutter widget test
+- Pass criteria: Mute, deaf, push-to-talk, input meter, current channel, and latency properties render correctly.
+- Evidence: Test result
+
+**SWE4-UV-012**: Verify `ChanoraChannelTree` data and interaction behavior.
+
+- Source SDD: SDD-019, SDD-020
+- Verification method: Flutter widget test
+- Pass criteria: Channel hierarchy, selected state, expansion state, join intent, and context-menu intent operate as designed.
+- Evidence: Test result
+
+**SWE4-UV-013**: Verify `ChanoraClientTile` state semantics.
+
+- Source SDD: SDD-021
+- Verification method: Widget test, accessibility test
+- Pass criteria: Client status is available through text/icon/semantic cues and not color alone.
+- Evidence: Test result
+
+**SWE4-UV-014**: Verify localized semantic labels for icon-only buttons.
+
+- Source SDD: SDD-024, SDD-031, SDD-032
+- Verification method: Accessibility test, localization unit test
+- Pass criteria: Icon-only controls expose localized semantic labels with fallback.
+- Evidence: Test result
+
+**SWE4-UV-015**: Verify keyboard focus traversal.
+
+- Source SDD: SDD-025
+- Verification method: Widget test
+- Pass criteria: Primary interactive controls can be traversed in a logical order.
+- Evidence: Test result
+
+**SWE4-UV-016**: Verify text-scale resilience of critical controls.
+
+- Source SDD: SDD-026
+- Verification method: Accessibility widget test
+- Pass criteria: Critical controls remain reachable under increased text scale.
+- Evidence: Test result
+
+**SWE4-UV-017**: Verify platform inset service unit behavior.
+
+- Source SDD: SDD-027, SDD-030
+- Verification method: Unit test with platform test doubles
+- Pass criteria: Insets are normalized and exposed to the shell.
+- Evidence: Test result
+
+**SWE4-UV-018**: Verify back intent service behavior.
+
+- Source SDD: SDD-028
+- Verification method: Unit test with platform test doubles
+- Pass criteria: Platform back events map to expected route-level intents.
+- Evidence: Test result
+
+**SWE4-UV-019**: Verify localization fallback.
+
+- Source SDD: SDD-031, SDD-032, SDD-033
+- Verification method: Unit test
+- Pass criteria: Missing localized strings fall back deterministically.
+- Evidence: Test result
+
+**SWE4-UV-020**: Verify server-content pass-through.
+
+- Source SDD: SDD-034
+- Verification method: Unit test
+- Pass criteria: Server-provided content is not translated by product localization.
+- Evidence: Test result
+
+**SWE4-UV-021**: Verify Unicode text boundary behavior.
+
+- Source SDD: SDD-035, SDD-036, SDD-037
+- Verification method: Unit test
+- Pass criteria: Valid multilingual Unicode content is preserved; invalid external encodings are handled at boundaries.
+- Evidence: Test result
+
+**SWE4-UV-022**: Verify diagnostic Unicode preservation and redaction behavior.
+
+- Source SDD: SDD-038, SDD-041, SDD-050, SDD-054
+- Verification method: Unit test, security review
+- Pass criteria: Secrets are redacted while multilingual content is preserved.
+- Evidence: Test result, review record
+
+**SWE4-UV-023**: Verify locale-aware formatting.
+
+- Source SDD: SDD-040
+- Verification method: Unit test
+- Pass criteria: Dates, times, numbers, and timestamps format through localization utilities.
+- Evidence: Test result
+
+**SWE4-UV-024**: Verify traceability checker behavior.
+
+- Source SDD: SDD-043, SDD-044, SDD-055, SDD-056, SDD-066, SDD-067
+- Verification method: Unit test / script test
+- Pass criteria: Invalid direct-layer references are detected.
+- Evidence: Test result
+
+**SWE4-UV-025**: Verify bridge DTO safety.
+
+- Source SDD: SDD-046
+- Verification method: Unit test, static inspection
+- Pass criteria: Bridge DTOs do not expose internal Rust implementation types.
+- Evidence: Test result, review record
+
+**SWE4-UV-026**: Verify Rust core event mapping.
+
+- Source SDD: SDD-047
+- Verification method: Rust unit test
+- Pass criteria: Core events map deterministically to view model deltas.
+- Evidence: Test result
+
+**SWE4-UV-027**: Verify voice view model separation from DSP.
+
+- Source SDD: SDD-048
+- Verification method: Code review, unit test
+- Pass criteria: Voice UI receives status values and does not perform audio DSP.
+- Evidence: Review record, test result
+
+**SWE4-UV-028**: Verify storage facade isolation.
+
+- Source SDD: SDD-049
+- Verification method: Static inspection, unit test
+- Pass criteria: Feature widgets do not directly call database APIs.
+- Evidence: Review record, test result
+
+**SWE4-UV-029**: Verify interface detail catalog completeness.
+
+- Source SDD: SDD-059, SDD-060
+- Verification method: Review
+- Pass criteria: Unit-level interface entries include required details where applicable.
+- Evidence: Review record
+
+**SWE4-UV-030**: Verify unit construction and review records.
+
+- Source SDD: SDD-064, SDD-065, SDD-068, SDD-069, SDD-070
+- Verification method: Review
+- Pass criteria: Unit construction, review, verification handoff, and registry records exist for release scope units.
+- Evidence: Review record
+
+## 7. Traceability Matrix
+
+| SDD Range | SWE.4 Coverage |
+|---|---|
+| SDD-001 through SDD-010 | SWE4-UV-001 through SWE4-UV-005 |
+| SDD-011 through SDD-018 | SWE4-UV-006 through SWE4-UV-011 |
+| SDD-019 through SDD-026 | SWE4-UV-012 through SWE4-UV-016 |
+| SDD-027 through SDD-037 | SWE4-UV-017 through SWE4-UV-021 |
+| SDD-038 through SDD-050 | SWE4-UV-022 through SWE4-UV-028 |
+| SDD-051 through SDD-070 | SWE4-UV-029 through SWE4-UV-030 |
+
+## 8. Result Reporting
+
+Unit verification results shall be summarized in a unit verification summary report including:
+
+- verification scope
+- selected verification measures
+- skipped measures and rationale
+- pass/fail result
+- nonconformances
+- regression scope
+- residual risks
+- release recommendation
+
+## 9. Change History
+
+| Version | Date | Description |
+|---|---|---|
+| 0.1.0 | 2026-05-14 | Initial SWE.4 unit verification plan derived from SDD v0.3. |
+
+---
+
+## 10. Platform Decision Unit Verification Addendum
+
+**SWE4-UV-031**: Verify iOS and Android build configuration units.
+
+- Source SDD: SDD-071, SDD-072, SDD-073
+- Verification method: Static inspection, platform test
+- Pass criteria: iOS minimum runtime, Apple SDK gate, Android minimum runtime, and Android target SDK configuration are inspectable and match release policy.
+- Evidence: Test result, release inspection
+
+**SWE4-UV-032**: Verify single active connection enforcement.
+
+- Source SDD: SDD-074
+- Verification method: Unit test
+- Pass criteria: Attempting to create a second active MVP connection is rejected or routed through a controlled disconnect/switch policy.
+- Evidence: Test result
+
+**SWE4-UV-033**: Verify audio processing defaults and backend selection.
+
+- Source SDD: SDD-075, SDD-076
+- Verification method: Unit test, audio test
+- Pass criteria: AEC, AGC, Noise Suppression, and High-Pass Filter default to enabled where supported and stable; backend selector prefers platform-native processing.
+- Evidence: Test result
+
+**SWE4-UV-034**: Verify local database, secret storage, bridge, and diagnostics privacy gate units.
+
+- Source SDD: SDD-077, SDD-078, SDD-079, SDD-080
+- Verification method: Unit test, security inspection
+- Pass criteria: Non-secret storage, secret storage, typed bridge DTOs, and disabled automatic upload/crash behavior match detailed design.
+- Evidence: Test result, security review
+
+| SDD Range | SWE.4 Coverage |
+|---|---|
+| SDD-071 through SDD-080 | SWE4-UV-031 through SWE4-UV-034 |
+
+
+## Baseline Candidate 0.9.1 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. |
+
+
+## Baseline Candidate 0.9.2 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. |
@@ -0,0 +1,225 @@
+
+# Chanora SWE.5 Software Integration and Integration Verification Plan
+
+**Document type:** Software Integration Verification Plan  
+**Process alignment:** ASPICE SWE.5 Software Component Verification and Integration Verification  
+**Version:** 0.9.2
+**Status:** Baseline Candidate  
+**Language:** English  
+**Product:** Chanora  
+**Verification object:** Integrated software elements  
+**Direct source layer:** SAD and SDD verification objects  
+
+**Repo path:** `docs/verification/swe5-software-integration-verification-plan.md`  ---
+
+## 1. Purpose
+
+This document defines the software integration and integration verification strategy for Chanora. It verifies that software elements integrate correctly and interact according to the software architecture and detailed design.
+
+```text
+SysRS -> SysDes -> SRS -> SAD -> SDD
+                         -> SWE.5 Software Integration Verification
+```
+
+SWE.5 verifies architecture interfaces, dynamic behavior, component behavior, and selected detailed-design interactions.
+
+## 2. Integration Strategy
+
+| Integration step | Integrated elements | Purpose |
+|---|---|---|
+| SWE5-INT-001 | Flutter App Shell + Design System | Confirm theme initialization and token availability |
+| SWE5-INT-002 | Design System + UI Components | Confirm components consume tokens and expose semantics |
+| SWE5-INT-003 | Adaptive Shell + Feature Modules | Confirm compact/medium/expanded layouts integrate with features |
+| SWE5-INT-004 | Localization Service + UI Components | Confirm product strings and accessibility labels integrate |
+| SWE5-INT-005 | Protocol Adapter + Rust Core | Confirm protocol events and errors integrate with core state |
+| SWE5-INT-006 | Rust Core + Bridge Facade | Confirm commands, results, and event streams integrate |
+| SWE5-INT-007 | Bridge Facade + Flutter State | Confirm event mapping and view model updates |
+| SWE5-INT-008 | Audio Subsystem + Platform Audio | Confirm capture, processing, encode/decode, and playback interface behavior |
+| SWE5-INT-009 | Diagnostics + Storage + Localization | Confirm diagnostics event keys, localized descriptions, redaction, and export integration |
+| SWE5-INT-010 | Full Flutter UI + Rust Core | Confirm end-to-end software behavior before software qualification testing |
+
+## 3. Integration Verification Measures
+
+**SWE5-IV-001**: Verify Flutter App Shell and Design System integration.
+
+- Source SAD: SAD-001, SAD-002, SAD-007
+- Source SDD: SDD-001, SDD-002, SDD-003
+- Verification method: Flutter integration test
+- Pass criteria: App initializes Material 3 theme and Chanora semantic tokens before rendering feature screens.
+- Evidence: Integration test result
+
+**SWE5-IV-002**: Verify Design System and UI Component integration.
+
+- Source SAD: SAD-002, SAD-003, SAD-014
+- Source SDD: SDD-004 through SDD-010, SDD-021 through SDD-024
+- Verification method: Widget integration test
+- Pass criteria: Components consume design tokens and expose required accessibility semantics.
+- Evidence: Integration test result
+
+**SWE5-IV-003**: Verify adaptive shell and feature module integration.
+
+- Source SAD: SAD-008 through SAD-011
+- Source SDD: SDD-011 through SDD-015
+- Verification method: Integration test
+- Pass criteria: Compact, medium, and expanded layouts render correct feature regions and preserve critical voice/connection access.
+- Evidence: Integration test result
+
+**SWE5-IV-004**: Verify connection status and VoiceBar integration.
+
+- Source SAD: SAD-012, SAD-013, SAD-016
+- Source SDD: SDD-016, SDD-017, SDD-018, SDD-026
+- Verification method: Integration test
+- Pass criteria: Connection status and primary voice controls are visible or directly reachable across layout classes.
+- Evidence: Integration test result
+
+**SWE5-IV-005**: Verify localization and accessibility integration.
+
+- Source SAD: SAD-014, SAD-020, SAD-026
+- Source SDD: SDD-024, SDD-031, SDD-032, SDD-040
+- Verification method: Integration test, accessibility test
+- Pass criteria: Localized strings, semantic labels, fallback behavior, and locale-aware formatting work together.
+- Evidence: Integration test result
+
+**SWE5-IV-006**: Verify server-content text path integration.
+
+- Source SAD: SAD-021, SAD-022, SAD-023
+- Source SDD: SDD-034, SDD-035, SDD-036, SDD-037
+- Verification method: Integration test
+- Pass criteria: Server names, channel names, nicknames, and messages preserve Unicode and are not translated.
+- Evidence: Integration test result
+
+**SWE5-IV-007**: Verify Platform Services and App Shell integration.
+
+- Source SAD: SAD-017, SAD-018, SAD-019
+- Source SDD: SDD-027, SDD-028, SDD-029, SDD-030
+- Verification method: Platform integration test
+- Pass criteria: Insets, back intent, haptics, and keyboard avoidance integrate with shell behavior.
+- Evidence: Platform test result
+
+**SWE5-IV-008**: Verify Bridge Facade and Rust Core integration.
+
+- Source SAD: SAD-040, SAD-041
+- Source SDD: SDD-046, SDD-047
+- Verification method: Integration test
+- Pass criteria: Flutter commands and Rust events flow through stable DTOs and deterministic event mapping.
+- Evidence: Integration test result
+
+**SWE5-IV-009**: Verify Rust Core and Protocol Adapter integration.
+
+- Source SAD: SAD-032, SAD-033, SAD-041
+- Source SDD: SDD-046, SDD-047
+- Verification method: Integration test with protocol test server or protocol test double
+- Pass criteria: Connection, snapshot, delta events, and protocol errors integrate with core state.
+- Evidence: Integration test result
+
+**SWE5-IV-010**: Verify Audio Subsystem and Platform Audio integration.
+
+- Source SAD: SAD-034
+- Source SDD: SDD-048
+- Verification method: Audio integration test
+- Pass criteria: Audio status reaches UI while DSP remains isolated from UI units.
+- Evidence: Audio integration test result
+
+**SWE5-IV-011**: Verify Diagnostics integration.
+
+- Source SAD: SAD-036, SAD-050
+- Source SDD: SDD-038, SDD-041, SDD-050, SDD-054
+- Verification method: Integration test, audit
+- Pass criteria: Diagnostic keys, localized descriptions, redaction, Unicode preservation, and export flow operate together.
+- Evidence: Integration test result, audit record
+
+**SWE5-IV-012**: Verify storage and secure-storage integration boundaries.
+
+- Source SAD: SAD-035
+- Source SDD: SDD-049
+- Verification method: Integration test, security review
+- Pass criteria: Non-secret data uses storage facade and secrets use secure storage boundaries.
+- Evidence: Integration test result, review record
+
+**SWE5-IV-013**: Verify architecture-view and traceability-tooling integration.
+
+- Source SAD: SAD-046 through SAD-060
+- Source SDD: SDD-051 through SDD-070
+- Verification method: Documentation/tooling integration check
+- Pass criteria: Architecture views, ADRs, interface detail catalog, and traceability checker are mutually consistent.
+- Evidence: Review record
+
+## 4. Regression Strategy
+
+Regression selection shall consider:
+
+- changed software unit
+- changed interface
+- changed architecture item
+- changed DTO
+- changed localization resource
+- changed audio pipeline behavior
+- changed protocol adapter behavior
+- changed diagnostics redaction behavior
+- changed platform behavior
+
+## 5. Traceability Matrix
+
+| Architecture / Design Area | SWE.5 Coverage |
+|---|---|
+| SAD-001 through SAD-016 | SWE5-IV-001 through SWE5-IV-005 |
+| SAD-017 through SAD-027 | SWE5-IV-005 through SWE5-IV-007, SWE5-IV-011 |
+| SAD-028 through SAD-031 | SWE5-IV-013 |
+| SAD-032 through SAD-041 | SWE5-IV-008 through SWE5-IV-012 |
+| SAD-042 through SAD-050 | SWE5-IV-001, SWE5-IV-011, SWE5-IV-013 |
+| SAD-051 through SAD-060 | SWE5-IV-013 |
+| SDD-001 through SDD-030 | SWE5-IV-001 through SWE5-IV-007 |
+| SDD-031 through SDD-050 | SWE5-IV-005 through SWE5-IV-012 |
+| SDD-051 through SDD-070 | SWE5-IV-013 |
+
+## 6. Result Reporting
+
+Software integration verification results shall be summarized in an integration verification summary report including:
+
+- integrated elements
+- selected integration sequence
+- selected verification measures
+- regression scope
+- test environment
+- pass/fail result
+- nonconformances
+- interface issues
+- residual risks
+- release recommendation
+
+## 7. Change History
+
+| Version | Date | Description |
+|---|---|---|
+| 0.1.0 | 2026-05-14 | Initial SWE.5 software integration and integration verification plan. |
+
+---
+
+## 8. Platform Decision Integration Verification Addendum
+
+**SWE5-IV-014**: Verify platform baseline, build configuration, single connection, audio defaults, storage, bridge, and diagnostics privacy integration.
+
+- Source SAD: SAD-061 through SAD-070
+- Source SDD: SDD-071 through SDD-080
+- Verification method: Integration test, release inspection, security review
+- Pass criteria: New product decisions integrate across build configuration, runtime behavior, audio, storage, bridge, diagnostics, and release readiness.
+- Evidence: Integration verification result
+
+| Architecture / Design Area | SWE.5 Coverage |
+|---|---|
+| SAD-061 through SAD-070 | SWE5-IV-014 |
+| SDD-071 through SDD-080 | SWE5-IV-014 |
+
+
+## Baseline Candidate 0.9.1 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. |
+
+
+## Baseline Candidate 0.9.2 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. |
@@ -0,0 +1,224 @@
+
+# Chanora SWE.6 Software Verification Plan
+
+**Document type:** Software Verification / Software Qualification Test Plan  
+**Process alignment:** ASPICE SWE.6 Software Verification  
+**Version:** 0.9.2
+**Status:** Baseline Candidate  
+**Language:** English  
+**Product:** Chanora  
+**Verification object:** Fully integrated Chanora software  
+**Direct source layer:** SRS  
+
+**Repo path:** `docs/verification/swe6-software-verification-plan.md`  ---
+
+## 1. Purpose
+
+This document defines the software verification strategy for Chanora. It verifies that the fully integrated software satisfies the Software Requirements Specification.
+
+```text
+SysRS -> SysDes -> SRS -> SAD -> SDD
+                 -> SWE.6 Software Verification
+```
+
+SWE.6 verifies against SRS. It does not replace SWE.4 unit verification or SWE.5 software integration verification.
+
+## 2. Software Verification Strategy
+
+| Verification type | Purpose |
+|---|---|
+| Functional software tests | Verify integrated software behavior against SRS |
+| Non-functional software tests | Verify performance, accessibility, security, diagnostics, localization, and reliability requirements |
+| Platform software tests | Verify integrated software behavior on target platforms |
+| Regression tests | Confirm changes did not break previously verified software requirements |
+| Release-scope test selection | Select tests according to target release content |
+| Summary reporting | Communicate software verification status |
+
+## 3. Software Verification Measures
+
+**SWE6-SV-001**: Verify server connection flow.
+
+- Source SRS: SRS-001 through SRS-030
+- Verification method: End-to-end software test
+- Pass criteria: User can connect to a compatible server with configured connection data.
+- Evidence: Software verification result
+
+**SWE6-SV-002**: Verify channel tree, client list, and server state display.
+
+- Source SRS: SRS-031 through SRS-060
+- Verification method: End-to-end software test
+- Pass criteria: Channel and client state is displayed and updates after server events.
+- Evidence: Software verification result
+
+**SWE6-SV-003**: Verify voice send and receive.
+
+- Source SRS: SRS-061 through SRS-090
+- Verification method: Audio software verification test
+- Pass criteria: User can transmit and receive voice under supported conditions.
+- Evidence: Software verification result
+
+**SWE6-SV-004**: Verify push-to-talk, mute, deaf, and voice status.
+
+- Source SRS: SRS-061 through SRS-090, SRS-156
+- Verification method: End-to-end software test
+- Pass criteria: Voice controls perform expected software behavior and display correct state.
+- Evidence: Software verification result
+
+**SWE6-SV-005**: Verify local storage and secure storage behavior.
+
+- Source SRS: SRS-091 through SRS-110
+- Verification method: Software security and persistence test
+- Pass criteria: Non-secret data persists through approved storage and secrets use secure storage boundaries.
+- Evidence: Software verification result
+
+**SWE6-SV-006**: Verify diagnostics and redacted export behavior.
+
+- Source SRS: SRS-111 through SRS-124, SRS-177, SRS-178
+- Verification method: Software verification test, audit
+- Pass criteria: Diagnostic export requires user action and redacts sensitive data while preserving safe Unicode content.
+- Evidence: Software verification result, audit record
+
+**SWE6-SV-007**: Verify deployment-sensitive software behavior.
+
+- Source SRS: SRS-125 through SRS-134
+- Verification method: Release build verification
+- Pass criteria: Release build metadata, packaging behavior, and platform declarations are consistent with software requirements.
+- Evidence: Release verification result
+
+**SWE6-SV-008**: Verify traceability and documentation controls.
+
+- Source SRS: SRS-135 through SRS-143, SRS-180 through SRS-183
+- Verification method: Documentation verification
+- Pass criteria: SRS, SAD, and SDD direct-source rules pass validation.
+- Evidence: Traceability report
+
+**SWE6-SV-009**: Verify Material 3 and Chanora Design System behavior.
+
+- Source SRS: SRS-144 through SRS-150
+- Verification method: UI software verification, review
+- Pass criteria: Integrated app uses Material 3 baseline and Chanora semantic tokens without feature-screen hardcoding.
+- Evidence: Software verification result
+
+**SWE6-SV-010**: Verify adaptive layouts.
+
+- Source SRS: SRS-151 through SRS-156
+- Verification method: UI software verification
+- Pass criteria: Compact, medium, and expanded layouts preserve connection status and primary voice controls.
+- Evidence: Software verification result
+
+**SWE6-SV-011**: Verify accessibility behavior.
+
+- Source SRS: SRS-157 through SRS-161
+- Verification method: Accessibility verification
+- Pass criteria: Critical controls expose semantics, non-color-only state cues, focus behavior, and text-scale resilience.
+- Evidence: Accessibility verification result
+
+**SWE6-SV-012**: Verify platform behavior.
+
+- Source SRS: SRS-162 through SRS-164
+- Verification method: Platform software verification
+- Pass criteria: Insets, safe areas, keyboard, Android back behavior, and iOS platform behavior operate as specified.
+- Evidence: Platform verification result
+
+**SWE6-SV-013**: Verify localization and fallback behavior.
+
+- Source SRS: SRS-165 through SRS-169
+- Verification method: Localization software verification
+- Pass criteria: Product strings are externalized, English baseline exists, additional locales can be added, and fallback is deterministic.
+- Evidence: Localization verification result
+
+**SWE6-SV-014**: Verify Unicode and server-content behavior.
+
+- Source SRS: SRS-170 through SRS-176
+- Verification method: Internationalization software verification
+- Pass criteria: Server content is preserved, displayed without translation, UTF-8 is used internally, and locale-aware formatting works.
+- Evidence: Internationalization verification result
+
+**SWE6-SV-015**: Verify software architecture and detailed design traceability controls.
+
+- Source SRS: SRS-180 through SRS-184
+- Verification method: Documentation/tooling verification
+- Pass criteria: SAD derives from SRS and SDD derives from SAD; initialization sequence is verified.
+- Evidence: Traceability validation result
+
+## 4. Regression Strategy
+
+Regression test selection shall consider:
+
+- changed SRS item
+- changed feature
+- changed architecture component
+- changed detailed design unit
+- changed platform behavior
+- changed localization or Unicode handling
+- changed diagnostics or redaction
+- changed audio behavior
+- changed protocol adapter behavior
+
+## 5. Traceability Matrix
+
+| SRS Range | SWE.6 Coverage |
+|---|---|
+| SRS-001 through SRS-030 | SWE6-SV-001 |
+| SRS-031 through SRS-060 | SWE6-SV-002 |
+| SRS-061 through SRS-090 | SWE6-SV-003, SWE6-SV-004 |
+| SRS-091 through SRS-110 | SWE6-SV-005 |
+| SRS-111 through SRS-124 | SWE6-SV-006 |
+| SRS-125 through SRS-134 | SWE6-SV-007 |
+| SRS-135 through SRS-143 | SWE6-SV-008 |
+| SRS-144 through SRS-150 | SWE6-SV-009 |
+| SRS-151 through SRS-156 | SWE6-SV-010 |
+| SRS-157 through SRS-161 | SWE6-SV-011 |
+| SRS-162 through SRS-164 | SWE6-SV-012 |
+| SRS-165 through SRS-169 | SWE6-SV-013 |
+| SRS-170 through SRS-176 | SWE6-SV-014 |
+| SRS-177 through SRS-184 | SWE6-SV-006, SWE6-SV-015 |
+
+## 6. Result Reporting
+
+Software verification results shall be summarized in a software verification summary report including:
+
+- release scope
+- selected software verification measures
+- skipped measures and rationale
+- platform/environment used
+- pass/fail status
+- nonconformances
+- regression scope
+- residual risks
+- release recommendation
+
+## 7. Change History
+
+| Version | Date | Description |
+|---|---|---|
+| 0.1.0 | 2026-05-14 | Initial SWE.6 software verification plan derived from SRS v0.5. |
+
+---
+
+## 8. Platform Decision Software Verification Addendum
+
+**SWE6-SV-016**: Verify platform baseline, release SDK gates, single connection MVP scope, audio defaults, storage/bridge policy, and diagnostics/crash reporting policy.
+
+- Source SRS: SRS-185 through SRS-194
+- Verification method: Software verification, release inspection, security/privacy review
+- Pass criteria: Integrated software and release configuration satisfy the accepted product decisions.
+- Evidence: Software verification result, release inspection record
+
+| SRS Range | SWE.6 Coverage |
+|---|---|
+| SRS-185 through SRS-194 | SWE6-SV-016 |
+
+
+## Baseline Candidate 0.9.1 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. |
+
+
+## Baseline Candidate 0.9.2 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. |
@@ -0,0 +1,241 @@
+
+# Chanora SYS.4 System Integration and Integration Verification Plan
+
+**Document type:** System Integration and Integration Verification Plan  
+**Process alignment:** ASPICE SYS.4 System Integration and Integration Verification  
+**Version:** 0.9.2
+**Status:** Baseline Candidate  
+**Language:** English  
+**Product:** Chanora  
+**Verification object:** Integrated application system elements  
+**Direct source layer:** SysDes  
+
+**Repo path:** `docs/verification/sys4-system-integration-verification-plan.md`  ---
+
+## 1. Purpose
+
+This document defines the system integration and integration verification strategy for the Chanora application system. It verifies that the system elements defined by SysDes are integrated and interact according to the system architecture.
+
+```text
+SysRS -> SysDes -> SYS.4 System Integration Verification
+```
+
+SYS.4 verifies system architecture integration. It does not replace SWE.4, SWE.5, or SWE.6.
+
+## 2. System Integration Scope
+
+System elements include:
+
+- User/operator interaction
+- Client device hardware
+- Operating system services
+- Network environment
+- External compatible voice server
+- Chanora application container
+- Flutter UI
+- Rust Core
+- Protocol adapter
+- Audio subsystem
+- Platform adapters
+- Storage
+- Secure storage
+- Diagnostics
+- Deployment environment
+- Localization and UI/UX architecture elements
+
+## 3. System Integration Strategy
+
+| Integration step | System elements | Purpose |
+|---|---|---|
+| SYS4-INT-001 | Chanora app + OS permissions | Verify microphone, notification, secure storage, lifecycle, and permission integration |
+| SYS4-INT-002 | Chanora app + audio hardware | Verify input/output device integration and route changes |
+| SYS4-INT-003 | Chanora app + network environment | Verify connection behavior, reconnect, and failure presentation |
+| SYS4-INT-004 | Chanora app + external compatible server | Verify channels, clients, voice, and text behavior with real or representative server |
+| SYS4-INT-005 | Flutter UI + platform services | Verify safe areas, system bars, keyboard, and platform navigation behavior |
+| SYS4-INT-006 | Rust Core + external protocol server | Verify protocol integration at system level |
+| SYS4-INT-007 | Diagnostics + user export target | Verify diagnostic export workflow at system level |
+| SYS4-INT-008 | Deployment artifact + target OS | Verify packaged application launches and uses required services |
+| SYS4-INT-009 | Localization + server multilingual content | Verify multilingual product UI and server-provided content handling |
+| SYS4-INT-010 | Full application system | Verify integrated behavior across supported platform classes |
+
+## 4. System Integration Verification Measures
+
+**SYS4-SIV-001**: Verify OS permission integration.
+
+- Source SysDes: SysDes-048 through SysDes-058, SysDes-118
+- Verification method: Platform system integration test
+- Pass criteria: Required permissions, lifecycle behavior, safe areas, keyboard behavior, and platform navigation behavior integrate with the application.
+- Evidence: System integration test result
+
+**SYS4-SIV-002**: Verify audio hardware integration.
+
+- Source SysDes: SysDes-059 through SysDes-074
+- Verification method: Audio system integration test
+- Pass criteria: Audio capture, playback, route change handling, and processing feature availability work with supported devices.
+- Evidence: System integration test result
+
+**SYS4-SIV-003**: Verify network environment integration.
+
+- Source SysDes: SysDes-075 through SysDes-087
+- Verification method: Network system integration test
+- Pass criteria: Connection, recoverable network loss, reconnect, and user-safe errors work under defined network conditions.
+- Evidence: System integration test result
+
+**SYS4-SIV-004**: Verify external compatible server integration.
+
+- Source SysDes: SysDes-088 through SysDes-101
+- Verification method: Server system integration test
+- Pass criteria: Server connection, channel list, client list, voice, text, and disconnect behavior integrate correctly.
+- Evidence: System integration test result
+
+**SYS4-SIV-005**: Verify application functional system integration.
+
+- Source SysDes: SysDes-102 through SysDes-120
+- Verification method: System integration test
+- Pass criteria: User-visible workflows operate across UI, Rust Core, protocol, state, audio, storage, and diagnostics elements.
+- Evidence: System integration test result
+
+**SYS4-SIV-006**: Verify protocol system integration.
+
+- Source SysDes: SysDes-121 through SysDes-128
+- Verification method: System integration test with compatible server
+- Pass criteria: Protocol adapter integrates with Rust Core and external compatible server without exposing protocol internals to UI.
+- Evidence: System integration test result
+
+**SYS4-SIV-007**: Verify state synchronization system integration.
+
+- Source SysDes: SysDes-129 through SysDes-132
+- Verification method: System integration test
+- Pass criteria: Snapshot, delta, reconnect, event ordering, and UI update behavior operate together.
+- Evidence: System integration test result
+
+**SYS4-SIV-008**: Verify storage and security system integration.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: Security and system integration test
+- Pass criteria: Bookmarks, settings, secure storage, redaction, and privacy constraints integrate correctly.
+- Evidence: System integration test result, audit record
+
+**SYS4-SIV-009**: Verify diagnostics and operations system integration.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: System integration test
+- Pass criteria: Logs, redaction, diagnostics, export, and support workflow operate as an integrated capability.
+- Evidence: System integration test result
+
+**SYS4-SIV-010**: Verify non-functional system behavior.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: Performance and reliability system integration test
+- Pass criteria: Responsiveness, audio latency, memory growth controls, reconnect, and malformed-event behavior meet defined expectations.
+- Evidence: System integration test result
+
+**SYS4-SIV-011**: Verify deployment and release environment integration.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: Deployment system integration test
+- Pass criteria: Target platform packages install, launch, and access required OS services as expected.
+- Evidence: Deployment integration result
+
+**SYS4-SIV-012**: Verify interface integration.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: Interface system integration test
+- Pass criteria: User, bridge, protocol, audio, storage, secure storage, network, and diagnostic interfaces integrate correctly.
+- Evidence: Interface integration result
+
+**SYS4-SIV-013**: Verify constraints and assumptions integration impact.
+
+- Source SysDes: SysDes-001 through SysDes-132
+- Verification method: Review, inspection, system integration test
+- Pass criteria: Constraints and assumptions are respected or deviations are documented.
+- Evidence: Review record, system integration test result
+
+**SYS4-SIV-014**: Verify UI/UX, Material 3, platform, and i18n system integration.
+
+- Source SysDes: SysDes-111 through SysDes-132
+- Verification method: System integration test
+- Pass criteria: Material 3 design system, adaptive shell, accessibility, platform behavior, localization, Unicode, diagnostics localization, and traceability controls integrate correctly.
+- Evidence: System integration test result
+
+## 5. Regression Strategy
+
+Regression selection shall consider:
+
+- changed system element
+- changed software release
+- changed platform adapter
+- changed audio hardware support
+- changed compatible server behavior
+- changed network behavior
+- changed deployment package
+- changed localization or Unicode handling
+- changed diagnostics export behavior
+- changed system architecture item
+
+## 6. Traceability Matrix
+
+| SysDes Range | SYS.4 Coverage |
+|---|---|
+| SysDes-001 through SysDes-034 | SYS4-SIV-005, SYS4-SIV-006, SYS4-SIV-007 |
+| SysDes-035 through SysDes-058 | SYS4-SIV-001 |
+| SysDes-059 through SysDes-074 | SYS4-SIV-002 |
+| SysDes-075 through SysDes-087 | SYS4-SIV-003 |
+| SysDes-088 through SysDes-101 | SYS4-SIV-004 |
+| SysDes-102 through SysDes-110 | SYS4-SIV-005 |
+| SysDes-111 through SysDes-132 | SYS4-SIV-014 |
+| SysDes-121 through SysDes-128 | SYS4-SIV-006 |
+| SysDes-129 through SysDes-132 | SYS4-SIV-007 |
+| SysDes-above-current-baseline and above | Not applicable; no such IDs exist in current SysDes baseline. |
+
+## 7. Result Reporting
+
+System integration verification results shall be summarized in a system integration verification summary report including:
+
+- release scope
+- integrated system elements
+- integration sequence
+- selected verification measures
+- regression scope
+- platform/environment used
+- pass/fail status
+- nonconformances
+- interface issues
+- dynamic behavior issues
+- residual risks
+- release recommendation
+
+## 8. Change History
+
+| Version | Date | Description |
+|---|---|---|
+| 0.1.0 | 2026-05-14 | Initial SYS.4 system integration and integration verification plan derived from SysDes v0.6. |
+
+---
+
+## 9. Platform Decision System Integration Verification Addendum
+
+**SYS4-SIV-015**: Verify platform baseline, Apple SDK gate, Android target gate, MVP single connection, audio defaults, storage, bridge, and diagnostics privacy system integration.
+
+- Source SysDes: SysDes-133 through SysDes-141
+- Verification method: System integration test, release inspection, security/privacy review
+- Pass criteria: System-level integration reflects accepted product decisions and release gates.
+- Evidence: System integration result, release readiness evidence
+
+| SysDes Range | SYS.4 Coverage |
+|---|---|
+| SysDes-133 through SysDes-141 | SYS4-SIV-015 |
+
+
+## Baseline Candidate 0.9.1 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. |
+
+
+## Baseline Candidate 0.9.2 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. |
@@ -0,0 +1,83 @@
+
+# Chanora Verification Master Plan
+
+**Document type:** Verification Master Plan  
+**Version:** 0.9.2
+**Status:** Baseline Candidate  
+**Language:** English  
+**Product:** Chanora  
+
+**Repo path:** `docs/verification/verification-master-plan.md`  ---
+
+## 1. Purpose
+
+This document defines how Chanora verification documents relate to the engineering hierarchy.
+
+Core engineering hierarchy:
+
+```text
+SysRS -> SysDes -> SRS -> SAD -> SDD
+```
+
+Verification work products are downstream evidence-producing artifacts and do not replace the hierarchy.
+
+## 2. Verification Layers
+
+| Process | Verification target | Direct verification source | Purpose |
+|---|---|---|---|
+| SWE.4 | Software units | SDD | Verify software units against detailed design |
+| SWE.5 | Integrated software elements | SAD and SDD | Verify software architecture integration, interfaces, dynamic behavior, and component interaction |
+| SWE.6 | Fully integrated software | SRS | Verify integrated software satisfies software requirements |
+| SYS.4 | Integrated application system elements | SysDes | Verify system elements integrate according to system architecture |
+
+## 3. Verification Flow
+
+```text
+SDD -> SWE.4 Unit Verification
+SAD + SDD -> SWE.5 Software Integration Verification
+SRS -> SWE.6 Software Verification
+SysDes -> SYS.4 System Integration Verification
+```
+
+## 4. Regression Rule
+
+A change in any design or requirement artifact shall trigger impact analysis for the corresponding verification layer:
+
+| Changed artifact | Verification impact |
+|---|---|
+| SDD | SWE.4 and SWE.5 impact analysis |
+| SAD | SDD, SWE.5, and possibly SWE.4 impact analysis |
+| SRS | SAD, SDD, SWE.6, and related lower-level verification impact analysis |
+| SysDes | SRS/SAD/SDD impact analysis and SYS.4 impact analysis |
+| SysRS | SysDes/SRS/SAD/SDD impact analysis and system/software verification impact analysis |
+
+## 5. Required Verification Reports
+
+| Report | Source |
+|---|---|
+| Unit Verification Summary Report | SWE.4 |
+| Software Integration Verification Summary Report | SWE.5 |
+| Software Verification Summary Report | SWE.6 |
+| System Integration Verification Summary Report | SYS.4 |
+| Regression Verification Report | Any affected verification layer |
+| Problem Resolution Report | Failed verification requiring defect handling |
+
+## 6. Change History
+
+| Version | Date | Description |
+|---|---|---|
+| 0.1.0 | 2026-05-14 | Initial verification master plan covering SWE.4, SWE.5, SWE.6, and SYS.4. |
+
+
+## Baseline Candidate 0.9.1 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.1 | 2026-05-14 | Updated baseline after product decision closure: Apple App Store SDK gate uses Xcode 26+ and iOS 26 / iPadOS 26 SDK+ since 2026-04-28, platform baselines and decision traceability propagated across the document set. |
+
+
+## Baseline Candidate 0.9.2 Update
+
+| Version | Date | Description |
+|---|---|---|
+| 0.9.2 | 2026-05-14 | Corrected Apple App Store Connect upload gate to 2026-04-28 and checked full-package naming, references, and coverage. |