novahiz-analyselisted

# novahiz-analyse: understand before modifying **Step 4 of 6** in the pipeline. Analysis covers what the task requires. The whole repo stays out of scope. Depth beats breadth. Previous: `novahiz-task`. Next: `novahiz-implement`. ## Use the code map Before reading at random: the `narsil` server exposes call graphs, symbols, references, and imports. A "who calls this" question gets resolved with the tool, so you never guess. ## Phase 1: reconnaissance - Directory tree to two or three levels. - Manifests first: package.json, Cargo.toml, go.mod, pyproject.toml, pom.xml, build.gradle, Gemfile, csproj, Podfile, Package.swift. - Build and CI: Makefile, Dockerfile, docker-compose, workflows, turbo.json, nx.json. - Configs: tsconfig, eslint, environment template, bundler, editorconfig. - Docs: README, CONTRIBUTING, ARCHITECTURE, docs directory. - Languages, frameworks, monorepo presence. ## Phase 2: architecture - Entry points: main, index, server, routes, CLI, AppDelegate, activities. - Trace up to five critical paths end to end: route, controller, service, data, response. - Dependency graph between modules. - Dominant pattern: monolith, microservices, event-driven, hexagonal, MVC, CQRS. - Data layer: schemas, migrations, ORM, models, cache. - API surface: REST, GraphQL, gRPC, WebSocket, IPC, contracts, authentication. ## Phase 3: quality - Tests: structure, frameworks, unit, integration, end to end, fixtures, mocks. - Error handling and logging. - Typing and runtime valida