@mmerterden/multi-agent-pipeline 12.2.0 → 12.3.0

package/pipeline/multi-agent-refs/analysis-template.md

@@ -10,7 +10,7 @@ description: "v3 canonical template for /multi-agent:analysis. 23 main sections
 
 > **Language**: This file is read as a system prompt. Prose stays English. Example tables and headings carry bilingual TR / EN scaffolds; the runtime renderer picks the right column per `outputLanguage`.
 
-> **Locked decisions that govern this template**: 1 (one feature per run), 2 (omission rule), 3 (citation discipline), 4 (forward-looking spec), 7 (humanizer punctuation policy), 8 (standards binding), 9 (per-platform output split), 11 (repo-evidence reuse-first), 12 (Gherkin), 13 (Goals + Non-Goals), 14 (SVG default), 15 (Files-to-Add tag), 16 (API response variants), 17 (screenshots embedded), 18 (all Figma variants), 19 (8-locale full coverage), 20 (References at bottom), 21 (platform-agnostic + Pass B), 22 (convention extraction), 23 (fallback risk), 24 (Pass B footnote mandatory), 28 (SwiftUI Preview block iOS), 29 (variant usage explicit), 30 (analysis self-contained pipeline-wide MCP forbidden outside analysis phase).
+> **Locked decisions that govern this template**: the canonical numbered list lives in `pipeline/commands/multi-agent/analysis/SKILL.md` (cite decisions by label, not by a number duplicated here, to avoid drift). The template's structure is shaped chiefly by: one-feature-per-run, section omission rule, citation discipline (incl. annotation-as-copy), forward-looking spec, humanizer punctuation policy, standards binding, per-platform output split, repo-evidence reuse-first, Figma 3-tier access, Gherkin user stories, Goals + Non-Goals paired, SVG default, Files-to-Add tag, API response variants exhaustive, screenshots embedded, all Figma variants drilled, localization mode (ownership-aware), References at bottom, platform-agnostic + Pass B render, convention extraction, Pass B footnote mandatory, Lite mode, SwiftUI Preview block (iOS), variant usage explicit, analysis self-contained (no MCP downstream), and business-rule to acceptance-criterion to test traceability.
 
 ## Mode selection - Full vs Lite
 
@@ -45,6 +45,8 @@ feature: <FeatureName>
 platform: ios | android | backend | frontend
 language: tr | en
 mode: full | lite
+ui_tests: true | false
+a11y_depth: basic | full
 generated: <ISO 8601 UTC timestamp>
 jira: <JIRA_KEY>-<id>
 branch: <branch-name>
@@ -58,6 +60,8 @@ template_version: v3
 ---
 ```
 
+`ui_tests` and `a11y_depth` record the Phase 0 Step 5a opt-ins (defaults `false` / `basic`) so the coverage choice is auditable and the pre-dispatch validator can enforce it: `ui_tests: true` requires Section 15.6, `a11y_depth: full` requires the Section 16.2 walkthrough.
+
 The dev pipeline (`/multi-agent:dev`) reads `platform` to verify file match, `evidence_digest` to detect stale specs, and `mode` to know which section set to expect.
 
 ## Omission rules
@@ -71,15 +75,15 @@ Locked 2 - no `TBD` / `Not applicable` placeholder. Sections with zero evidence
 | 6 Component Inventory | No Figma URL AND no UI primitive evidence in repo |
 | 7 Design Tokens | Sections 5 and 6 both omitted |
 | 8 Asset Inventory | No new visual asset planned AND no existing asset modified |
-| 10 Localization | No Figma text layer AND no localization key file in repo |
+| 10 Localization | No Figma annotation AND no Figma text layer AND no localization key file in repo |
 | 11 Analytics | No Firebase input AND no analytics call site in repo |
 | 12 Deeplink/Push | No deeplink handler in repo AND no push payload binding AND spec silent |
 | 15 Test Plan | Backend-only run with no contract testing planned (rare) |
 | 16 Accessibility | Backend-only (no UI surface) |
 | 17 Security | No PII / auth / health data touched (rare, document explicit decision) |
-| 18 Rollout | Lite mode |
-| 19 Alternatives | Lite mode AND zero significant architectural decision points |
-| 22 Glossary | Lite mode |
+| 18 Rollout | Lite mode. In Full mode render the compact checklist only (not prose); drop if the pipeline's own commit/PR/rollout phase already covers it and no staged rollout / feature flag applies |
+| 19 Alternatives | Default drop. Render ONLY when a real architectural decision with 2+ genuine options exists; a thin or invented alternatives list is worse than none (a real decision point already lives in Section 20) |
+| 22 Glossary | Default drop. Render ONLY on explicit request or when the doc uses more than 5 domain-specific terms a new reader would not know; otherwise define terms inline |
 | 23 Changelog | Lite mode (optional even in Full for small revisions) |
 
 Sections 1, 2, 4, 9, 13, 14, 20, 21 are never omitted.
@@ -95,10 +99,10 @@ Every Pass B-rendered cell carries a footnote pointing to its evidence source:
 Examples:
 
 ```
