Vibecode pbmate.ro

You are building a lean indie version of pbmate.ro.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# pbmate.ro indie build

## Goal

Build the smallest trustworthy replacement for the core pbmate.ro workflow for one developer or a tiny team.

## Scope

A local trainer for maths problems you author yourself: pick a chapter, work through five problems, reveal graded hints, then the full solution, and watch a per chapter mastery bar move.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- roughly 5.000 vetted problems, each tied to a chapter of the Romanian programa and a difficulty tier
- official exam papers rebuilt as interactive tests, with each marking scheme re-derived point by point
- three progressive hints and a written solution on every problem, not just the correct letter
- the parent and teacher surfaces, assigned homework, and the iOS app
- somebody maintaining all of it when the programa or the exam format shifts

If those capabilities are essential, use KaTeX instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a personal Romanian maths practice trainer in an empty folder.
Stack: Next.js 15 (App Router), TypeScript, SQLite via better-sqlite3, Tailwind, KaTeX. Do not offer alternatives.
Problems live as Markdown files in content/problems, one per file, with frontmatter: id, chapter, grade, difficulty 1 to 5, statement, four options, correctIndex, hints (up to three, ordered nudge -> method -> setup), solution.
Write `npm run import` to validate every file into SQLite, failing loudly on a missing correctIndex, an out-of-range difficulty, an unknown chapter, or a hint containing the final answer as a substring.
Ship exactly three seed problems as format examples plus a chapters.json for one grade, taken from the official programa. Generate no problems yourself.
Practice loop: pick a chapter, get five problems ordered easy to hard, answer, then reveal hints one at a time before the solution.
Record every attempt (problem id, chosen option, correct, seconds, hints used) in SQLite.
Show a per-chapter mastery bar from the last twenty attempts on that chapter and a weak-chapters list. No streaks, no badges, no daily guilt.
Add `npm run drill` that serves only problems previously answered wrong.
Render maths with KaTeX inline and display, and verify the seed problems render before you finish.
Handle Romanian diacritics correctly in the files and the UI.
Add `npm run export` writing all attempts to CSV, and keep every byte on the local disk.
If ANTHROPIC_API_KEY is set in .env, add an optional `npm run draft -- paper.pdf` that turns an exam PDF into draft Markdown in content/drafts, never imported until a human moves the file, and print a warning that the answer key is unverified.
Secrets in .env, ship .env.example, commit neither.
Test the importer validation rules and one end-to-end five-problem session.
Write a README covering setup, the problem file format, and how to add a chapter.
Leave out: accounts, payments, hosting, telemetry, parent and teacher views, a mobile app, and anything claiming to grade a real exam.
Finish by running the import and the tests, then print the exact commands used.

## Required capabilities

- Node 22
- your own problem set, or the public Bacalaureat and Evaluare Națională PDFs
- optional Anthropic or OpenAI API key for draft extraction from those PDFs
- somebody willing to solve every problem before trusting its answer key

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of pbmate.ro.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# pbmate.ro indie build

## Goal

Build the smallest trustworthy replacement for the core pbmate.ro workflow for one developer or a tiny team.

## Scope

A local trainer for maths problems you author yourself: pick a chapter, work through five problems, reveal graded hints, then the full solution, and watch a per chapter mastery bar move.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- roughly 5.000 vetted problems, each tied to a chapter of the Romanian programa and a difficulty tier
- official exam papers rebuilt as interactive tests, with each marking scheme re-derived point by point
- three progressive hints and a written solution on every problem, not just the correct letter
- the parent and teacher surfaces, assigned homework, and the iOS app
- somebody maintaining all of it when the programa or the exam format shifts

