docs: reorganize tree, restore architecture + research from archive, add Phase 0 reports

Active docs/ was stub scaffolding while the real docs sat in docs/_archive/.
Restore and correct them, and record the Phase 0 work.

- docs/architecture/current.md: verified system map (from archived SYSTEM_OVERVIEW,
  9 corrections against code).
- docs/research/competitors.md: sourced competitor analysis (from archived
  PRODUCT_RESEARCH, feature matrix corrected).
- docs/decisions/ADR-002-job-application-model.md: the Job/JobApplication split.
- docs/application-discovery-report.md, docs/implementation-roadmap.md,
  docs/phase-0-foundation-report.md, docs/career-workspace-branch-assessment.md.
- Remove 10 zero-byte placeholder files that advertised content that never existed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/technical/coding-standards.md

@@ -0,0 +1,52 @@
+# Coding Standards
+
+## General Rules
+
+Code should be:
+
+- Readable.
+- Self documenting.
+- Consistent.
+
+---
+
+# Naming
+
+Use meaningful names.
+
+Avoid:
+
+- Short unclear variables.
+- Generic service names.
+
+---
+
+# Methods
+
+Prefer:
+
+Small focused methods.
+
+Avoid:
+
+Large methods handling multiple responsibilities.
+
+---
+
+# Error Handling
+
+Errors should:
+
+- Be handled explicitly.
+- Provide useful messages.
+- Not expose sensitive information.
+
+---
+
+# Comments
+
+Comments should explain:
+
+Why something exists.
+
+Not what the code does.

docs/technical/deployment.md

@@ -0,0 +1,41 @@
+# Deployment
+
+## Current Goal
+
+Reliable production deployments.
+
+---
+
+# Deployment Requirements
+
+Before deploying:
+
+- Build succeeds.
+- Tests pass.
+- Database migrations reviewed.
+
+---
+
+# Production Safety
+
+Avoid:
+
+- Breaking migrations.
+- Downtime.
+- Lost data.
+
+---
+
+# Rollback
+
+Every deployment should have a recovery plan.
+
+---
+
+# Future SaaS
+
+Consider:
+
+- Automated deployments.
+- Staging environment.
+- Deployment approvals.

docs/technical/docker.md

@@ -0,0 +1,51 @@
+# Docker
+
+## Purpose
+
+Maintain consistent environments.
+
+---
+
+# Requirements
+
+Containers should:
+
+- Have clear names.
+- Use health checks.
+- Log correctly.
+
+---
+
+# Images
+
+Prefer:
+
+- Official images.
+- Pinned versions.
+
+---
+
+# Volumes
+
+Important data must use persistent storage.
+
+---
+
+# Production
+
+Monitor:
+
+- Container health.
+- Memory usage.
+- Disk usage.
+- Restarts.
+
+---
+
+# Common Issues
+
+Investigate:
+
+- Container crashes.
+- Storage exhaustion.
+- Network issues.

docs/technical/environment.md

@@ -0,0 +1,32 @@
+# Environment Configuration
+
+## Principles
+
+Never hardcode secrets.
+
+---
+
+# Configuration
+
+Use:
+
+- Environment variables.
+- Secret storage.
+
+---
+
+# Examples
+
+Database credentials.
+
+API keys.
+
+OAuth secrets.
+
+AI provider keys.
+
+---
+
+# Development
+
+Local configuration should not affect production.

docs/technical/git-workflow.md

@@ -0,0 +1,53 @@
+# Git Workflow
+
+## Branches
+
+Use feature branches.
+
+Examples:
+
+feature/cv-builder-themes
+
+feature/google-auth
+
+fix/pdf-parser
+
+---
+
+# Commits
+
+Commits should:
+
+- Describe the change.
+- Be focused.
+- Be reviewable.
+
+---
+
+# Commit Style
+
+Examples:
+
+feat: add CV theme selector
+
+fix: correct PDF extraction
+
+refactor: extract AI service
+
+docs: update architecture
+
+---
+
+# Before Commit
+
+Check:
+
+- Tests pass.
+- Build succeeds.
+- No secrets included.
+
+---
+
+# Deployment
+
+Do not deploy untested breaking changes.