-| State holder | `PassengerFlightViewModel` ^[C2 high: 8 örnek; en yakın StandaloneLoginViewModel.swift] |
+| State holder | `UserProfileViewModel` ^[C2 high: 8 örnek; en yakın StandaloneLoginViewModel.swift] |
 | Test naming | `@Test func fetch_validInput_returnsIdle()` ^[C4 medium: 4 mevcut örnek, çoğunluk Swift Testing] |
-| Identifier | `passengerFlight.continueButton` ^[C5 high: ui-testing-identifiers.json dot notation] |
-| State model | sealed enum `PassengerFlightUIState` ^[C3 fallback: conventions-defaults.md:C3-iOS, repo evidence none] |
+| Identifier | `userProfile.continueButton` ^[C5 high: ui-testing-identifiers.json dot notation] |
+| State model | sealed enum `UserProfileUIState` ^[C3 fallback: conventions-defaults.md:C3-iOS, repo evidence none] |
 ```
 
 Footnote-less cells fail the dispatch gate.
@@ -132,13 +136,17 @@ Never omitted. Locked 13 - both columns mandatory. A row in only one column is n
 ## 2. Hedefler ve Karşı Hedefler   <!-- TR -->
 ## 2. Goals and Non-Goals          <!-- EN -->
 
+### İş kapsamı / Business scope
+
+<1-2 sentences: what this feature covers and its boundary, in domain language. Names the platforms in scope (from the provided repos) and what is explicitly out of scope.>
+
 | Hedef / Goal | Karşı Hedef / Non-Goal |
 |---|---|
 | <goal 1 citing source> | <non-goal 1 citing source> |
 | <goal 2> | <non-goal 2> |
 ```
 
-Each non-goal must say what it does NOT cover, not a vague "out of scope".
+Each non-goal must say what it does NOT cover, not a vague "out of scope" (AI cannot infer exclusion from omission - state it positively). The scope line frames the goals below; detailed rules live in Section 4.4.
 
 ## 3. Akış Diyagramı / Flow Chart
 
@@ -217,7 +225,7 @@ And <secondary outcome>
 Given <precondition>
 But <conflicting state>
 When <action>
-Then <prevention code shown, e.g. PP-211>
+Then <business-rule code shown, e.g. ERR-211>
 And <user guidance>
 \`\`\`
 
@@ -228,9 +236,18 @@ Given <precondition>
 When <action>
 Then <expected outcome>
 \`\`\`
+
+### 4.4 İş Kuralları / Business Rules
+
+Locked 31 - the traceability spine. Every business rule is deterministic and testable (same input always yields the same outcome) and carries a stable id `BR-<slug>-NN`. Each rule maps to at least one acceptance criterion written Given / When / Then. In Full mode each acceptance criterion is then realized as unit-test scenarios in Section 15.1; in Lite mode Section 15 is not rendered, so the acceptance criterion stands alone here (it is itself the testable statement) and the 15.1 mapping is deferred to a later Full analysis or to `/multi-agent:dev`. Rules come from the spec / Confluence / Jira / annotations, never invented; a rule with no source cites `[label TBD - see Open Questions]` and adds a Section 20 row.
+
+| BR ID | Kural / Rule (deterministic, testable) | Kaynak / Source | Kabul kriteri / Acceptance criterion (Given/When/Then) |
+|---|---|---|---|
+| BR-<slug>-01 | <rule statement> | [Confluence:<pageId>:<heading>] / [Figma annotation <nodeId>] / file:line | Given <state>, When <action>, Then <binary outcome> |
+| BR-<slug>-02 | <rule statement> | <source> | Given ..., When ..., Then ... (+ >=1 failure-mode criterion) |
 ```
 
-Each scenario cites the matching prevention code (Section 9) when applicable. Plain-prose user stories without Given/When/Then are rejected by the renderer.
+Each scenario in 4.1-4.3 cites the matching `BR-<slug>-NN` id (and, when a server code applies, the Section 9.4 code). Plain-prose user stories without Given/When/Then are rejected by the renderer.
 
 ## 5. Tasarım Referansı / Design Reference
 
@@ -266,6 +283,24 @@ Token references for each variant (no raw numbers).
 Tier in use: <1 (MCP) | 2 (REST) | 3 (user screenshot)>
 Screenshots attached: <count>
 Auth retries used: <count>
