azcodr 1.3.0 → 1.5.0

package/docs/rules/test_isolation.md

@@ -1,26 +0,0 @@
-# Test Coverage, Isolation & Determinism
-
-> **Core Mandate:** Enforce 100.00% test coverage thresholds, transactional database rollback per test, deterministic data factories, and zero-sleep flakiness elimination across all test suites.
-
----
-
-## 1. Mandatory 100.00% Test Coverage Thresholds
-
-- **Strict Coverage Thresholds**: Maintain line, function, branch, and statement test coverage at **100.00%** across all backend domain logic, adapters, contracts, and frontend suites. Strictly enforce 100% threshold failure gates in CI pipelines.
-- **Exhaustive Status Codes & Error Branches**: Explicitly test all HTTP/gRPC response codes:
-  - Success: `200 OK`, `201 Created`, `204 No Content`
-  - Client Errors: `400 Bad Request`, `401 Unauthorized`, `403 Forbidden`, `404 Not Found`, `409 Conflict`, `422 Unprocessable Entity`, `429 Too Many Requests`
-  - Server Failures: `500 Internal Server Error`, `503 Service Unavailable`
-- **UI Interaction States & Edge Cases**: Fully assert all presentation states (loading spinners, disabled controls, error banners, success feedback, empty states) across suites.
-
----
-
-## 2. Database Test Isolation & Zero Flakiness
-
-- **Transactional Rollback per Integration Test**:
-  - Every integration test that interacts with persistence must execute within a scoped transaction that is rolled back upon test completion (`afterEach` rollback) or use ephemeral, disposable database isolates. Never leave mutated rows that pollute subsequent tests.
-- **Deterministic Test Data Factories**:
-  - Utilize strongly-typed test data factories (`buildUser()`, `buildOrder()`) with randomized unique identifiers rather than hardcoded magic strings or fixed database IDs.
-- **Zero Sleep / Flakiness Elimination**:
-  - Strictly forbid arbitrary `sleep()` or timeout pauses in tests.
-  - Rely exclusively on deterministic condition polling (`waitFor(condition)`) or reactive event promises to eliminate test flakiness.

package/docs/rules/typescript.md

@@ -1,55 +0,0 @@
-# Static Type Safety & Sound Type Systems
-
-> **Core Mandate:** Enforce maximum compiler strictness, branded nominal typing for domain identifiers, strict prohibition of untyped escape hatches, and automated pre-commit quality guardrails across polyglot implementations.
-
----
-
-## 1. Maximum Compiler Strictness & Soundness
-
-Regardless of the execution language chosen for an adapter or service, enforce maximum compiler rigor to eliminate runtime null pointer exceptions, unhandled type cases, and memory errors at compile time:
-
-- **TypeScript**: Enable all strict compiler flags (`strict: true`, `noImplicitAny: true`, `strictNullChecks: true`, `noUncheckedIndexedAccess: true`).
-- **Rust**: Enable `#![deny(clippy::all)]` and `#![deny(missing_docs)]` with zero `unsafe` blocks.
-- **Go**: Enable comprehensive static analysis (`golangci-lint` with `errcheck`, `govet`, `staticcheck`).
-- **Python**: Enforce strict type checking (`mypy --strict` or `pyright`).
-
----
-
-## 2. Branded Nominal Typing & Primitive Obsession Elimination
-
-Prevent accidental mixing of raw primitive identifiers (e.g. passing an arbitrary `string` representing a `TenantId` where a `UserId` is expected) by enforcing nominal types:
-
-```
-┌────────────────────────────────────────────────────────┐
-│ Nominal Domain Identifier Pattern (Polyglot)           │
-├────────────────────────────────────────────────────────┤
-│ Rust:       struct TenantId(String);                   │
-│             struct UserId(String);                     │
-│ Go:         type TenantId string                       │
-│             type UserId string                         │
-│ TypeScript: type TenantId = Brand<string, 'TenantId'>; │
-│             type UserId = Brand<string, 'UserId'>;     │
-│ Python:     TenantId = NewType('TenantId', str)        │
-│             UserId = NewType('UserId', str)            │
-└────────────────────────────────────────────────────────┘
-```
-
-Domain functions must accept and return branded types rather than raw primitive strings or integers.
-
----
-
-## 3. Strict Prohibition of Untyped Escape Hatches
-
-- **Zero Tolerance for Unsound Types**: Strictly prohibit `any` in TypeScript, raw `interface{}` / `any` without type assertion checks in Go, raw `Any` in Python, or unchecked casts in Java/Rust.
-- **Runtime Validation at Boundaries**: External payloads (network requests, message queues, disk files) must be parsed and narrowed into strongly-typed domain structures before passing to application services.
-- **Commit Guardrails**: Enforce Conventional Commits via commit linters. Never bypass pre-commit hooks running static type checking, formatting, and linters.
-
----
-
-## 4. Module Path Aliases & Relative Traversal Elimination
-
-- **Path Alias Mandate (`@/*`)**: All TypeScript packages in the workspace must configure and standardize on `@/*` mapped to `./src/*` across `tsconfig.json` (`"baseUrl": "."`, `"paths": { "@/*": ["./src/*"] }`), bundlers (Vite `resolve.alias`), and test runners (Vitest `resolve.alias`).
-- **Strict Prohibition of Deep Relative Traversal**: Never use deep relative traversals (`../../../..`, `../../..`, `../..`) across layers or contexts. Deep relative paths create fragile coupling, impair refactoring, and obscure domain layer boundaries.
-- **Node.js ESM Production Resolution**: In backend environments executing compiled JavaScript under Node.js ESM (`node dist/index.js`), use `tsc-alias` post-compilation (`tsc && tsc-alias`) to resolve path aliases in `dist/` to valid relative paths without introducing runtime loader overhead.
-- **Scope of Sibling Imports**: Local relative imports (`./file.js`) are permitted only for immediate siblings within the identical directory. Any import traversing up a directory hierarchy or crossing architectural boundaries (domain, ports, adapters, components, context) MUST resolve via `@/*`.
-