If those capabilities are essential, use KaTeX instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a personal Romanian maths practice trainer in an empty folder.
Stack: Next.js 15 (App Router), TypeScript, SQLite via better-sqlite3, Tailwind, KaTeX. Do not offer alternatives.
Problems live as Markdown files in content/problems, one per file, with frontmatter: id, chapter, grade, difficulty 1 to 5, statement, four options, correctIndex, hints (up to three, ordered nudge -> method -> setup), solution.
Write `npm run import` to validate every file into SQLite, failing loudly on a missing correctIndex, an out-of-range difficulty, an unknown chapter, or a hint containing the final answer as a substring.
Ship exactly three seed problems as format examples plus a chapters.json for one grade, taken from the official programa. Generate no problems yourself.
Practice loop: pick a chapter, get five problems ordered easy to hard, answer, then reveal hints one at a time before the solution.
Record every attempt (problem id, chosen option, correct, seconds, hints used) in SQLite.
Show a per-chapter mastery bar from the last twenty attempts on that chapter and a weak-chapters list. No streaks, no badges, no daily guilt.
Add `npm run drill` that serves only problems previously answered wrong.
Render maths with KaTeX inline and display, and verify the seed problems render before you finish.
Handle Romanian diacritics correctly in the files and the UI.
Add `npm run export` writing all attempts to CSV, and keep every byte on the local disk.
If ANTHROPIC_API_KEY is set in .env, add an optional `npm run draft -- paper.pdf` that turns an exam PDF into draft Markdown in content/drafts, never imported until a human moves the file, and print a warning that the answer key is unverified.
Secrets in .env, ship .env.example, commit neither.
Test the importer validation rules and one end-to-end five-problem session.
Write a README covering setup, the problem file format, and how to add a chapter.
Leave out: accounts, payments, hosting, telemetry, parent and teacher views, a mobile app, and anything claiming to grade a real exam.
Finish by running the import and the tests, then print the exact commands used.

## Required capabilities

- Node 22
- your own problem set, or the public Bacalaureat and Evaluare Națională PDFs
- optional Anthropic or OpenAI API key for draft extraction from those PDFs
- somebody willing to solve every problem before trusting its answer key

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of pbmate.ro.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# pbmate.ro product brief

## Problem

The trainer is not the product. An agent will hand you a clean multiple-choice runner with LaTeX, hints and a mastery chart in one evening, and then you will be staring at an empty database. What is actually being sold here is roughly 5.000 published problems mapped chapter by chapter to the Romanian programa, the official Bacalaureat and Evaluare Națională papers rebuilt as interactive tests with every marking scheme re-derived rather than trusted, and four role surfaces (pupil, parent, teacher, plus an iOS app) grown over more than 2.300 commits. A language model will cheerfully generate a thousand Romanian maths problems for you, and a worrying share will carry a wrong answer key, a hint that leaks the answer, or a chapter label that does not match the programa. You will not find out which until a child gets one wrong for the wrong reason. Check a hundred by hand and the price stops looking mysterious. Build the trainer if you enjoy building; the honest free move is the ministry's own paper archive, not a rebuild.

## Product outcome

A local trainer for maths problems you author yourself: pick a chapter, work through five problems, reveal graded hints, then the full solution, and watch a per chapter mastery bar move.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 22
- your own problem set, or the public Bacalaureat and Evaluare Națională PDFs
- optional Anthropic or OpenAI API key for draft extraction from those PDFs
- somebody willing to solve every problem before trusting its answer key

## Explicit non-goals for v1