+
+### 5.4 Yerleşim ve Kaydırma / Layout and Scroll
+
+Precise-enough-to-reproduce layout. Spacing/padding are token names (no raw numbers, Locked bound to Section 7). One row per meaningful component or frame region.
+
+| Bileşen / Component | Node | Auto Layout (yön/wrap) | Padding (kenar/edge -> token) | Boşluk / Gap (token) | Hizalama / Alignment | Boyut / Sizing (fixed/hug/fill) | Konum / Position (constraint) |
+|---|---|---|---|---|---|---|---|
+| <name> | <nodeId> | vertical | top Spacing.spacing16 / others Spacing.spacing12 | Spacing.spacing8 | leading / center | width fill, height hug | pinned top |
+
+**Scroll and container behavior** (a static Figma frame cannot express this - state it explicitly for both the AI and the human):
+
+- Kaydırma kabı / Scroll container: <which region scrolls; single vertical scroll vs nested>
+- Sabit / Sticky: <header/footer/CTA pinned while content scrolls, or none>
+- İçerik kenar boşlukları / Content insets: <token or safe-area-relative>
+- Güvenli alan / Safe area: <edges respected: top notch / bottom home indicator / status bar>
+- Klavye / Keyboard avoidance: <inset-adjust vs scroll-into-view vs none>
+
+Capture order (tokens never hardcoded): `mcp__claude_ai_Figma__get_metadata` (tree) -> `mcp__claude_ai_Figma__get_variable_defs` (resolve spacing/color/type tokens) -> render -> `mcp__claude_ai_Figma__get_screenshot` (visual check). Run per section/frame for fidelity, not per whole page.
 ```
 
 Frame gallery images are uploaded to Confluence as multipart attachments and referenced via `<ac:image><ri:attachment ri:filename="..." /></ac:image>` (Locked 17). Section URL drilling enumerates all child frames automatically via `mcp__claude_ai_Figma__get_metadata` or `figma-screenshot.sh --section`.
@@ -287,6 +322,18 @@ Per-platform projection.
 
 Locked 11 - existence is resolved against `evidence.codeConnect[]` (the Code Connect index from Phase 1b.1) first: a design `nodeId` (or its `fileKey`) that matches an index entry emits a `reuse` row (`Mevcut/Existing = yes`, pointing at the bound component + path), because figma-to-swiftui already built and bound it. A `nodeId` with no Code Connect match falls back to the Phase 1b `uiComponents` heuristic; only when neither finds a candidate does the row become a new component (`Existing = no`, added to Section 14).
 
+**Code Connect snippet is an existence oracle, not spec truth.** The Code Connect index answers "does this component already exist and is it bound", nothing more. A Code Connect snippet's contents are NOT authoritative for copy or for what the new screen needs - they describe what the codebase currently maps. Drift between a snippet and the current design is logged ONCE as a design-system-maintenance note in Section 20 (Open Questions), never as a per-string verification row.
+
+### 6.X Varyant / prop kapsamı - Variant / property coverage
+
+Completeness audit: every property of a consumed Figma component gets exactly one disposition, so the spec proves it examined the whole component surface. An unmapped remainder is a Section 20 Risk.
+
+| Bileşen / Component | Özellik / Property | Karar / Disposition | Not / Note |
+|---|---|---|---|
+| <Name> | <figmaProperty> | implement | <mapped concept / param> |
+| <Name> | <figmaProperty> | skip | <reason not used on this screen> |
+| <Name> | <figmaProperty> | defer | <open question ref> |
+
 ## 7. Tasarım Token'ları / Design Tokens
 
 Per-platform projection. No magic numbers, no raw hex, no raw `.font()`.
@@ -315,9 +362,20 @@ Per-platform projection. No magic numbers, no raw hex, no raw `.font()`.
 |---|---|
 | .h6 | <where> |
 | .body1 | <where> |
+
+### 7.4 Karanlık Mod / Dark Mode
+
+Rendered when the design ships a dark variant (else drop with note `(N/A: no dark variant)`). Each row is a semantic token PAIR, never a literal hue - the token resolves per scheme. Re-verify contrast in dark; a light-passing pair can fail dark.
+
+| Rol / Role | Light token | Dark token | Not / Note (elevation, asset variant, contrast) |
+|---|---|---|---|
+| surface/base | Color.Surface.base | Color.Surface.base (adaptive) | iOS systemBackground; Android tonal elevation (no shadow in dark) |
+| content/primary | Color.Content.primary | Color.Content.primary | contrast >= 4.5:1 rechecked in dark |
+| border/subtle | Color.Border.subtle | Color.Border.subtle | - |
+| <named asset> | icon@light | icon@dark | asset-catalog appearance variant |
 ```
 
-Per-platform projection translates token names: iOS uses `.Spacing.spacingN` enum; Android uses `MaterialTheme.spacing.medium` or design system equivalent; Frontend uses CSS variables `--spacing-md` or Tailwind classes; Backend section omitted.
+Per-platform projection translates token names: iOS uses `.Spacing.spacingN` enum + adaptive `Color(.systemBackground)` / asset appearances; Android uses `MaterialTheme.spacing.medium` + Material 3 color roles with tonal elevation in dark; Frontend uses CSS variables `--spacing-md` / `--color-*` per `prefers-color-scheme`; Backend section omitted.
 
 ## 8. Asset Envanteri / Asset Inventory
 
@@ -379,40 +437,63 @@ List every HTTP status code one by one.
 | 422 | business rule violated | `{"code":"FP-031"}` | <UI> |
 | 500 | server error | `{"code":"GEN-500"}` | <UI> |
 