docs/technical/logging.md

@@ -0,0 +1,45 @@
+# Logging
+
+## Purpose
+
+Make debugging possible.
+
+---
+
+# Log Levels
+
+Use:
+
+Trace.
+
+Debug.
+
+Information.
+
+Warning.
+
+Error.
+
+Critical.
+
+---
+
+# Do Not Log
+
+Never log:
+
+- Passwords.
+- Tokens.
+- API keys.
+- Private documents.
+
+---
+
+# Useful Logs
+
+Include:
+
+- Operation.
+- User context where safe.
+- Error details.
+- Correlation IDs.

docs/technical/monitoring.md

@@ -0,0 +1,39 @@
+# Monitoring
+
+## Purpose
+
+Detect problems early.
+
+---
+
+# Monitor
+
+Application:
+
+- Errors.
+- Response times.
+- Background jobs.
+
+Infrastructure:
+
+- CPU.
+- Memory.
+- Disk.
+- Containers.
+
+---
+
+# Alerts
+
+Important alerts:
+
+- Application unavailable.
+- Database errors.
+- Failed deployments.
+- Storage issues.
+
+---
+
+# User Experience
+
+Errors should be visible internally before users report them.

docs/technical/overview.md

@@ -0,0 +1,41 @@
+# Technical Overview
+
+## Purpose
+
+Define engineering standards for Jobjakt development.
+
+These guidelines help maintain:
+
+- Code quality.
+- Reliability.
+- Security.
+- Maintainability.
+
+---
+
+# Development Philosophy
+
+Prefer:
+
+- Simple solutions.
+- Clear code.
+- Incremental improvements.
+- Tested changes.
+
+Avoid:
+
+- Premature optimisation.
+- Large rewrites.
+- Unnecessary dependencies.
+
+---
+
+# Engineering Priorities
+
+Order of importance:
+
+1. User experience.
+2. Reliability.
+3. Security.
+4. Maintainability.
+5. Performance.

docs/technical/performance.md

@@ -0,0 +1,36 @@
+# Performance
+
+## Principles
+
+Optimise based on evidence.
+
+---
+
+# Important Areas
+
+Database:
+
+- Query efficiency.
+- Indexes.
+
+Frontend:
+
+- Bundle size.
+- Rendering.
+
+Backend:
+
+- Expensive operations.
+
+AI:
+
+- Token usage.
+- Response time.
+
+---
+
+# Avoid
+
+Optimising prematurely.
+
+Complex caching without measurements.

docs/technical/testing.md

@@ -0,0 +1,65 @@
+# Testing Strategy
+
+## Goal
+
+Maintain confidence while changing the application.
+
+---
+
+# Test Areas
+
+## Backend
+
+Test:
+
+- Business logic.
+- Services.
+- APIs.
+- Database behaviour.
+
+---
+
+## Frontend
+
+Test:
+
+- Important workflows.
+- Components.
+- User interactions.
+
+---
+
+# Priority Workflows
+
+Must protect:
+
+## Authentication
+
+- Signup.
+- Login.
+- OAuth.
+- Password reset.
+- 2FA.
+
+---
+
+## Jobs
+
+- Creating jobs.
+- Updating status.
+- Follow-ups.
+
+---
+
+## Career
+
+- CV upload.
+- CV extraction.
+- CV generation.
+- PDF generation.
+
+---
+
+# Production Confidence
+
+Critical user journeys should have automated tests.

docs/technical/troubleshooting.md

@@ -0,0 +1,32 @@
+# Troubleshooting
+
+## Purpose
+
+Provide debugging approach.
+
+---
+
+# General Process
+
+1. Reproduce issue.
+2. Check logs.
+3. Identify affected component.
+4. Make smallest safe fix.
+5. Verify.
+
+---
+
+# Production Issues
+
+Check:
+
+- Application logs.
+- Docker status.
+- Database.
+- External services.
+
+---
+
+# Never
+
+Do not randomly change production configuration without understanding the cause.