- roughly 5.000 vetted problems, each tied to a chapter of the Romanian programa and a difficulty tier
- official exam papers rebuilt as interactive tests, with each marking scheme re-derived point by point
- three progressive hints and a written solution on every problem, not just the correct letter
- the parent and teacher surfaces, assigned homework, and the iOS app
- somebody maintaining all of it when the programa or the exam format shifts

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build a personal Romanian maths practice trainer in an empty folder.
Stack: Next.js 15 (App Router), TypeScript, SQLite via better-sqlite3, Tailwind, KaTeX. Do not offer alternatives.
Problems live as Markdown files in content/problems, one per file, with frontmatter: id, chapter, grade, difficulty 1 to 5, statement, four options, correctIndex, hints (up to three, ordered nudge -> method -> setup), solution.
Write `npm run import` to validate every file into SQLite, failing loudly on a missing correctIndex, an out-of-range difficulty, an unknown chapter, or a hint containing the final answer as a substring.
Ship exactly three seed problems as format examples plus a chapters.json for one grade, taken from the official programa. Generate no problems yourself.
Practice loop: pick a chapter, get five problems ordered easy to hard, answer, then reveal hints one at a time before the solution.
Record every attempt (problem id, chosen option, correct, seconds, hints used) in SQLite.
Show a per-chapter mastery bar from the last twenty attempts on that chapter and a weak-chapters list. No streaks, no badges, no daily guilt.
Add `npm run drill` that serves only problems previously answered wrong.
Render maths with KaTeX inline and display, and verify the seed problems render before you finish.
Handle Romanian diacritics correctly in the files and the UI.
Add `npm run export` writing all attempts to CSV, and keep every byte on the local disk.
If ANTHROPIC_API_KEY is set in .env, add an optional `npm run draft -- paper.pdf` that turns an exam PDF into draft Markdown in content/drafts, never imported until a human moves the file, and print a warning that the answer key is unverified.
Secrets in .env, ship .env.example, commit neither.
Test the importer validation rules and one end-to-end five-problem session.
Write a README covering setup, the problem file format, and how to add a chapter.
Leave out: accounts, payments, hosting, telemetry, parent and teacher views, a mobile app, and anything claiming to grade a real exam.
Finish by running the import and the tests, then print the exact commands used.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted pbmate.ro capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# pbmate.ro indie build

## Goal

Build the smallest trustworthy replacement for the core pbmate.ro workflow for one developer or a tiny team.

## Scope

A local trainer for maths problems you author yourself: pick a chapter, work through five problems, reveal graded hints, then the full solution, and watch a per chapter mastery bar move.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- roughly 5.000 vetted problems, each tied to a chapter of the Romanian programa and a difficulty tier
- official exam papers rebuilt as interactive tests, with each marking scheme re-derived point by point
- three progressive hints and a written solution on every problem, not just the correct letter
- the parent and teacher surfaces, assigned homework, and the iOS app
- somebody maintaining all of it when the programa or the exam format shifts

If those capabilities are essential, use KaTeX instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build a personal Romanian maths practice trainer in an empty folder.
Stack: Next.js 15 (App Router), TypeScript, SQLite via better-sqlite3, Tailwind, KaTeX. Do not offer alternatives.
Problems live as Markdown files in content/problems, one per file, with frontmatter: id, chapter, grade, difficulty 1 to 5, statement, four options, correctIndex, hints (up to three, ordered nudge -> method -> setup), solution.
Write `npm run import` to validate every file into SQLite, failing loudly on a missing correctIndex, an out-of-range difficulty, an unknown chapter, or a hint containing the final answer as a substring.
Ship exactly three seed problems as format examples plus a chapters.json for one grade, taken from the official programa. Generate no problems yourself.
Practice loop: pick a chapter, get five problems ordered easy to hard, answer, then reveal hints one at a time before the solution.
Record every attempt (problem id, chosen option, correct, seconds, hints used) in SQLite.
Show a per-chapter mastery bar from the last twenty attempts on that chapter and a weak-chapters list. No streaks, no badges, no daily guilt.
Add `npm run drill` that serves only problems previously answered wrong.
Render maths with KaTeX inline and display, and verify the seed problems render before you finish.
Handle Romanian diacritics correctly in the files and the UI.
Add `npm run export` writing all attempts to CSV, and keep every byte on the local disk.
If ANTHROPIC_API_KEY is set in .env, add an optional `npm run draft -- paper.pdf` that turns an exam PDF into draft Markdown in content/drafts, never imported until a human moves the file, and print a warning that the answer key is unverified.
Secrets in .env, ship .env.example, commit neither.
Test the importer validation rules and one end-to-end five-problem session.
Write a README covering setup, the problem file format, and how to add a chapter.
Leave out: accounts, payments, hosting, telemetry, parent and teacher views, a mobile app, and anything claiming to grade a real exam.
Finish by running the import and the tests, then print the exact commands used.