-### 9.4 Prevention catalog (when applicable)
+### 9.4 Business-rule catalog (when applicable)
 
 | Kod / Code | Anlam / Meaning | UI konumu / UI location |
 |---|---|---|
 | FP-011 | Invalid format | <screen> |
-| PP-211 | Empty result set | <screen> |
+| ERR-211 | Empty result set | <screen> |
 ```
 
 ## 10. Lokalizasyon Anahtarları / Localization Keys
 
-Per-platform projection. Locked 19 - 8-locale full coverage mandatory for new keys.
+Per-platform projection. Locked 20 - shape depends on the project `figma-config` `localization.ownership`. The locale set comes from `localization.locales` (default `tr, en, ar, de, es, fr, it, ru`); never hardcode a locale list.
+
+### Mode A - `in-repo` (default): full per-locale grid
+
+New keys carry filled cells for every configured locale.
 
 ```markdown
 ## 10. Lokalizasyon Anahtarları   <!-- TR -->
 ## 10. Localization Keys          <!-- EN -->
 
-Desteklenen diller: TR, EN, AR, DE, ES, FR, RU, ZH
+Desteklenen diller / Supported locales: <localization.locales, e.g. TR, EN, AR, DE, ES, FR, IT, RU>
 
-| Key | TR | EN | AR | DE | ES | FR | RU | ZH | Source | Status |
-|---|---|---|---|---|---|---|---|---|---|---|
-| <key 1> | <tr> | <en> | <ar> | <de> | <es> | <fr> | <ru> | <zh> | Figma <nodeId> | new |
-| <key 2> | <tr> | <en> | <ar> | <de> | <es> | <fr> | <ru> | <zh> | repo:Localizable.xcstrings | reuse |
-| <key 3> | <tr> | <en> | [bekleniyor: çeviri ekibi] | [bekleniyor: çeviri ekibi] | ... | ... | ... | ... | Figma | partial |
+| Key | <loc1> | <loc2> | ... | Source | Status |
+|---|---|---|---|---|---|
+| <key 1> | <val> | <val> | ... | Figma annotation <nodeId> | new |
+| <key 2> | <val> | <val> | ... | repo:Localizable.xcstrings | reuse |
+| <key 3> | <tr> | <en> | [bekleniyor: çeviri ekibi] / [pending: translation team] | Figma annotation <nodeId> | partial |
 ```
 
-Status values:
-
 | Status | Meaning |
 |---|---|
-| reuse | Existing namespace, no new translation needed |
-| new | New key, all 8 locales must be filled |
-| partial | TR + EN filled, remaining 6 locales pending translation team. Dispatch report flags `i18n_pending: <count>` as blocker. |
+| reuse | Existing key, no new translation needed |
+| new | New key, all configured locales must be filled |
+| partial | Base locales filled, rest pending translation team. Dispatch flags `i18n_pending: <count>` as blocker. |
+
+### Mode B - `externally-owned`: keys + ownership, values deferred
+
+Per-locale values are owned by `localization.authoringPipeline` and are NOT hand-filled here (they would be overwritten by the owning system and were never the analyst's to write). List the key, its status, the copy source, and the `localization.baseLanguage` value only.
 
-Per-platform projection:
+```markdown
+## 10. Lokalizasyon Anahtarları   <!-- TR -->
+## 10. Localization Keys          <!-- EN -->
+
+Sahiplik / Ownership: <localization.authoringPipeline>  (per-locale values authored there)
+Temel dil / Base language: <localization.baseLanguage>
+
+| Key (<keyPattern>) | Durum / Status | Kopya kaynağı / Copy source | Temel değer / Base value | Sahiplik / Ownership |
+|---|---|---|---|---|
+| <Namespace.Case> | new | Figma annotation <nodeId> | <base-language value> | <authoringPipeline> |
+| <Namespace.Case> | reuse | existing catalog | (existing) | <authoringPipeline> |
+```
+
+Gate (Mode B): the base-language value is present (sourced from the Figma annotation per Locked 3) AND the ownership reference is cited. A key missing its base-language value is a blocker - at runtime a missing base value renders the raw `Namespace.Case` key on screen. Fabricated per-locale values are rejected.
+
+Label-authoring contract (Mode B): the analysis names each label and its base copy; it does NOT write per-locale values or hand-edit the owning system's files. A `new` key is a pure addition (auto-mergeable by the authoring pipeline). A `reuse` key that needs a copy change is an EDIT - flag it as review-gated (the owning pipeline requires approval) and never silently overwrite. The base copy always comes from the Figma annotation; when the annotation is missing a language the authoring pipeline expects, emit a Section 20 row rather than inventing it.
+
+Per-platform projection (both modes):
 
 | Platform | File format | Key convention | Example |
 |---|---|---|---|
@@ -426,15 +507,16 @@ Per-platform projection:
 ```markdown
 ## 11. Analytics
 
