@ryuenn3123/agentic-senior-core 6.16.5 → 6.16.6

package/.agents/plugins/agentic-senior-core/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agentic-senior-core",
-  "version": "6.16.5",
+  "version": "6.16.6",
   "description": "Universal AI coding rules. Write code like a staff engineer.",
   "skills": "./skills/",
   "hooks": "./hooks/hooks.json",

package/.agents/plugins/agentic-senior-core/commands/asc-test.md

@@ -1,2 +1,2 @@
-Run the testing, TDD, verification, and UAT standards from skills/asc-test/SKILL.md. Enforce the Iron Law (no production code without a failing test first), apply verification gates with fresh execution evidence, reproduce bugfixes with regression proofs, design boundary-isolated tests, and diagnose flaky tests.
+Run the testing, TDD, verification, and UAT standards from skills/asc-test/SKILL.md. Enforce test-first discipline (no production code without a failing test first), apply verification gates with fresh execution evidence, reproduce bugfixes with regression proofs, design boundary-isolated tests, and diagnose flaky tests.
 

package/.agents/plugins/agentic-senior-core/commands/asc-ui.md

@@ -1 +1 @@
-Run the UI/UX engineering and anti-slop guidelines from skills/asc-ui/SKILL.md. Clean up verbose microcopy, eliminate redundant headings/subtitles, enforce single-language purity without awkward foreign loanwords, optimize information density, and implement reliable data states.
+Run the UI/UX engineering, typography, and accessibility guidelines from skills/asc-ui/SKILL.md. Clean up verbose microcopy, eliminate redundant headings/subtitles, enforce single-language consistency across interfaces, optimize information density, and implement reliable data states.

package/.agents/plugins/agentic-senior-core/hooks/lib/known-ui-slop-patterns.json

@@ -159,6 +159,11 @@
       "id": "copy-filler-preamble",
       "regex": "\\b(In today's (?:fast-paced|digital)|Built for (?:the )?modern teams?|Welcome to the)\\b",
       "message": "note: AI preamble/filler detected ('In today\\'s fast-paced...', 'Built for modern teams'). Delete the introductory throat-clearing and lead with action."
+    },
+    {
+      "id": "copy-clumsy-indonesian-translations",
+      "regex": "\\b(laci sembul|jendela sembul|garis rambut|panggung asimetris)\\b",
+      "message": "warning: clumsy literal translation detected ('laci sembul', 'garis rambut'). Use natural Indonesian ('panel samping', 'garis tipis', 'area utama')."
     }
   ]
 }

package/.agents/plugins/agentic-senior-core/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "agentic-senior-core",
   "displayName": "Agentic Senior Core",
-  "version": "6.16.5",
+  "version": "6.16.6",
   "description": "Universal AI coding rules and workflows. Write code like a staff engineer.",
   "author": "fatidaprilian",
   "repository": "https://github.com/fatidaprilian/Agentic-Senior-Core"

package/.agents/plugins/agentic-senior-core/rules/agentic-senior-core.md

@@ -46,7 +46,8 @@ When picking step 5 or 6 (unless trivial):
   - 50% reduction rule: Write the statement, then cut unnecessary words. Replace ornamental adjectives with measurable facts (not "a robust, blazing-fast parser", write "parses 50MB/s with zero heap allocations").
   - Ban AI cadences: Never use the Tricolon ("Fast. Simple. Secure."), the Mad-Lib ("The AI-powered platform for modern teams"), the Rebuttal ("Not just a tool, it's a workflow"), or conversational throat-clearing ("In today's fast-paced landscape...").
   - Buzzword blacklist: Never emit `seamless(ly)`, `robust`, `empower(ing)`, `supercharge`, `elevate`, `effortless(ly)`, `cutting-edge`, `delve`, `testament`, `pivotal`, `crucial`, `game-changing`, or `next-generation`.
