p19-bug-fixes

openspec/changes/p19-vj-defects/specs/indic-font-typography-improvement/spec.md

@@ -0,0 +1,32 @@
+## ADDED Requirements
+
+### Requirement: System uses smooth, readable Indic fonts
+The system SHALL use alternative Indic fonts that provide better readability and visual smoothness compared to the current Noto Sans Tamil and Noto Sans Malayalam fonts.
+
+#### Scenario: Tamil font is smooth and readable
+- **WHEN** Tamil content is displayed
+- **THEN** the font SHALL render with smooth edges without rough or pixelated appearance
+- **AND** the font SHALL maintain readability at various sizes (14px to 32px)
+- **AND** the font SHALL support all Tamil Unicode characters including conjuncts and ligatures
+
+#### Scenario: Malayalam font is smooth and readable
+- **WHEN** Malayalam content is displayed
+- **THEN** the font SHALL render with smooth edges without rough or pixelated appearance
+- **AND** the font SHALL maintain readability at various sizes (14px to 32px)
+- **AND** the font SHALL support all Malayalam Unicode characters including conjuncts and ligatures
+
+#### Scenario: Font loading is optimized
+- **WHEN** Indic fonts are loaded
+- **THEN** the fonts SHALL load asynchronously to prevent layout shift
+- **AND** a system font fallback SHALL display immediately while Indic fonts load
+- **AND** the font-display strategy SHALL be "swap" to ensure text remains visible
+
+#### Scenario: Font weights are available
+- **WHEN** Indic content requires different font weights
+- **THEN** at minimum regular (400) and bold (700) weights SHALL be available
+- **AND** the bold weight SHALL be visually distinguishable from regular
+
+#### Scenario: Font fallback chain is defined
+- **WHEN** Indic fonts fail to load or are not supported
+- **THEN** the system SHALL fall back through: preferred Indic font → Noto Sans [language] → system-ui → sans-serif
+- **AND** fallback fonts SHALL maintain similar character proportions to minimize layout shift

openspec/changes/p19-vj-defects/specs/indic-language-mobile-optimization/spec.md

@@ -0,0 +1,30 @@
+## ADDED Requirements
+
+### Requirement: Hero block adapts to Indic languages on mobile viewports
+The system SHALL adjust hero block typography and layout when displaying Tamil or Malayalam content on mobile devices to ensure full content visibility.
+
+#### Scenario: Tamil content on mobile viewport
+- **WHEN** the hero block displays Tamil content on a mobile viewport (width ≤ 640px)
+- **THEN** the hero block height SHALL increase to accommodate the larger text
+- **AND** the hero title font size SHALL be reduced from 1.9rem to 1.6rem
+- **AND** the hero summary font size SHALL be reduced from 1.08rem to 0.95rem
+- **AND** the entire hero content including headline and summary SHALL remain visible without clipping
+
+#### Scenario: Malayalam content on mobile viewport
+- **WHEN** the hero block displays Malayalam content on a mobile viewport (width ≤ 640px)
+- **THEN** the hero block height SHALL increase to accommodate the larger text
+- **AND** the hero title font size SHALL be reduced from 1.9rem to 1.6rem
+- **AND** the hero summary font size SHALL be reduced from 1.08rem to 0.95rem
+- **AND** the entire hero content including headline and summary SHALL remain visible without clipping
+
+#### Scenario: Hero image scales appropriately on mobile
+- **WHEN** the hero block is displayed on a mobile viewport (width ≤ 640px)
+- **THEN** the hero image height SHALL be reduced from 300px to 220px
+- **AND** the image SHALL maintain its aspect ratio
+- **AND** the image SHALL not overflow its container
+
+#### Scenario: Content remains readable after adjustments
+- **WHEN** typography adjustments are applied for mobile Indic content
+- **THEN** text SHALL remain legible with adequate line height (minimum 1.5)
+- **AND** text SHALL maintain sufficient contrast against background
+- **AND** touch targets SHALL remain at least 44px in height

openspec/changes/p19-vj-defects/specs/share-and-contact-microinteractions/spec.md

@@ -0,0 +1,14 @@
+## MODIFIED Requirements
+
+### Requirement: Contact affordance provides randomized safe microcopy
+The contact link SHALL present randomized, policy-safe helper messages to encourage feedback, including keyboard-triggered visibility for accessibility.
+
+#### Scenario: Randomized helper tooltip
+- **WHEN** user hovers or nears the contact affordance
+- **THEN** a tooltip-style helper message is shown from a predefined safe message pool
+- **AND** message language avoids profanity/offensive/racist/sexist/misogynistic content
+
+#### Scenario: Keyboard-triggered helper tooltip
+- **WHEN** a keyboard user focuses the contact email affordance
+- **THEN** helper tooltip content becomes visible and readable
+- **AND** tooltip dismisses cleanly on blur without trapping focus