-| Event | Parametreler / Params | Tetiklenme / Trigger | Source | Status |
+| Event | Parametreler / Params | Tetiklenme / Trigger (story / rule) | Source | Status |
 |---|---|---|---|---|
-| <event_name> | <param1, param2> | <when> | <Firebase schema / repo / Confluence> | new |
-| <event_name> | <params> | <when> | <source> | reuse |
+| <event_name> | <param1, param2> | 4.1 happy path / BR-<slug>-01 | <Firebase schema / repo / Confluence> | new |
+| <event_name> | <params> | <story or BR id> | <source> | reuse |
 
+Each event's Trigger cites the user story (Section 4) or business rule (`BR-` id, Section 4.4) it fires on, so the analytics plan traces to behavior (Locked 31).
 PII redaction: <list of fields hashed before telemetry>
 ```
 
-Locked 11 - direct-match events emit reuse rows. Locked 17 - PII fields (PNR, surname, ffp number) hashed before emit.
+Locked 11 - direct-match events emit reuse rows. Locked 17 - PII fields (email, phone, national ID) hashed before emit.
 
 ## 12. Deeplink ve Push Notification / Deeplink and Push
 
@@ -530,7 +612,7 @@ Locked 21 - platform-agnostic concept layer rendered with repo conventions.
 <rendered navigator interface per Pass B>
 \`\`\`
 
-### 13.6 DI registration
+### 13.5.1 DI registration
 
 \`\`\`<lang>
 <rendered DI register line per Pass B>
@@ -548,28 +630,28 @@ One preview entry per variant matters for Xcode Canvas and snapshot test alignme
 | Default | LTR Dark | dark mode regression check |
 | Default | RTL Light | RTL layout regression |
 | Default | Dynamic Type accessibilityLarge | scaling regression |
-| Error state | LTR Light | empty state, prevention message |
+| Error state | LTR Light | empty state, error message |
 | Loading state | LTR Light | skeleton or spinner |
-| Edge case (e.g. long copy, single passenger) | LTR Light | optional, when distinct from canonical |
+| Edge case (e.g. long copy, single item) | LTR Light | optional, when distinct from canonical |
 
 Preview snippet (Pass B fills variant list per Phase 1c convention):
 
 \`\`\`swift
 #Preview("Default") {
-    PassengerFlightView(viewModel: .preview(.idle))
+    UserProfileView(viewModel: .preview(.idle))
 }
 
-#Preview("Error - PP-211") {
-    PassengerFlightView(viewModel: .preview(.error(.PP_211)))
+#Preview("Error - ERR-211") {
+    UserProfileView(viewModel: .preview(.error(.PP_211)))
 }
 
 #Preview("Dark") {
-    PassengerFlightView(viewModel: .preview(.idle))
+    UserProfileView(viewModel: .preview(.idle))
         .preferredColorScheme(.dark)
 }
 
 #Preview("RTL") {
-    PassengerFlightView(viewModel: .preview(.idle))
+    UserProfileView(viewModel: .preview(.idle))
         .environment(\.layoutDirection, .rightToLeft)
 }
 \`\`\`
@@ -610,11 +692,22 @@ Per-platform projection.
 ## 15. Test Planı   <!-- TR -->
 ## 15. Test Plan    <!-- EN -->
 
-### 15.1 Birim testleri / Unit tests
+### 15.1 Birim testleri / Unit tests (kural bazlı / rule-driven)
 
-| Test | Hedef / Target |
-|---|---|
-| <test name per C4 convention> | <what it verifies> |
+Locked 31 - one sub-table per business rule from Section 4.4. Enumerate the cases: happy, boundary (min/max, off-by-one), error/failure, empty/nil. Each row is Given / When / Then plus a framework-correct test name that traces back to the `BR-` id. Boundary rows collapse into one parameterized test.
+
+Framework per platform (from Phase 1c conventions; these are the modern defaults): iOS Swift Testing (`@Test`, `@Suite`, `@Test(arguments:)` for boundary tables, `#expect` / `#require`); Android JUnit5 + MockK (`coEvery` / `coVerify`) + Turbine (`flow.test { awaitItem() }`) + coroutines-test (`runTest`, `StandardTestDispatcher`); Backend pytest (parametrize); Frontend Vitest.
+
+**BR-<slug>-01**
+
+| Senaryo / Case | Given | When | Then | Test adı / name |
+|---|---|---|---|---|
+| happy | <state> | <action> | <expected> | `func rule_validInput_returnsExpected()` ^[C4 <conf>] |
+| boundary | <edge state> | <action> | <expected> | `@Test(arguments:)` parametrized |
+| error | <failure state> | <action> | <error/emission> | `func rule_failure_emitsError()` |
+| empty/nil | <empty state> | <action> | <default/guard> | `func rule_empty_returnsIdle()` |
+
+(Repeat one sub-table per rule. A rule with no unit-test row fails the dispatch gate, Locked 31.)
 
 ### 15.2 Görsel regresyon / Snapshot tests
 
