**Purpose:** the Git-tracked, **user-facing** knowledge base: real functions, pages, controls, account behavior, prerequisites, how to use each available capability, troubleshooting and limitations.
**Current product status:** P02 local backend Compose, P03 imported Login V2 source, P04 account portal source. No integrated deployed product yet; Account Portal dependency installs/builds, login and health checks remain unverified. **Do not claim pages/buttons are working in production merely because source exists.**
## What to read
1. [USER-GUIDE.md](USER-GUIDE.md) — every currently first-party Account Portal page, button and link, security/login semantics.
2. [SETUP-GUIDE.md](SETUP-GUIDE.md) — current dev stack prerequisites, account OIDC setup plan, configuration variables and boundaries.
3. [FEATURES-STATUS.md](FEATURES-STATUS.md) — implemented vs not yet integrated/tested/available.
4. [TROUBLESHOOTING.md](TROUBLESHOOTING.md) — common observable issues and *safe* diagnosis.
8. [MINIFEST.md](MINIFEST.md) — exact files and purposes.
## Rules for every future developer/AI agent
- Update the **corresponding user guide and button/page instructions in the same approved phase** as code changes.
- For each feature: name, who can use it, URL, action/button, what data it shows or changes, errors/permissions, prerequisites, exact current status and verified evidence.
- Do **not** copy implementation internals here as the only explanation; put developer file/function details under `project/`.
- Do not omit known restrictions or advertise planned abilities as live.
- Never publish real personal user data, passwords, access tokens or secrets.
Full update policy is in root [AGENTS.md](../AGENTS.md). A list of available docs is in [MINIFEST.md](MINIFEST.md).
For manual Gitea runner verification and its limitations, see [P05-CI-01.md](P05-CI-01.md). A green backend discovery smoke is not an authenticated user-login result.