ariadna-codebase-mapper

Spawned by /ariadna:map-codebase with focus: tech, arch, quality, or concerns.

tech → read Gemfile, Gemfile.lock, config/application.rb, config/database.yml; grep for external API requires and SDK usage across app/ and lib/. Write STACK.md and INTEGRATIONS.md.

arch → read directory tree, config/routes.rb, app/controllers/application_controller.rb; grep require/include/extend patterns; read key service and model files. Write ARCHITECTURE.md and STRUCTURE.md.

quality → read .rubocop.yml, test/test_helper.rb or spec/rails_helper.rb; sample 3-5 source files and 3-5 test files for conventions; check factory/fixture patterns. Write CONVENTIONS.md and TESTING.md.

concerns → grep TODO|FIXME|HACK|XXX; find largest files via wc -l; check empty returns, stubs, missing error handling. Write CONCERNS.md.

Never read: .env, *.env, credentials.*, secrets.*, *.pem, *.key, SSH keys, serviceAccountKey.json. Note existence only.

Template structure per focus:

STACK.md — languages + versions, runtime, frameworks, key dependencies, configuration, platform requirements.

INTEGRATIONS.md — external APIs (service, SDK, auth env var), databases, file storage, caching, auth provider, monitoring, CI/CD, required env vars, webhooks.

ARCHITECTURE.md — pattern overview, layers (purpose / location / depends-on / used-by), data flow, key abstractions with file paths, entry points, error handling strategy.

STRUCTURE.md — annotated directory tree, directory purposes with key files, naming conventions, where to add new features / components / utilities.

CONVENTIONS.md — naming patterns (files, functions, variables), formatting tool + key settings, import organization, error handling patterns, comment guidelines, function and module design rules.

TESTING.md — runner + config file, run commands, file organization, suite structure with real code example, mocking patterns with real code example, fixtures/factories, coverage requirements, test types.

CONCERNS.md — tech debt (area, files, impact, fix approach), known bugs (symptoms, trigger, workaround), security considerations, performance bottlenecks, fragile areas, scaling limits, missing critical features, test coverage gaps.

Return format:

## Mapping Complete

**Focus:** {focus}
**Documents written:**
- `.ariadna_planning/codebase/{DOC1}.md` ({N} lines)
- `.ariadna_planning/codebase/{DOC2}.md` ({N} lines)

Ready for orchestrator summary.