@@ -636,11 +729,11 @@ Cihaz boyutları / Device sizes: <list>
 
 ### 15.4 Kabul senaryoları / Acceptance scenarios
 
-Gherkin scenarios from Section 4 mapped to UI test names.
+Section 4 Gherkin scenarios + their `BR-` ids mapped to test names.
 
-| Senaryo | UI test |
-|---|---|
-| 4.1 happy path | <XCUITest / Espresso / Playwright name> |
+| Senaryo | BR ID | Test |
+|---|---|---|
+| 4.1 happy path | BR-<slug>-01 | <unit or UI test name> |
 
 ### 15.5 Performans bütçesi / Performance budget
 
@@ -649,6 +742,16 @@ Gherkin scenarios from Section 4 mapped to UI test names.
 | Cold start to ready | <ms> |
 | Scroll FPS | 60 |
 | Memory peak | <MB> |
+
+### 15.6 UI test senaryoları / UI test scenarios (OPTIONAL)
+
+Rendered ONLY when `state.analysisSpec.options.uiTests == true` (Phase 0 Step 5a opt-in); otherwise omitted. UI tests are the most expensive tier - reserve for high-risk / revenue-connected cross-screen flows, not per-element coverage. Selectors are stable ids (iOS `accessibilityIdentifier`, Android `Modifier.testTag` / `contentDescription`), never localized text, so the flow survives copy/locale changes and an agent can generate it mechanically.
+
+| Flow ID | Öncelik / Priority (why it earns a UI test) | Adımlar / Steps | Seçiciler / Selectors | Doğrulamalar / Assertions | Ön koşullar / Preconditions | BR ID |
+|---|---|---|---|---|---|---|
+| UI-<slug>-01 | <high-risk reason> | <ordered user actions> | <accessibilityIdentifier / testTag> | <visible state / navigation / error> | <seeded data / launch args / mocked network> | BR-<slug>-NN |
+
+Framework: iOS XCUITest (`waitForExistence`, identifier-driven); Android Compose UI test (`createComposeRule`, `onNodeWithTag`) or Espresso for View-based screens.
 ```
 
 ## 16. Erişilebilirlik / Accessibility
@@ -659,17 +762,29 @@ Per-platform projection. WCAG 2.2 AA + Apple HIG + Material A11y.
 ## 16. Erişilebilirlik   <!-- TR -->
 ## 16. Accessibility     <!-- EN -->
 
-| Madde / Item | Durum / Status | Notlar / Notes |
-|---|---|---|
-| Unique identifier on every interactive element | required | <per C5 convention> |
-| Minimum tap target (iOS 44x44 pt / Android 48x48 dp / Web 44x44 px) | required | |
-| Screen reader label (accessibilityLabel / contentDescription / aria-label) | required | |
-| Hint text (accessibilityHint / stateDescription / aria-description) | optional | |
-| Dynamic Type / font scaling support | required | |
-| Contrast ratio >= 4.5:1 | required | |
-| State expressed beyond colour | required | |
-| Keyboard navigation (web only) | required | tabindex + focus order |
-| Voice Over / TalkBack reading order | required | |
+### 16.1 Kontrol listesi / Checklist (always)
+
+| Madde / Item | Durum / Status | Notlar / Notes | WCAG 2.2 |
+|---|---|---|---|
+| Unique identifier on every interactive element | required | <per C5 convention> | 4.1.2 |
+| Minimum tap target (iOS 44x44 pt / Android 48x48 dp / Web 44x44 px) | required | exceeds AA | 2.5.8 |
+| Screen reader label (accessibilityLabel / contentDescription / aria-label) | required | | 1.1.1 / 4.1.2 |
+| Hint text (accessibilityHint / stateDescription / aria-description) | optional | | 4.1.2 |
+| Dynamic Type / font scaling to 200% | required | | 1.4.4 |
+| Contrast ratio >= 4.5:1 (text) / 3:1 (large) | required | recheck in dark | 1.4.3 |
+| State expressed beyond colour | required | | 1.4.1 |
+| Reduce motion honored | required | | 2.3.3 |
+| Keyboard navigation (web only) | required | tabindex + focus order | 2.1.1 / 2.4.3 |
+| Voice Over / TalkBack reading order | required | see 16.2 when full depth | 2.4.3 |
+
+### 16.2 Ekran okuyucu gezinme / Screen-reader walkthrough (OPTIONAL)
+
+Rendered ONLY when `state.analysisSpec.options.a11yDepth == "full"` (Phase 0 Step 5a opt-in); otherwise omitted. An ordered reading-order script that is BOTH the implementation spec and the manual VoiceOver / TalkBack test. One row per focus stop, in traversal order.
+
+| # | Odak / Focus target | Seslendirilen / Announced (label + role/trait + value + hint) | Hareket / Gesture | Sonuç / Resulting state |
+|---|---|---|---|---|
+| 1 | <element + selector> | "<label>, <role>, <value>. <hint>" | swipe right | focus moves to 2 |
+| 2 | <element> | "<...>" | double-tap | <navigation / state change> |
 ```
 
 ## 17. Güvenlik ve Gizlilik / Security and Privacy