## Required capabilities

- Node 22
- your own problem set, or the public Bacalaureat and Evaluare Națională PDFs
- optional Anthropic or OpenAI API key for draft extraction from those PDFs
- somebody willing to solve every problem before trusting its answer key

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# pbmate.ro product brief

## Problem

The trainer is not the product. An agent will hand you a clean multiple-choice runner with LaTeX, hints and a mastery chart in one evening, and then you will be staring at an empty database. What is actually being sold here is roughly 5.000 published problems mapped chapter by chapter to the Romanian programa, the official Bacalaureat and Evaluare Națională papers rebuilt as interactive tests with every marking scheme re-derived rather than trusted, and four role surfaces (pupil, parent, teacher, plus an iOS app) grown over more than 2.300 commits. A language model will cheerfully generate a thousand Romanian maths problems for you, and a worrying share will carry a wrong answer key, a hint that leaks the answer, or a chapter label that does not match the programa. You will not find out which until a child gets one wrong for the wrong reason. Check a hundred by hand and the price stops looking mysterious. Build the trainer if you enjoy building; the honest free move is the ministry's own paper archive, not a rebuild.

## Product outcome

A local trainer for maths problems you author yourself: pick a chapter, work through five problems, reveal graded hints, then the full solution, and watch a per chapter mastery bar move.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- Node 22
- your own problem set, or the public Bacalaureat and Evaluare Națională PDFs
- optional Anthropic or OpenAI API key for draft extraction from those PDFs
- somebody willing to solve every problem before trusting its answer key

## Explicit non-goals for v1

- roughly 5.000 vetted problems, each tied to a chapter of the Romanian programa and a difficulty tier
- official exam papers rebuilt as interactive tests, with each marking scheme re-derived point by point
- three progressive hints and a written solution on every problem, not just the correct letter
- the parent and teacher surfaces, assigned homework, and the iOS app
- somebody maintaining all of it when the programa or the exam format shifts

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build a personal Romanian maths practice trainer in an empty folder.
Stack: Next.js 15 (App Router), TypeScript, SQLite via better-sqlite3, Tailwind, KaTeX. Do not offer alternatives.
Problems live as Markdown files in content/problems, one per file, with frontmatter: id, chapter, grade, difficulty 1 to 5, statement, four options, correctIndex, hints (up to three, ordered nudge -> method -> setup), solution.
Write `npm run import` to validate every file into SQLite, failing loudly on a missing correctIndex, an out-of-range difficulty, an unknown chapter, or a hint containing the final answer as a substring.
Ship exactly three seed problems as format examples plus a chapters.json for one grade, taken from the official programa. Generate no problems yourself.
Practice loop: pick a chapter, get five problems ordered easy to hard, answer, then reveal hints one at a time before the solution.
Record every attempt (problem id, chosen option, correct, seconds, hints used) in SQLite.
Show a per-chapter mastery bar from the last twenty attempts on that chapter and a weak-chapters list. No streaks, no badges, no daily guilt.
Add `npm run drill` that serves only problems previously answered wrong.
Render maths with KaTeX inline and display, and verify the seed problems render before you finish.
Handle Romanian diacritics correctly in the files and the UI.
Add `npm run export` writing all attempts to CSV, and keep every byte on the local disk.
If ANTHROPIC_API_KEY is set in .env, add an optional `npm run draft -- paper.pdf` that turns an exam PDF into draft Markdown in content/drafts, never imported until a human moves the file, and print a warning that the answer key is unverified.
Secrets in .env, ship .env.example, commit neither.
Test the importer validation rules and one end-to-end five-problem session.
Write a README covering setup, the problem file format, and how to add a chapter.
Leave out: accounts, payments, hosting, telemetry, parent and teacher views, a mobile app, and anything claiming to grade a real exam.
Finish by running the import and the tests, then print the exact commands used.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted pbmate.ro capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent