@nano-step/skill-manager 5.6.0 → 5.6.1

package/skills/rri-t-testing/assets/rri-t-persona-interview.md

@@ -0,0 +1,249 @@
+# RRI-T Persona Interview — {Feature Name}
+
+**Feature:** {feature-name}
+**Date:** {YYYY-MM-DD}
+**Interviewer:** {agent/person}
+
+## Interview Summary
+| Persona | Questions Generated | Key Concerns |
+|---------|-------------------|--------------|
+| End User | 0/25 | |
+| Business Analyst | 0/25 | |
+| QA Destroyer | 0/25 | |
+| DevOps Tester | 0/25 | |
+| Security Auditor | 0/25 | |
+| **Total** | **0/125** | |
+
+---
+
+## Persona 1: End User (Nguoi dung cuoi)
+
+### Context
+As a household member using {feature-name} daily to manage my family's shared resources, I need the feature to work reliably across different devices, network conditions, and usage patterns. I care about speed, clarity, and not losing my work.
+
+### Questions
+1. What happens when I add an inventory item while my phone has weak 3G signal? `[PERF]` `[D3: Performance]`
+2. What happens when I start editing a shopping list on mobile, then switch to desktop mid-task? `[DATA]` `[D5: Data Integrity]`
+3. What happens when I search for "nguyen" but the item name is "Nguyen Van A"? `[DATA]` `[D1: UI/UX]`
+4. What happens when I accidentally navigate away from a half-filled form? `[DATA]` `[D1: UI/UX]`
+5. What happens when I try to delete an item that another household member is currently editing? `[DATA]` `[D5: Data Integrity]`
+6. What happens when I upload a photo of a receipt and the file is 10MB? `[PERF]` `[D3: Performance]`
+7. What happens when I filter 500+ inventory items by expiration date on a mid-range phone? `[PERF]` `[D3: Performance]`
+8. What happens when I receive a phone call while recording a voice note for a meal plan? `[TECH]` `[D7: Edge Cases]`
+9. What happens when the app shows "1,000,000d" instead of "1.000.000d" for Vietnamese currency? `[BUS]` `[D1: UI/UX]`
+10. What happens when I'm offline for 2 days and then reconnect with 50 pending changes? `[DATA]` `[D6: Infrastructure]`
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 2: Business Analyst (Phan tich nghiep vu)
+
+### Context
+As someone responsible for ensuring business rules are correctly implemented, I need to verify that household permissions, data ownership, financial calculations, and multi-household scenarios work as specified. I care about data consistency and rule enforcement.
+
+### Questions
+1. What happens when a household member with "viewer" role tries to delete an inventory item? `[SEC]` `[D4: Security]`
+2. What happens when a user belongs to 3 households and switches between them rapidly? `[DATA]` `[D5: Data Integrity]`
+3. What happens when two members simultaneously mark the same shopping list item as "purchased"? `[DATA]` `[D5: Data Integrity]`
+4. What happens when a household admin removes a member who has pending edits? `[BUS]` `[D4: Security]`
+5. What happens when the total expense calculation includes items in different currencies (VND and USD)? `[BUS]` `[D5: Data Integrity]`
+6. What happens when a recurring meal plan conflicts with a one-time event on the same date? `[BUS]` `[D7: Edge Cases]`
+7. What happens when a user tries to share an inventory item with a household they don't belong to? `[SEC]` `[D4: Security]`
+8. What happens when the system calculates "items expiring in 3 days" across different timezones? `[BUS]` `[D7: Edge Cases]`
+9. What happens when a household reaches the maximum allowed inventory items (if there's a limit)? `[BUS]` `[D7: Edge Cases]`
+10. What happens when a deleted household still has active shopping lists in other members' offline caches? `[DATA]` `[D6: Infrastructure]`
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 3: QA Destroyer (Pha hoai vien QA)
+
+### Context
+As someone whose job is to break things, I need to find every edge case, race condition, and unexpected input that could crash the system or corrupt data. I care about boundary conditions, malformed inputs, and timing attacks.
+
+### Questions
+1. What happens when I paste 50,000 characters into the "item name" field? `[DATA]` `[D7: Edge Cases]`
+2. What happens when I rapidly click "save" 20 times in 1 second? `[PERF]` `[D7: Edge Cases]`
+3. What happens when I set my device date to 2099 and create an inventory item? `[DATA]` `[D7: Edge Cases]`
+4. What happens when I upload a file named `"; DROP TABLE inventory; --"` as an item photo? `[SEC]` `[D4: Security]`
+5. What happens when I create an item with expiration date "yesterday" and quantity "-5"? `[DATA]` `[D7: Edge Cases]`
+6. What happens when I open the app in 10 browser tabs and edit the same item in all of them? `[DATA]` `[D5: Data Integrity]`
+7. What happens when I force-kill the app during a GraphQL mutation? `[DATA]` `[D6: Infrastructure]`
+8. What happens when I inject `<script>alert('xss')</script>` into a meal plan description? `[SEC]` `[D4: Security]`
+9. What happens when I create a circular dependency (Item A requires Item B, Item B requires Item A)? `[BUS]` `[D7: Edge Cases]`
+10. What happens when I change my device timezone mid-session and create a timestamped event? `[DATA]` `[D7: Edge Cases]`
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 4: DevOps Tester (Kiem thu ha tang)
+
+### Context
+As someone responsible for deployment, monitoring, and infrastructure reliability, I need to verify that the feature works under load, handles server restarts gracefully, and doesn't leak resources. I care about scalability, observability, and recovery.
+
+### Questions
+1. What happens when the GraphQL server restarts while a user is mid-sync? `[OPS]` `[D6: Infrastructure]`
+2. What happens when 100 users simultaneously bulk-import 500 inventory items each? `[PERF]` `[D3: Performance]`
+3. What happens when the database connection pool is exhausted during peak usage? `[OPS]` `[D6: Infrastructure]`
+4. What happens when the CDN serving item photos goes down? `[OPS]` `[D6: Infrastructure]`
+5. What happens when a GraphQL query takes longer than the 30-second timeout? `[PERF]` `[D3: Performance]`
+6. What happens when the Redis cache is cleared while users have active sessions? `[OPS]` `[D6: Infrastructure]`
+7. What happens when a deployment rolls out a new schema version while old clients are still connected? `[OPS]` `[D2: API]`
+8. What happens when disk space runs out during a photo upload? `[OPS]` `[D6: Infrastructure]`
+9. What happens when the monitoring system detects 500 errors but the app still appears functional? `[OPS]` `[D6: Infrastructure]`
+10. What happens when a user's offline queue grows to 1000+ pending mutations? `[PERF]` `[D3: Performance]`
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Persona 5: Security Auditor (Kiem toan bao mat)
+
+### Context
+As someone responsible for security compliance, I need to verify that authentication, authorization, data exposure, and audit trails are properly implemented. I care about access control, data leakage, and attack surface.
+
+### Questions
+1. What happens when a user's JWT token expires mid-session? `[SEC]` `[D4: Security]`
+2. What happens when a user tries to access another household's data by guessing the household ID? `[SEC]` `[D4: Security]`
+3. What happens when a removed household member still has cached data on their device? `[SEC]` `[D4: Security]`
+4. What happens when someone intercepts the GraphQL request and replays it with modified variables? `[SEC]` `[D4: Security]`
+5. What happens when a user tries to upload a malicious file disguised as an image? `[SEC]` `[D4: Security]`
+6. What happens when the audit log shows who deleted an item, but the user claims they didn't? `[SEC]` `[D4: Security]`
+7. What happens when a user shares their session token with someone outside the household? `[SEC]` `[D4: Security]`
+8. What happens when someone uses SQL injection in a search query (even though it's GraphQL)? `[SEC]` `[D4: Security]`
+9. What happens when a user's password is compromised and they don't realize it for 3 days? `[SEC]` `[D4: Security]`
+10. What happens when the system logs sensitive data (like financial amounts) in plain text? `[SEC]` `[D4: Security]`
+11. 
+12. 
+13. 
+14. 
+15. 
+16. 
+17. 
+18. 
+19. 
+20. 
+21. 
+22. 
+23. 
+24. 
+25. 
+
+### Key Concerns
+- {list concerns discovered}
+
+---
+
+## Consolidation Method
+
+After completing all persona interviews, consolidate findings into the risk register:
+
+1. **Group by Category:** Organize questions by risk category (TECH, SEC, PERF, DATA, BUS, OPS)
+2. **Identify Patterns:** Look for concerns raised by multiple personas
+3. **Score Risks:** For each unique risk, assign Probability (1-3) x Impact (1-3)
+4. **Prioritize:** Sort by risk score descending
+5. **Map to Dimensions:** Ensure each risk maps to at least one dimension (D1-D7)
+6. **Create Test Cases:** Convert high-priority risks into test cases using Q-A-R-P-T format
+
+### Consolidation Table
+
+| Risk ID | Description | Raised By | Category | Dimension | P | I | Score |
+|---------|-------------|-----------|----------|-----------|---|---|-------|
+| R-001 | | | | | | | |
+| R-002 | | | | | | | |
+| R-003 | | | | | | | |
+| R-004 | | | | | | | |
+| R-005 | | | | | | | |
+
+---
+
+## Raw Test Ideas (Consolidated)
+| # | Idea | Source Persona | Potential Dimension | Priority Estimate |
+|---|------|---------------|--------------------|--------------------|
+| 1 | | | | |
+| 2 | | | | |
+| 3 | | | | |
+| 4 | | | | |
+| 5 | | | | |
+| 6 | | | | |
+| 7 | | | | |
+| 8 | | | | |
+| 9 | | | | |
+| 10 | | | | |
+| 11 | | | | |
+| 12 | | | | |
+| 13 | | | | |
+| 14 | | | | |
+| 15 | | | | |
+| 16 | | | | |
+| 17 | | | | |
+| 18 | | | | |
+| 19 | | | | |
+| 20 | | | | |

package/skills/rri-t-testing/assets/rri-t-quality-scorecard.md

@@ -0,0 +1,122 @@
+# RRI-T Quality Scorecard
+
+**Feature:** {feature-name}
+**Date:** {YYYY-MM-DD}
+**Assessor:** {agent/person}
+
+## Score Calculation
+
+### Starting Score: 100
+
+---
+
+## Violations
+
+### Critical Violations (-10 each)
+
+| ID | Violation | Description | Present | Penalty |
+|----|-----------|-------------|---------|---------|
+| CRIT-1 | Hard waits | Using sleep/wait instead of proper assertions | Y / N | -10 |
+| CRIT-2 | Missing assertions | Test has no verification of expected outcome | Y / N | -10 |
+| CRIT-3 | CSS selectors | Using fragile CSS selectors instead of semantic locators | Y / N | -10 |
+| CRIT-4 | Conditional flow | Using if/else in test logic (non-deterministic) | Y / N | -10 |
+
+**Critical Subtotal:** -{count} x 10 = -{total}
+
+### High Violations (-5 each)
+
+| ID | Violation | Description | Present | Penalty |
+|----|-----------|-------------|---------|---------|
+| HIGH-1 | No isolation | Tests share state or depend on execution order | Y / N | -5 |
+| HIGH-2 | Duplicate setup | Same setup code repeated across tests | Y / N | -5 |
+| HIGH-3 | Flaky test | Test fails intermittently without code changes | Y / N | -5 |
+| HIGH-4 | Missing error coverage | No tests for error/edge cases | Y / N | -5 |
+
+**High Subtotal:** -{count} x 5 = -{total}
+
+### Medium Violations (-2 each)
+
+| ID | Violation | Description | Present | Penalty |
+|----|-----------|-------------|---------|---------|
+| MED-1 | Vague names | Test names do not describe what is being tested | Y / N | -2 |
+| MED-2 | File > 300 lines | Test file exceeds 300 lines | Y / N | -2 |
+| MED-3 | Test > 90s | Individual test takes longer than 90 seconds | Y / N | -2 |
+| MED-4 | No test ID | Test cases lack unique identifiers | Y / N | -2 |
+
+**Medium Subtotal:** -{count} x 2 = -{total}
+
+### Low Violations (-1 each)
+
+| ID | Violation | Description | Present | Penalty |
+|----|-----------|-------------|---------|---------|
+| LOW-1 | Style inconsistency | Inconsistent naming, formatting, or structure | Y / N | -1 |
+| LOW-2 | Missing comment | Complex logic without explanatory comment | Y / N | -1 |
+
+**Low Subtotal:** -{count} x 1 = -{total}
+
+---
+
+## Violation Tracking
+
+| ID | Description | Severity | Penalty | File/Line |
+|----|-------------|----------|---------|-----------|
+| V-001 | | CRIT / HIGH / MED / LOW | | |
+| V-002 | | | | |
+| V-003 | | | | |
+| V-004 | | | | |
+| V-005 | | | | |
+
+**Total Penalties:** -{total}
+
+---
+
+## Bonuses (+5 each, max +30)
+
+| ID | Criteria | Description | Present | Points |
+|----|----------|-------------|---------|--------|
+| BON-1 | Semantic locators | Uses data-testid, aria-label, role selectors | Y / N | +5 |
+| BON-2 | Data factories | Uses factories/fixtures for test data | Y / N | +5 |
+| BON-3 | Network-first | Mocks/intercepts network for determinism | Y / N | +5 |
+| BON-4 | Isolation | Each test is fully independent | Y / N | +5 |
+| BON-5 | Test IDs | All test cases have unique TC-XXX identifiers | Y / N | +5 |
+| BON-6 | BDD style | Uses Given/When/Then or similar structure | Y / N | +5 |
+
+**Total Bonuses:** +{total} (capped at +30)
+
+---
+
+## Final Score Calculation
+
+| Component | Value |
+|-----------|-------|
+| Starting Score | 100 |
+| Critical Penalties | -{total} |
+| High Penalties | -{total} |
+| Medium Penalties | -{total} |
+| Low Penalties | -{total} |
+| Bonuses | +{total} |
+| **Final Score** | **{score}** |
+
+---
+
+## Grade
+
+| Grade | Score Range | Description |
+|-------|-------------|-------------|
+| A+ | 90-100+ | Excellent - production ready |
+| A | 80-89 | Good - minor improvements suggested |
+| B | 70-79 | Acceptable - improvements needed |
+| C | 60-69 | Below standard - significant issues |
+| F | < 60 | Failing - major rework required |
+
+**Final Grade:** {grade}
+
+---
+
+## Recommendations
+
+| Priority | Recommendation |
+|----------|----------------|
+| 1 | |
+| 2 | |
+| 3 | |

package/skills/rri-t-testing/assets/rri-t-risk-matrix.md

@@ -0,0 +1,87 @@
+# RRI-T Risk Matrix
+
+**Feature:** {feature-name}
+**Owner:** {owner}
+**Date:** {YYYY-MM-DD}
+**Build:** {build-id}
+
+## Risk Register
+
+| ID | Risk Description | Category | Probability | Impact | Score | Mitigation | Status |
+|----|------------------|----------|-------------|--------|-------|------------|--------|
+| R-001 | API rate limiting not tested under load | PERF | 2 | 3 | 6 | Add load test for 100 concurrent users | OPEN |
+| R-002 | User session not invalidated on role change | SEC | 2 | 3 | 6 | Test role revocation mid-session | OPEN |
+| R-003 | Offline sync may duplicate items on reconnect | DATA | 3 | 2 | 6 | Test offline queue with 50+ pending changes | OPEN |
+| R-004 | | | | | | | |
+| R-005 | | | | | | | |
+| R-006 | | | | | | | |
+| R-007 | | | | | | | |
+| R-008 | | | | | | | |
+| R-009 | | | | | | | |
+| R-010 | | | | | | | |
+
+## Scoring Guide
+
+### Probability
+
+| Score | Definition |
+|-------|------------|
+| 1 | Unlikely - well-tested area, minor change |
+| 2 | Possible - moderate complexity, some unknowns |
+| 3 | Likely - new area, high complexity, many dependencies |
+
+### Impact
+
+| Score | Definition |
+|-------|------------|
+| 1 | Low - cosmetic, workaround exists |
+| 2 | Medium - feature degraded, user friction |
+| 3 | High - data loss, security breach, revenue impact |
+
+### Risk Score = Probability x Impact
+
+| Score | Level | Action |
+|-------|-------|--------|
+| 1-2 | LOW | Monitor, test if time permits |
+| 3-5 | MEDIUM | Test with standard coverage |
+| 6-8 | HIGH | Requires mitigation before release |
+| 9 | CRITICAL | Blocks release if unmitigated |
+
+## Category Definitions
+
+| Code | Category | Description |
+|------|----------|-------------|
+| TECH | Technical | Architecture fragility, integration issues, technical debt |
+| SEC | Security | Authentication, authorization, data exposure, vulnerabilities |
+| PERF | Performance | Response time, throughput, scalability, resource usage |
+| DATA | Data | Integrity, corruption, loss, migration, consistency |
+| BUS | Business | Logic errors, calculation mistakes, workflow issues |
+| OPS | Operational | Deployment, monitoring, recovery, configuration |
+
+## Threshold Rules
+
+- Score >= 6: Requires documented mitigation plan
+- Score = 9: Blocks release until mitigated and verified
+- SEC category: Always requires security dimension testing
+- DATA category: Always requires data integrity dimension testing
+
+## Risk Summary
+
+| Metric | Value |
+|--------|-------|
+| Total Risks | {count} |
+| High (>= 6) | {count} |
+| Critical (= 9) | {count} |
+| Mitigated | {count} |
+| Open | {count} |
+
+## Risk by Category
+
+| Category | Count | Highest Score |
+|----------|-------|---------------|
+| TECH | | |
+| SEC | | |
+| PERF | | |
+| DATA | | |
+| BUS | | |
+| OPS | | |

package/skills/rri-t-testing/assets/rri-t-stress-matrix.md

@@ -0,0 +1,100 @@
+# RRI-T Stress Matrix Template
+
+## Feature
+- Name: <feature-name>
+- Owner: <owner>
+- Date: <yyyy-mm-dd>
+- Build/Release: <build-id>
+- Environment: <dev/staging/prod>
+
+## Summary
+This template covers RRI-T 8-axis stress testing for a household management app
+(inventory, meal planning, shopping lists, finances).
+
+## Stress Axes Summary
+| Axis | Name | Focus | Notes |
+| --- | --- | --- | --- |
+| 1 | TIME | Deadlines, bulk ops, timeouts | Burst actions, long-running jobs |
+| 2 | DATA | 1000+ rows, search/filter speed | Large inventory, long history |
+| 3 | ERROR | Undo/redo, auto-save recovery, messages | Resilience, recoverability |
+| 4 | COLLAB | Concurrent editing, conflicts, multi-user | Household members overlap |
+| 5 | EMERGENCY | Interruptions, crash recovery | Browser/device failures |
+| 6 | SECURITY | Access revocation, audit logs, session expiry | Role changes, expiring auth |
+| 7 | INFRA | Server crash, RTO<15m, RPO<5m, offline | Service resilience |
+| 8 | LOCALE | Vietnamese diacritics, VND, GMT+7, overflow | Local UX correctness |
+
+## Axis Combination Matrix (Test Where X)
+| Axis | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| 1 TIME | - | X | X | X | X | X | X | X |
+| 2 DATA | X | - | X | X |  | X | X | X |
+| 3 ERROR | X | X | - | X | X |  | X | X |
+| 4 COLLAB | X | X | X | - |  | X |  | X |
+| 5 EMERGENCY | X |  | X |  | - | X | X |  |
+| 6 SECURITY | X | X |  | X | X | - | X | X |
+| 7 INFRA | X | X | X |  | X | X | - | X |
+| 8 LOCALE | X | X | X | X |  | X | X | - |
+
+## Stress Scenarios
+
+### Axis 1: TIME
+| # | Scenario | Steps | Expected | Priority |
+| --- | --- | --- | --- | --- |
+| S-TIME-001 | Bulk add 500 pantry items before dinner | Start timer 2 min, import CSV of pantry items | Import completes, progress visible, no timeout | P1 |
+| S-TIME-002 | Rapid meal plan edits during 10-min window | Update 10 meals in 60s, save each | Saves succeed, no stale data, UI responsive | P1 |
+| S-TIME-003 | Shopping list sync under poor network | Add 30 items quickly, toggle offline/online | Sync resolves within 60s, no duplicates | P2 |
+| S-TIME-004 | Finance entry auto-save timeout | Create expense, wait 45s idle, resume edit | Auto-save persists, no data loss | P2 |
+
+### Axis 2: DATA
+| # | Scenario | Steps | Expected | Priority |
+| S-DATA-001 | Inventory list 1000+ items | Load inventory with 1200 items | Scroll, search, filter remain under 2s | P1 |
+| S-DATA-002 | Shopping history filter speed | Filter 800 past purchases by category | Results appear under 2s, no UI freeze | P2 |
+| S-DATA-003 | Meal plan calendar 6 months | Open 6-month plan view with 180 entries | Render within 3s, no layout shift | P2 |
+| S-DATA-004 | Finance ledger export 2000 rows | Export 2k ledger rows to CSV | Export completes, file accurate | P2 |
+
+### Axis 3: ERROR
+| # | Scenario | Steps | Expected | Priority |
+| S-ERROR-001 | Undo/redo inventory quantity changes | Change item qty 5 times, undo 5, redo 5 | Exact state restored each step | P1 |
+| S-ERROR-002 | Auto-save recovery after crash | Edit meal notes, force close tab, reopen | Draft restored with last autosave | P1 |
+| S-ERROR-003 | Validation error messages | Add expense with negative value | Clear inline error, no save | P2 |
+| S-ERROR-004 | Failed bulk import rollback | Import malformed CSV for pantry | No partial data, error list shown | P1 |
+
+### Axis 4: COLLAB
+| # | Scenario | Steps | Expected | Priority |
+| S-COLLAB-001 | Two users edit shopping list | User A adds 5 items, User B deletes 2 | Conflict warning, final list consistent | P1 |
+| S-COLLAB-002 | Concurrent budget updates | Two users change monthly budget | Latest change prompts merge dialog | P2 |
+| S-COLLAB-003 | Shared meal plan edit | User A updates recipe, User B updates servings | Both changes applied without loss | P2 |
+| S-COLLAB-004 | New member joins household | Invite new user during active edits | New user sees updated list | P3 |
+
+### Axis 5: EMERGENCY
+| # | Scenario | Steps | Expected | Priority |
+| S-EMERGENCY-001 | Browser crash while editing | Edit grocery item notes, kill browser | Reopen, draft restored | P1 |
+| S-EMERGENCY-002 | Power loss during bulk update | Start bulk pantry update, go offline | Partial changes queued or rolled back | P1 |
+| S-EMERGENCY-003 | Device sleep mid-sync | Start sync, close laptop lid | Resume sync without duplication | P2 |
+| S-EMERGENCY-004 | App reload mid-transaction | Save expense, hit refresh instantly | No double charge, one entry saved | P2 |
+
+### Axis 6: SECURITY
+| # | Scenario | Steps | Expected | Priority |
+| S-SECURITY-001 | Access revoked during edit | Admin removes user role mid-edit | User warned, changes blocked, data safe | P1 |
+| S-SECURITY-002 | Session expiry while shopping | Session expires, user adds item | Redirect to login, item queued | P1 |
+| S-SECURITY-003 | Audit log for finance edits | Edit expense amount | Audit entry with user, time, change | P2 |
+| S-SECURITY-004 | Private list access attempt | Non-member tries to open list | Access denied, no data leak | P1 |
+
+### Axis 7: INFRA
+| # | Scenario | Steps | Expected | Priority |
+| S-INFRA-001 | Server crash during sync | Trigger sync, kill server | Retry logic, no data loss | P1 |
+| S-INFRA-002 | RTO < 15m recovery | Simulate outage, restore service | Service back within 15m, status updated | P1 |
+| S-INFRA-003 | RPO < 5m data recovery | Create 3 entries, failover | Max 5m data loss, latest persists | P1 |
+| S-INFRA-004 | Offline mode for shopping list | Go offline, add 10 items | Local cache used, sync on reconnect | P2 |
+
+### Axis 8: LOCALE
+| # | Scenario | Steps | Expected | Priority |
+| S-LOCALE-001 | Diacritic-insensitive search | Search "nguyen" in household members | Finds "Nguyen" matches | P1 |
+| S-LOCALE-002 | VND currency formatting | View finance summary | Shows "1.000.000d" not "1,000,000" | P1 |
+| S-LOCALE-003 | Vietnamese text overflow | Open long Vietnamese recipe names | No overflow, wraps cleanly | P2 |
+| S-LOCALE-004 | Date format DD/MM/YYYY | View meal plan date header | Displays DD/MM/YYYY | P1 |
+
+## Notes
+- Attach logs, screenshots, and timings for any P1 or P2 failures.
+- Capture device, OS, browser, and network conditions.
+- Link to any incident or bug IDs created from results.