-  - Strict single-language purity: Choose one language per document or surface. In Indonesian contexts, never prefix grammatical affixes to raw English stems (`di-submit`, `meng-generate`, `di-approve`, `me-restore`).
+  - Strict single-language purity: Choose one language per document or surface. Never mix languages within a single deliverable. Never append parenthetical translation glosses to technical concepts. In localized contexts, translate concepts into the target language's natural, idiomatic engineering terms rather than clumsy literal calques.
+  - Silent internal framework discipline: Never leak ASC internal rule names, checklists, or meta-labels into user-facing plans, UI copy, or code comments. Focus purely on technical and domain facts.
 - Code comment hygiene: Zero decorative character banners (// =====), zero line-by-line narration (// Step 1: validate), zero empty category tags (// Main logic), and zero signature echoes in docstrings. Keep only comments that document non-obvious operational constraints, security boundaries, concurrency hazards, or protocol contracts.
 - Delete code that carries no behavior, safety, or test value. Readability wins over brevity.
 - Detect and respect project linter/formatter configs. Do not restate style rules enforced by tooling.

package/.agents/plugins/agentic-senior-core/skills/asc/references/writing-skills.md

@@ -4,7 +4,7 @@ Engineering guidelines for creating high-performance, token-efficient skills for
 
 ---
 
-## 1. The Discovery & Routing Trap
+## 1. Skill Discovery & Trigger Precision
 
 Research into agent skill selection shows that models degrade in tool and skill routing when descriptions summarize internal workflows.
 

package/.agents/plugins/agentic-senior-core/skills/asc-develop/SKILL.md

@@ -21,7 +21,7 @@ Use when creating a new application, service, or repository from zero.
 2. Propose the top-level directory layout and module boundaries following idiomatic conventions of the chosen stack.
 3. Present an architectural summary and wait for user alignment before writing files.
 
-### Step 2: Implementation & Decision Ladder
+### Step 2: Architecture & Implementation Hierarchy
 1. Apply the ASC Decision Ladder to every module:
    - Does this need to be built?
    - Can standard library or native platform handle it?
@@ -55,7 +55,7 @@ Use when adding endpoints, components, pages, or capabilities to an existing cod
 
 ### Step 3: Implement & Validate (TDD Integration)
 1. Follow the TDD cycle via `/asc-test`: write the failing test first (RED), write minimal code to pass (GREEN), then refactor.
-2. **Zero-Fake-Done Testing**: Run the project test suite (`ascx npm test`, `ascx pytest`, `ascx cargo test`). The test runner **MUST** exit with code 0.
+2. **Empirical Test Execution**: Run the project test suite (`ascx npm test`, `ascx pytest`, `ascx cargo test`). The test runner **MUST** exit with code 0.
 3. Never weaken or delete test assertions to simulate a passing run. Fix the underlying business logic.
 
 ---

package/.agents/plugins/agentic-senior-core/skills/asc-pentest/references/fuzzing-dsl.md

@@ -53,7 +53,7 @@ All dynamic injection tests must use non-destructive canary strings. Never injec
 
 ---
 
-## 3. The Failure Oracle (Crash & Error Triage)
+## 3. Crash Detection & Error Triage
 
 When fuzzing an endpoint, every server response is categorized against three automated oracles:
 

package/.agents/plugins/agentic-senior-core/skills/asc-test/SKILL.md

@@ -10,9 +10,9 @@ Staff-grade testing playbook and verification gates. Enforces test-first discipl
 
 ---
 
-## 1. The Iron Law of TDD
+## 1. Test-Driven Development Protocol
 
-> **THE IRON LAW:** No production code shall be written without a failing test first.
+> **CORE PROTOCOL:** No production code shall be written without a failing test first.
 
 Every feature, bugfix, or refactor must follow the Red-Green-Refactor sequence:
 1. **RED:** Write a minimal failing test. Execute it and confirm it fails for the expected reason.

package/.agents/plugins/agentic-senior-core/skills/asc-test/references/regression-proof.md

@@ -36,7 +36,7 @@ Never fix a bug by immediately editing production code. Follow this deterministi
 - Edit production code to eliminate the bug.
 - Run the reproduction test fresh: it must pass with exit code 0.
 
-### Step 3: The Regression Proof Gate (Revert & Confirm)
+### Step 3: Regression Verification (Revert & Confirm)
 To prove that the test actually guards against the bug:
 1. Temporarily comment out or revert the fix in production code.
 2. Run the test fresh: **The test must fail.**
@@ -45,7 +45,7 @@ To prove that the test actually guards against the bug:
 
 ---
 
-## 2. Claim Verification Gate
+## 2. Claim Verification Standards
 
 Every claim regarding test results or bug fixes requires concrete execution evidence:
 

package/.agents/plugins/agentic-senior-core/skills/asc-test/references/tdd-cycle.md

@@ -1,8 +1,8 @@
 # Test-Driven Development (TDD) Cycle
 
-TDD is an architectural discipline for writing deterministic, verifiable software. The Iron Law of TDD governs all development:
+TDD is an architectural discipline for writing deterministic, verifiable software. The core principle governs all development:
 
-> **THE IRON LAW:** No production code shall be written without a failing test first.
+> **Core Principle:** No production code shall be written without a failing test first.
 
 ---
 

package/.agents/plugins/agentic-senior-core/skills/asc-test/references/uat.md

@@ -42,7 +42,7 @@ Verification records, testing matrices, and UAT notes belong in the agent conver
 
 ---
 
-## 4. The Edge Case Quad
+## 4. Boundary & Edge Case Categories
 
 Never sign off on acceptance testing by verifying only the primary happy path. Every scenario must be verified against four operational vectors:
 

package/.agents/plugins/agentic-senior-core/skills/asc-ui/SKILL.md

@@ -27,7 +27,7 @@ Every UI edit must satisfy these 15 rules without exception:
 11. **Mobile containment:** Set `overflow-x: clip` on root shells. Never leak horizontal scrolling.
 12. **Touch targets:** Minimum 44×44px hit target with $\ge$ 8px clearance for all interactive touch controls.
 13. **Contrast floor:** Meet WCAG 2.2 AA (4.5:1 normal text, 3:1 large text and UI component boundaries).
-14. **Single-language purity:** Never mix languages on one surface; ban hybrid neologisms (`di-submit`, `meng-generate`).
+14. **Single-language purity:** Never mix languages on one surface; preserve monolingual consistency across headings, labels, errors, and actions.
 15. **Icon semantics:** Never use raw unicode or emojis as icons. Use dedicated SVG icons; mark decorative icons `aria-hidden="true"`.
 16. **Substance over restraint:** Stripping slop is only half the job. Replace removed ornaments with real substance: strong typographic scale contrast, full-field color anchors, and authentic interface fragments. Never leave an empty, sterile wireframe void.
 17. **Product over skill (No geek cosplay):** The real-world domain dictates aesthetics. Never inject terminal windows, ASCII art, or pseudo-telemetry consoles into civic, educational, or commercial products (`references/modes/genre-calibration.md`).
@@ -40,26 +40,17 @@ Every UI edit must satisfy these 15 rules without exception:
 
 Before declaring markup, drafting redesign plans, or inspecting user code:
 
-1. **Locate Skill Directory & References (MANDATORY):**
-   Reference files do NOT reside in the user workspace root. They are located adjacent to this `SKILL.md` file:
-   `<skill_directory>/references/<category>/<file>.md`
-   Identify the path of this `SKILL.md` file (provided by host/tooling) and resolve all reference paths relative to it.
-
-2. **Step 1 — Two-Phase Enforcement Gate (MANDATORY GATE):**
-   - **Phase A (Structure & Hierarchy First):** Lock project domain genre (Civic, Enterprise, SaaS, DevTools) and read `references/modes/genre-calibration.md` + target mode reference (`references/modes/<mode>.md`). Lock the primary focal anchor and spatial posture before writing code.
-   - **Phase B (Visual System & Themes):** Read `references/craft/themes-catalog.md` and lock one of the 16 curated themes across 8 real-world domains (e.g., Sovereign Slate, Almanac Index, Editorial Ledger, Pharmacy Calm, Ink & Signal, Graphite Instrument) to prevent probabilistic palette slop.
-   *Do NOT proceed until you have read the genre, mode, and theme references into context.*
-
-3. **Step 2 — Secondary Craft Ingestion:**
-   Execute `read_file` on at least one relevant craft reference for your task from Section 5 (e.g. `references/craft/typography.md`, `references/craft/color-surfaces.md`, or `references/divergence.md`).
-
-4. **Step 3 — Workspace Material Inventory:**
-   Only AFTER loading the mode reference, inspect the workspace:
-   - **Design Tokens:** Read project CSS variables, Tailwind configuration, or existing components in `components/` or `ui/`. If `DESIGN.md` exists, read it (read-only). Never create or edit persistent checkpoint files.
-   - **Take Material Inventory:**
-     - **Real:** Concrete numbers, existing endpoints, actual data attributes.
-     - **Pictures:** Actual screenshots and product visual assets.
-     - **Absent:** Missing quotes, missing logos, or unverified metrics—these are omitted entirely.
+1. **Step 1 — Workspace Brand Audit (Brownfield vs Greenfield):**
+   - Check project styling configuration: `app.css`, `globals.css`, `tailwind.config.*`, or `components/ui`.
+   - **Brownfield Rule:** If the project already defines brand tokens (e.g. custom brand colors, established fonts, existing UI library), **DO NOT OVERRIDE THEM**. Calibrate neutrals to the brand's color temperature (single neutral family law) and respect established naming.
+   - **Greenfield Fallback:** If the repository is brand new with zero tokens, read `references/modes/genre-calibration.md` and select a starting palette from `references/craft/themes-catalog.md`.
+2. **Step 2 — Silent Discipline & Real Visual Benchmarks:**
+   - Review `references/craft/composition-patterns.md` and inspect matching `references/visuals/real-*.png` / `*-dom.json` for authentic human-designed spacing and layout hierarchies rather than enclosing sections in repetitive `1px` boxes.
+   - **Silent Meta-Rules:** Never emit internal framework rules, theme catalog names, or parenthetical foreign translations in user deliverables. Focus purely on technical facts.
+3. **Step 3 — Workspace Material Inventory:**
+   - **Real:** Concrete numbers, existing endpoints, actual data attributes from controllers/models.
+   - **Pictures:** Actual screenshots and product visual assets.
+   - **Absent:** Missing quotes, missing logos, or unverified metrics—these are omitted entirely.
 
 ---
 
@@ -91,17 +82,19 @@ Never split the difference into cosmetic polish on a discarded look:
 | Target Domain / Task Requirement | Mandatory Reference Path |
 |---|---|
 | Domain & genre calibration (Anti-geek cosplay) | `references/modes/genre-calibration.md` |
-| Curated material themes & locked art direction | `references/craft/themes-catalog.md` |
+| Concrete structural layouts & anti-1px cage | `references/craft/composition-patterns.md` |
+| Real-world visual benchmarks & rendered DOMs | `references/visuals/` (13 live domains) |
+| Curated material themes (Greenfield reference) | `references/craft/themes-catalog.md` |
 | Waivable defaults & waiver syntax | `references/reflexes.md` |
 | Typography, line-height & tabular numbers | `references/craft/typography.md` |
-| Color tokens, 60-30-10 & elevation | `references/craft/color-surfaces.md` |
+| Color tokens, single neutral family & elevation | `references/craft/color-surfaces.md` |
 | Micro-interactions & GPU motion | `references/craft/motion.md` |
 | Native surfaces (selection, caret, scrollbars) | `references/craft/browser-surfaces.md` |
-| 50% reduction, active verbs & i18n | `references/copy-i18n.md` |
+| 50% reduction, active verbs & natural i18n | `references/copy-i18n.md` |
 | Responsive reflow, dvh & touch targets | `references/mobile-responsive.md` |
 | WCAG 2.2 AA contrast & keyboard operability | `references/accessibility.md` |
-| The Data State Quad & mutation feedback | `references/states-feedback.md` |
-| Anti-convergence, 4 Waves of Tells & Mirror Test | `references/divergence.md` |
+| The Data State System & mutation feedback | `references/states-feedback.md` |
+| Anti-convergence & layout diversity | `references/divergence.md` |
 | Structured UI audit matrix | `references/redesign-audit.md` |
 
 ---
@@ -109,9 +102,10 @@ Never split the difference into cosmetic polish on a discarded look:
 ## 6. Verification & Handoff Sweep
 
 Before completing any UI task, run this mechanical check:
-1. **Reference Compliance:** Confirm constraints from `references/modes/genre-calibration.md`, `references/craft/themes-catalog.md`, and target mode were strictly applied.
+1. **Brand & Reference Compliance:** Confirm project tokens were respected (or greenfield constraints followed). Verify zero clumsy literal translations or meta-jargon leaks.
 2. **Finish Gate Sweep:** Verify zero text clipping (+30% expansion buffer), zero awkward text wraps, and 4px/8px spacing grid consistency.
-3. **State Quad:** Loading skeleton, empty state, error with retry, and populated data are all handled.
-4. **Pending Feedback:** Buttons disable and display feedback during ongoing mutations.
-5. **Contrast & Focus:** Verify keyboard tab flow and high-contrast `:focus-visible` styling.
-6. **Lint Check:** Verify changes against `hooks/lib/known-ui-slop-patterns.json`.
+3. **Visual Verification (`asc preview`):** If a local dev server is running or an HTML prototype exists, run `asc preview <url|file> [--mobile]` to inspect the rendered visual balance before handoff.
+4. **Data States:** Loading skeleton, empty state, error with retry, and populated data are all handled.
+5. **Pending Feedback:** Buttons disable and display feedback during ongoing mutations.
+6. **Contrast & Focus:** Verify keyboard tab flow and high-contrast `:focus-visible` styling.
+7. **Lint Check:** Verify changes against `hooks/lib/known-ui-slop-patterns.json`.

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/accessibility.md

@@ -4,7 +4,7 @@ Accessibility is not an afterthought or an optional overlay. It is the structura
 
 ---
 
-## 1. Contrast Ratios & The Grey-on-Grey Trap
+## 1. Contrast Ratios & WCAG Compliance
 
 All text and critical visual indicators must meet WCAG 2.2 Level AA mathematical contrast floors.
 
@@ -13,7 +13,7 @@ All text and critical visual indicators must meet WCAG 2.2 Level AA mathematical
 - **Large Text ($\ge$ 18pt / 24px regular, $\ge$ 14pt bold):** Minimum `3:1` contrast ratio.
 - **UI Components & Graphical Boundaries:** Active input borders, toggle switches, and focus indicators require minimum `3:1` against adjacent background colors.
 
-### 1.2 The Dark Mode Grey-on-Grey Trap
+### 1.2 Avoiding Low-Contrast Surfaces
 A frequent aesthetic failure is using low-contrast grey text for "subtle elegance":
 - **Failing example:** `text-zinc-500` (`#71717a`) on `bg-zinc-900` (`#18181b`) = **3.8:1** (Fails 4.5:1 AA for body copy).
 - **Compliant fix:** `text-zinc-400` (`#a1a1aa`) on `bg-zinc-900` = **6.2:1** (Passes AA).

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/copy-i18n.md

@@ -89,19 +89,35 @@ An operational error message must never produce a dead end or display raw intern
 
 ---
 
-## 6. Single-Language Purity & Anti-Gado-Gado
+## 6. Single-Language Consistency & Localization
 
-Interfaces must maintain strict language purity. Mixing two languages within the same surface causes cognitive friction and feels unpolished.
+Interfaces and developer communications must maintain strict language purity without robotic or literal translation awkwardness.
 
 ### 6.1 Strict Monolingual Surface
 Choose one language for the entire surface and enforce it across headings, labels, errors, and tooltips:
 - **English UI:** All copy, actions, and timestamps in English.
-- **Indonesian UI:** All copy, actions, and timestamps in standard Indonesian (KBBI/PUEBI).
-
-### 6.2 Ban Hybrid Neologisms (Indonesian Context)
-Never prefix Indonesian grammatical affixes (`di-`, `meng-`, `ter-`, `pe-`) onto raw English stems:
-
-| Hybrid Neologism (Banned) | Standard Indonesian | Pure English Alternative |
+- **Indonesian UI:** All copy, actions, and timestamps in natural, standard Indonesian (KBBI/PUEBI).
+
+### 6.2 Codebase Lexicon Supremacy (Anti-Hallucinated Naming)
+Before naming navigation menus, section titles, table columns, or actions in an existing codebase, inspect the project's models, controllers, and view variables:
+- **Respect established domain terms:** Always adopt the exact nouns established in the repository's models, routes, and translations. Never substitute recognized project nouns with unprompted external synonyms.
+- Use the actual terminology the organization and developers already use in their schema and UI.
+
+### 6.3 Ban Robot Translations & Meta-Jargon Parens
+In localized interface and review text:
+1. **No clumsy literal translations of English layout terms:**
+   - Do NOT translate *drawer* into awkward calques; write natural native labels (e.g. "panel samping" or "detail").
+   - Do NOT translate *modal* literally; write natural functional terms (e.g. "dialog" or "popup").
+   - Do NOT translate *hairline border* as literal anatomy; write "garis tipis 1px" or "garis pemisah".
+   - Do NOT translate layout stages into literal theatrical terms; write "layout dua kolom" or "area utama".
+2. **No parenthetical English jargon leaks:**
+   - Never write sentences that append raw English terms in parentheses as translation glosses.
+   - Write clear, natural localized prose without meta-framework disclaimers.
+
+### 6.4 Ban Hybrid Neologisms
+Never prefix local grammatical affixes onto foreign language stems:
+
+| Hybrid Neologism (Banned) | Standard Native Alternative | Pure English Alternative |
 |---|---|---|
 | `di-submit` | `Dikirim` / `Diserahkan` | `Submitted` |
 | `meng-generate` | `Menghasilkan` / `Membuat` | `Generating` |

package/.agents/plugins/agentic-senior-core/skills/asc-ui/references/craft/color-surfaces.md

@@ -13,6 +13,13 @@ Grounded in: Apple HIG, Google Material Design 3, and Refactoring UI Color Strat
     - Borders: `border-border`, `border-input`, `border-primary`.
   - **Zero Raw Hex Literals in Markup:** Never write inline hex values (`#6366f1`, `#3b82f6`) or arbitrary utility classes (`bg-blue-600`) outside the root token definition.
 
+- **The Single Neutral Family Law (Anti-Muddy Surfaces):**
+  - Never mix cool-tinted grays (e.g. Tailwind `slate-*`, with blue undertones) and warm-tinted grays (e.g. `stone-*`, with yellow/brown undertones) on the same screen. Combining `slate-900` text with `stone-50` backgrounds creates a dirty, mismatched optical surface.
+  - Choose one neutral temperature matching the project's primary brand:
+    - Warm brands (warm green, brown, amber, terracotta) $\to$ pair strictly with `stone` or neutral warm tones.
+    - Cool brands (navy, cobalt, cyan, indigo) $\to$ pair strictly with `slate` or cool zinc.
+    - Pure monochromatic / minimal brands $\to$ pair with neutral `zinc` or `gray`.
+
 ---
 
 ## 2. The 60-30-10 Distribution Rule
@@ -49,13 +56,13 @@ Grounded in: Apple HIG, Google Material Design 3, and Refactoring UI Color Strat
 
 ---
 
-## 4. Integrated Scorecards & Metric Blocks (Anti-Sticker Invariant)
+## 4. Metric Displays & Scorecards
 
-- **Ban The Sticker Box:** Never place an isolated white box with a thin border floating inside an already white or light header canvas. This creates an optical "detached sticker" artifact.
+- **Integrated Layout:** Never place an isolated white box with a thin border floating inside an already white or light header canvas.
 - **Anchor Into Layout Chrome:**
   - Integrate scorecards directly into the identity header rail or stage banner using a unified divider (`border-l border-border/80 pl-6`) or structural inset well (`bg-muted/40`).
 - **Semantic Tinting for Evaluation Scores:**
-  - When communicating aggregate grades (e.g. `84,20 / 100`, Predikat B):
+  - When communicating aggregate grades (e.g. `84.20 / 100`, Rank B):
     - Background: subtle semantic tint (`bg-emerald-500/10` or `bg-slate-500/10`).
     - Border: matching tinted hairline (`border border-emerald-500/20`).
     - Typography: tabular numbers (`font-mono tabular-nums`) with clear contrast ($Display \ge 3.5\times Body$).
@@ -63,10 +70,10 @@ Grounded in: Apple HIG, Google Material Design 3, and Refactoring UI Color Strat
 
 ---
 
-## 5. Contextual Inline Alerts & Callouts (The Callout Invariant)
+## 5. Inline Notifications & Status Banners
 
-- **Never Float Warning Text Adrift:** Warning notes, disclaimers, or temporary state alerts must NEVER be dumped as raw floating text between layout sections.
-- **The Callout Invariant:** Every alert must reside in a structured callout container:
+- **Structured Containers:** Warning notes, disclaimers, or temporary state alerts must reside in clear semantic containers, never dumped as raw floating text between layout sections.
+- **Notification Requirements:** Every alert must reside in a structured callout container:
   - Container: 1px hairline border with matching light background tint (e.g. `border border-amber-500/30 bg-amber-500/10 rounded-md p-3`).
   - Icon Anchor: Dedicated semantic SVG icon (alert circle, triangle) aligned with first line of text.
   - Placement: Positioned immediately above or inside the data table/form it modifies, establishing unmistakable contextual binding.