agent-enderun 1.1.5 → 1.1.7

package/templates/architecture/standards/mobile-standards.md

@@ -1,48 +0,0 @@
-# Mobile Standards — Agent Enderun (React Native & Expo)
-
-This document establishes the responsive styling, safe layout, and development standards for mobile applications.
-
-## 📱 1. Safe Layout & Notches
-
-- **SafeAreaView Usage:** All screen entry points must be wrapped in a `SafeAreaView` (from `react-native-safe-area-context`) to avoid overlap with device notches, status bars, and home indicators.
-- **Avoid Hardcoded Padding/Margins:** Use the dynamic insets returned by the `useSafeAreaInsets()` hook for custom spacing.
-
-## 📏 2. Fluid & Responsive Dimensions
-
-- **No Hardcoded Absolute Sizes:** Hardcoding absolute widths and heights (e.g. `width: 375`) is strictly forbidden. 
-- **Flexbox First:** Build layouts using Flexbox (`flex: 1`, `flexDirection`, `justifyContent`, `alignItems`).
-- **Dynamic Scales:** Use percentages (`width: "100%"`) or calculate dynamic values using `useWindowDimensions()` or a scaling utility:
-  ```typescript
-  import { Dimensions } from "react-native";
-  const { width, height } = Dimensions.get("window");
-  
-  // Base design width (e.g., iPhone 14 / 390px wide)
-  const scale = width / 390;
-  export const normalize = (size: number) => Math.round(size * scale);
-  ```
-
-## 🎨 3. Typography & Styling
-
-- **System Fonts:** Use native platform fonts or custom configured Expo fonts consistently.
-- **Fluid Typography:** Scale font sizes dynamically using scaling utilities so they look proportionate on both compact screens and tablets.
-- **Platform Selection:** Target Android and iOS specifically when styling differs (e.g., shadows vs elevation) using `Platform.select()`:
-  ```typescript
-  const cardStyle = {
-    ...Platform.select({
-      ios: {
-        shadowColor: "#000",
-        shadowOffset: { width: 0, height: 2 },
-        shadowOpacity: 0.1,
-        shadowRadius: 4,
-      },
-      android: {
-        elevation: 4,
-      },
-    }),
-  };
-  ```
-
-## 📦 4. Asset & Network Optimization
-
-- **Vector Graphics:** Prefer SVG files over high-resolution PNG/JPG files for icons and illustrations to prevent scaling pixelation.
-- **Image Performance:** Always use caching and optimizing components like Expo's `Image` with appropriate content-fit modes.

package/templates/architecture/standards/tech-stack.md

@@ -1,9 +0,0 @@
-# Tech Stack — Agent Enderun (Enterprise)
-
-- **Execution Profile:** Full (Enterprise)
-- **Frontend:** React (Vite), Panda CSS (Zero UI Library)
-- **Backend:** Fastify API, Kysely (Query Builder)
-- **Database:** PostgreSQL
-- **Testing:** Vitest (Integration + Unit)
-- **Auth:** Contract-first (Type definitions)
-- **Versioning:** API-path versioning (/api/v1/...)

package/templates/backend/error-handling.md

@@ -1,74 +0,0 @@
-# Professional Domain Error Handling Pattern (v0.8.5)
-
-All backend components developed under the Agent Enderun framework must comply with the **Domain Error Handling Protocol**. Direct usage of generic Javascript `Error` objects or HTTP status codes inside domain services is strictly forbidden.
-
----
-
-## 🏛️ 1. DomainError Base Hierarchy
-
-We implement a strongly-typed, business-aware exception hierarchy. Every error thrown by the domain logic must inherit from the `DomainError` class.
-
-```typescript
-export abstract class DomainError extends Error {
-  public abstract readonly statusCode: number;
-  public abstract readonly errorCode: string;
-  public readonly timestamp: string;
-
-  constructor(message: string, public readonly metadata: Record<string, unknown> = {}) {
-    super(message);
-    Object.setPrototypeOf(this, new.target.prototype);
-    this.name = this.constructor.name;
-    this.timestamp = new Date().toISOString();
-  }
-}
-```
-
-### Core Exception Catalog
-
-*   **`NotFoundError` (HTTP 404):** Thrown when a resource (e.g., `User`, `Project`) identified by a **Branded Type ID** does not exist.
-*   **`ValidationError` (HTTP 400):** Thrown when data validation (usually Zod schemas) fails before processing business logic.
-*   **`ConflictError` (HTTP 409):** Thrown when database unique constraints or concurrent updates conflict.
-*   **`UnauthorizedError` (HTTP 401 / 403):** Thrown when RLS (Row Level Security) or RBAC policies are violated.
-
----
-
-## ⚡ 2. Fastify Global Exception Handler
-
-Fastify must be configured with a single central error handler to map `DomainError` to client responses safely, preventing internal stack traces from leaking to the outside world.
-
-```typescript
-import { FastifyInstance, FastifyReply, FastifyRequest } from "fastify";
-
-export function registerGlobalErrorHandler(server: FastifyInstance) {
-  server.setErrorHandler((error: Error, request: FastifyRequest, reply: FastifyReply) => {
-    if (error instanceof DomainError) {
-      server.log.warn({ err: error }, `Domain error: ${error.message}`);
-      return reply.status(error.statusCode).send({
-        success: false,
-        error: error.errorCode,
-        message: error.message,
-        timestamp: error.timestamp,
-        metadata: error.metadata
-      });
-    }
-
-    // Capture unhandled internal technical crashes
-    server.log.error({ err: error }, `Unhandled server crash: ${error.message}`);
-    return reply.status(500).send({
-      success: false,
-      error: "INTERNAL_SERVER_ERROR",
-      message: "An unexpected error occurred inside the system."
-    });
-  });
-}
-```
-
----
-
-## 🔒 3. Branded Types & Query Constraints
-
-1.  **Branded Type Enforcement:** You must never accept raw string IDs inside repository query parameters. Always enforce compile-time type safety:
-    ```typescript
-    export type UserId = string & { readonly __brand: unique symbol };
-    ```
-2.  **Kysely Query Failures:** All Kysely queries running inside database transactions must be wrapped inside a `try/catch` block that translates SQL constraints into precise `ConflictError` or `UnauthorizedError` entities instead of throwing raw database query failures.

package/templates/frontend/component-patterns.md

@@ -1,91 +0,0 @@
-# Atomic Component Standards & Panda CSS Guidelines (v0.8.5)
-
-All user interface developments inside the Agent Enderun framework must follow the **Fluid Component Protocol**. We strictly build component hierarchies following **Mobile-First Responsive Design** and type-safe styling using **Panda CSS**.
-
----
-
-## 🚫 1. Absolute UI Policies
-
-### A. Zero UI Library Policy
-*   **The Law:** The use of external component libraries (e.g. TailwindCSS, Radix UI, Shadcn/ui, Material UI, Chakra UI, Ant Design) is strictly forbidden. 
-*   **The Reason:** This ensures absolute design authenticity, maximum bundle optimization, zero dependency bloat, and fully controlled accessibility (WCAG 2.2 AA).
-*   **Exception:** Low-level headless primitives (like `@radix-ui/react-dialog` for focus trapping or `sonner` for toast dispatchers) may be allowed, subject to direct approval by `@manager`.
-
-### B. Shared Component First Policy
-*   **The Law:** Defining reusable atomic components (Buttons, Inputs, Cards, Badges, Modals) inside page-level files is strictly forbidden.
-*   **The Structure:** All atomic items must be created inside `apps/web/src/components/ui/` as focused, single-purpose, highly modular components.
-
----
-
-## 🐼 2. Panda CSS Styling Standards
-
-We utilize **Panda CSS** as our build-time type-safe CSS-in-JS engine. Raw inline styles or unmapped class names are completely banned.
-
-### A. Styling Token Best Practices
-Always leverage designated design tokens (colors, spacings, shadows) from the Panda config (`panda.config.ts`):
-
-```tsx
-import { css } from "../../styled-system/css";
-
-interface ButtonProps extends React.ButtonHTMLAttributes<HTMLButtonElement> {
-  variant?: "primary" | "secondary";
-}
-
-export function Button({ variant = "primary", className, children, ...props }: ButtonProps) {
-  return (
-    <button
-      className={css(
-        {
-          display: "inline-flex",
-          alignItems: "center",
-          justifyContent: "center",
-          px: "4",
-          py: "2.5",
-          borderRadius: "md",
-          fontSize: "sm",
-          fontWeight: "medium",
-          transition: "all 0.2s ease-in-out",
-          cursor: "pointer",
-          _disabled: { opacity: 0.5, cursor: "not-allowed" },
-        },
-        variant === "primary"
-          ? {
-              bg: "brand.primary",
-              color: "white",
-              _hover: { bg: "brand.primary.hover" },
-            }
-          : {
-              bg: "transparent",
-              color: "slate.700",
-              border: "1px solid",
-              borderColor: "slate.200",
-              _hover: { bg: "slate.50" },
-            }
-      )}
-      {...props}
-    >
-      {children}
-    </button>
-  );
-}
-```
-
-### B. Mobile-First Fluid Responsiveness
-Use array-based or object-based responsive syntax inside the `css` block. Never hardcode pixel values:
-
-```typescript
-// Enforce fluid flex layout across screen sizes
-const containerStyle = css({
-  display: "flex",
-  flexDirection: { base: "column", md: "row" }, // Mobile-first (column -> row on desktop)
-  gap: { base: "4", lg: "8" },
-  p: { base: "4", md: "6", xl: "8" }
-});
-```
-
----
-
-## ♿ 3. Accessibility & QA Gates (WCAG 2.2)
-
-1.  **Aria Standards:** All custom interactive elements (dropdowns, mobile navigation draw-ins, accordion blocks) must support full keyboard navigation (Tab, Enter, Space) and have valid `aria-*` tags.
-2.  **Vitest Verification:** A component must never be merged into master without an accompanying test file (`[component].test.tsx`) that verifies the component renders correctly and responds to user click actions.