@@ -700,17 +815,15 @@ OWASP MASVS quick check:
 
 ## 18. Yayılım Planı / Rollout Plan
 
+Compact checklist only (default-drop per the omission table when the pipeline's own commit/PR/rollout phase already covers it). Include a row ONLY when it carries feature-specific information beyond the standard pipeline flow.
+
 ```markdown
 ## 18. Yayılım Planı   <!-- TR -->
 ## 18. Rollout Plan    <!-- EN -->
 
-| Aşama / Stage | Aksiyon / Action |
-|---|---|
-| Development | feature branch <name> |
-| Code review | <number of approvals, who> |
-| QA test | <devices and versions> |
-| Staged rollout | <internal -> beta -> production %> |
-| Rollback | <remote flag name> |
+- Staged rollout: <internal -> beta -> production %, or "standard pipeline flow">
+- Feature flag / rollback: <remote flag name, or "none">
+- QA gate: <feature-specific device/version notes, or "standard">
 ```
 
 ## 19. Değerlendirilen Alternatifler / Alternatives Considered
@@ -779,13 +892,11 @@ Footer. Optional in Lite mode. Alphabetical.
 
 | Kısaltma / Abbreviation | Açıklama / Description |
 |---|---|
-| APIS | Advance Passenger Information System |
 | ATS | App Transport Security |
 | BFF | Backend For Frontend |
 | CTA | Call To Action |
-| FFP | Frequent Flyer Programme |
-| KVKK | Kişisel Verilerin Korunması Kanunu |
-| PNR | Passenger Name Record |
+| DTO | Data Transfer Object |
+| SSOT | Single Source of Truth |
 | WCAG | Web Content Accessibility Guidelines |
 ```
 
@@ -817,19 +928,19 @@ Conventions extracted: feature-first + clean arch, `<Feature>ViewModel`, sealed
 
 ```swift
 @MainActor
-final class PassengerFlightViewModel: ObservableObject {
-    @Published private(set) var state: PassengerFlightUIState = .loading
-    private let fetchUseCase: FetchPassengerFlightUseCaseProtocol
+final class UserProfileViewModel: ObservableObject {
+    @Published private(set) var state: UserProfileUIState = .loading
+    private let fetchUseCase: FetchUserProfileUseCaseProtocol
 
-    init(fetchUseCase: FetchPassengerFlightUseCaseProtocol) {
+    init(fetchUseCase: FetchUserProfileUseCaseProtocol) {
         self.fetchUseCase = fetchUseCase
     }
 
     func onAppear() async {
         do {
             let result = try await fetchUseCase.execute()
-            state = .idle(passengers: result.passengers, flights: result.flights)
-        } catch let error as PreventionError {
+            state = .idle(profile: result.profile)
+        } catch let error as DomainError {
             state = .error(error.code)
         } catch {
             state = .error(.generic)
@@ -837,17 +948,17 @@ final class PassengerFlightViewModel: ObservableObject {
     }
 }
 
-enum PassengerFlightUIState {
+enum UserProfileUIState {
     case loading
-    case idle(passengers: [PassengerEntity], flights: [FlightEntity])
-    case error(PreventionCode)
+    case idle(profile: ProfileEntity)
+    case error(DomainErrorCode)
 }
 ```
 
-Folder: `Domains/Checkin/Sources/Checkin/Screens/PassengerAndFlightSelection/Presentation/ViewModel/`
+Folder: `Domains/Profile/Sources/Profile/Screens/ProfileEditor/Presentation/ViewModel/`
 Test name: `@Test func fetch_validInput_returnsIdle()`
-Identifier: `passengerFlight.continueButton`
-Localization key: `PassengerFlight.ContinueButton`
+Identifier: `userProfile.continueButton`
+Localization key: `UserProfile.ContinueButton`
 
 ## Android render example
 
@@ -855,97 +966,96 @@ Conventions extracted: feature module + clean arch, `<Feature>ViewModel`, sealed
 
 ```kotlin
 @HiltViewModel
-class PassengerFlightViewModel @Inject constructor(
-    private val fetchUseCase: FetchPassengerFlightUseCase
+class UserProfileViewModel @Inject constructor(
+    private val fetchUseCase: FetchUserProfileUseCase
 ) : ViewModel() {
-    private val _state = MutableStateFlow<PassengerFlightUiState>(PassengerFlightUiState.Loading)
-    val state: StateFlow<PassengerFlightUiState> = _state.asStateFlow()
+    private val _state = MutableStateFlow<UserProfileUiState>(UserProfileUiState.Loading)
+    val state: StateFlow<UserProfileUiState> = _state.asStateFlow()
 
     fun onAppear() {
         viewModelScope.launch {
             try {
                 val result = fetchUseCase.execute()
-                _state.value = PassengerFlightUiState.Idle(result.passengers, result.flights)
-            } catch (e: PreventionException) {
-                _state.value = PassengerFlightUiState.Error(e.code)
+                _state.value = UserProfileUiState.Idle(result.profile)
+            } catch (e: DomainException) {
+                _state.value = UserProfileUiState.Error(e.code)
             }
         }
     }
 }
 
-sealed interface PassengerFlightUiState {
-    data object Loading : PassengerFlightUiState
-    data class Idle(val passengers: List<Passenger>, val flights: List<Flight>) : PassengerFlightUiState
-    data class Error(val code: PreventionCode) : PassengerFlightUiState
+sealed interface UserProfileUiState {
+    data object Loading : UserProfileUiState
+    data class Idle(val profile: Profile) : UserProfileUiState
+    data class Error(val code: DomainErrorCode) : UserProfileUiState
 }
 ```
 
-Folder: `feature/checkin/src/main/java/<package>/passengerflight/ui/`
+Folder: `feature/profile/src/main/java/<package>/userprofile/ui/`
 Test name: `fun fetch_validInput_returnsIdle()`
-testTag: `passengerFlightContinueButton`
-strings.xml: `passenger_flight_continue_button`
+testTag: `userProfileContinueButton`
+strings.xml: `user_profile_continue_button`
 
 ## Backend render example
 
 Conventions extracted: layered Python FastAPI, router + service + repository, Pydantic DTO, pytest snake_case, FastAPI Depends.
 
 ```python
-class PassengerFlightService:
+class UserProfileService:
     def __init__(
         self,
-        repository: PassengerFlightRepository,
-        validator: PassengerSelectionValidator,
+        repository: UserProfileRepository,
+        validator: ProfileInputValidator,
     ):
         self.repository = repository
         self.validator = validator
 
-    async def fetch(self, request: PassengerFlightIn) -> PassengerFlightOut:
-        passengers = await self.repository.search_passengers(request.pnr, request.surname)
-        flights = await self.repository.get_flight_details(request.pnr)
-        return PassengerFlightOut(passengers=passengers, flights=flights)
+    async def fetch(self, request: UserProfileIn) -> UserProfileOut:
+        profile = await self.repository.get_profile(request.user_id)
+        return UserProfileOut(profile=profile)
 
 
-@router.post("/start-checkin", response_model=PassengerFlightOut)
-async def start_checkin(
-    request: PassengerFlightIn,
-    service: PassengerFlightService = Depends(get_passenger_flight_service),
-) -> PassengerFlightOut:
+@router.post("/update-profile", response_model=UserProfileOut)
+async def update_profile(
+    request: UserProfileIn,
+    service: UserProfileService = Depends(get_user_profile_service),
+) -> UserProfileOut:
     return await service.fetch(request)
 ```
 
-Folder: `app/api/checkin/`, `app/services/checkin/`, `app/schemas/checkin/`
-Test name: `def test_fetch_valid_input_returns_passenger_list():`
-OpenAPI operationId: `startCheckin`
+Folder: `app/api/profile/`, `app/services/profile/`, `app/schemas/profile/`
+Test name: `def test_fetch_valid_input_returns_profile():`
+OpenAPI operationId: `updateProfile`
 
 ## Frontend render example
 
 Conventions extracted: Next.js App Router, feature folder, React Query hooks, Zustand stores, Vitest, kebab data-testid, hierarchical dot camelCase i18n.
 
 ```tsx
-type PassengerFlightState =
+type UserProfileState =
   | { kind: "loading" }
-  | { kind: "idle"; passengers: Passenger[]; flights: Flight[] }
-  | { kind: "error"; code: PreventionCode };
+  | { kind: "idle"; profile: Profile }
+  | { kind: "error"; code: DomainErrorCode };
 
-export function usePassengerFlight(pnr: string, surname: string) {
-  return useQuery<PassengerFlightDto, PreventionError>({
-    queryKey: ["passenger-flight", pnr, surname],
-    queryFn: () => passengerFlightApi.fetch({ pnr, surname }),
+export function useUserProfile(userId: string) {
+  return useQuery<UserProfileDto, DomainError>({
+    queryKey: ["user-profile", userId],
+    queryFn: () => userProfileApi.fetch({ userId }),
   });
 }
 
-export function PassengerFlightPage({ pnr, surname }: Props) {
-  const query = usePassengerFlight(pnr, surname);
+export function UserProfilePage({ userId }: Props) {
+  const query = useUserProfile(userId);
   if (query.isLoading) return <LoadingState />;
   if (query.isError) return <ErrorState code={query.error.code} />;
-  return <PassengerFlightContent data={query.data} />;
+  return <UserProfileContent data={query.data} />;
 }
 ```
 
-Folder: `src/features/checkin/passenger-flight/{components,hooks,api,types}/`
+Folder: `src/features/profile/user-profile/{components,hooks,api,types}/`
 Test name: `it('returns idle state for valid input', ...)`
-data-testid: `passenger-flight-continue-button`
-i18n key: `passengerFlight.continueButton`
+data-testid: `user-profile-continue-button`
+i18n key: `userProfile.continueButton`
 
 ---