package/docs/rules/ui_navigation.md

@@ -1,20 +0,0 @@
-# UI Navigation & URL State Synchronization
-
-> **Core Mandate:** Enforce bidirectional URL state synchronization for all interactive view states, preserving deep linkability, bookmarkability, and native browser navigation.
-
----
-
-## 1. Bidirectional URL State Synchronization
-
-Every view state that represents navigation, active tab, filtering, sorting, pagination, or search query must synchronize bidirectionally with URL search parameters (`useSearchParams`):
-- **Bookmarkability**: A user copying the browser URL must be able to restore the exact view, active tab, filter selections, and pagination page on any device.
-- **Browser History Integration**: The browser's back and forward buttons must navigate between state transitions smoothly without triggering full page reloads.
-
----
-
-## 2. Deep Linking Standards
-
-- **Tabbed Interfaces**: Encode active tab keys in query params (e.g. `?tab=security` or `/settings/security`).
-- **Data Tables & Lists**: Preserve table states in URL parameters:
-  - `?page=2&limit=25&sort=createdAt&order=desc&status=ACTIVE`
-- **Modal & Drawer States**: If a modal or drawer represents an actionable sub-view (e.g. `?modal=edit-user&userId=123`), synchronize it with the URL so direct links open the intended context.

package/docs/rules/workspace_isolation.md

@@ -1,25 +0,0 @@
-# Workspace Isolation & Zero Global Context Interference
-
-> **Core Mandate:** Enforce strict workspace containment within the workspace root (`./`), strictly prohibiting any leakage, interference, or unverified assumptions from global configurations, external directories, or sibling projects.
-
----
-
-## 1. Principle of Workspace Sovereignty
-
-- **Ground Truth Boundary**: Only files, dependencies, configuration files (`package.json`, `tsconfig.json`, `docker-compose.yml`), and verified command executions within the local workspace (`./`) constitute project truth.
-- **Zero Global Contamination**: Never import, execute, or assume tools, environment variables, or conventions from global system directories (e.g. `~/.config`, `/tmp`, `~/.gemini/antigravity-cli`, or parent directories) unless explicitly defined within local workspace configuration.
-- **Sibling Project Isolation**: Strictly ignore all external or legacy projects. Do not read from or write to directories outside the local repository (`./`).
-
----
-
-## 2. Dependency & Tooling Isolation
-
-- **Local Package Manager**: Standardize strictly on local workspace dependencies managed via `npm` within this workspace. Never rely on global npm packages (`npm install -g`).
-- **Container Network Containment**: All Docker containers and bridge networks must be named and scoped specifically to this project (e.g. `azcodr_network`, `azcodr_postgres`) to prevent port collisions or cross-project data leakage.
-
----
-
-## 3. Subagent & Execution Context Sandboxing
-
-- When spawning subagents or executing commands, ensure the working directory (`Cwd`) is anchored strictly to the workspace root (`./`).
-- Subagents must never carry over assumptions from other workspaces or global memory pools.