Changelog

2026-03-06 — P1/P2/P3 Improvements + Quick Wins

verification-matrix as a single source for all "verification required" items across documents.
day-1-day-3-onboarding for 3-day junior learning pathway.
change-example-pack contains 3 realistic change examples complete with impact and rollback.

api-examples enhanced with source proof labels (REAL-SANITIZED vs MOCK) and explicit runtime state.
api-reference adds runtime evidence status + verification matrix reference.
The dense diagram in end-to-end-process is broken down into per-domain diagrams: SPB, PO, SPK, Payment.
Visual consistency strengthened: quick-summary box + section labels on main long pages.
Onboarding/intro shortcut links updated to new page.
The sidebar has been overhauled to make the learning sequence clearer.

New verification-guideline page for standard status: Verified, Partial, Unknown.

All Verification Notes sections are standardized with the format: Status, Scope, Action.
Intro + sidebar updated so guidelines are easy for junior devs to find.

Establish single source of truth:
The full API is centralized in api-full-catalog.
api-endpoints changed to index pages + read routes.
database-viewer is made into a simple quick viewer, details remain in database-design-full.
Added Where to find X sections in intro and onboarding-junior.
Standardize terms/glossary for SPB/PO/SPK/payment terms/status.
Tidy up the sidebar order for a more logical reading flow and remove duplicative API categories.
Fixed an incorrect term in the controller map (SPB = Goods Request Letter).

The main goal of this pass: reduce overlap between pages and make scanning easier for junior devs.

New/completely overhauled documents:
overview
architecture
role-access-matrix
domain-model
module-map
business-flows
api-reference
fire-cookbook
request-response-catalog
database-schema-map
state-machine
integration-points
setup-local
deployment-runbook
observability-ops
trouble shooting
glossary
Mermaid diagrams for architecture, main flow, domain relationships, and state machines.
Requires Verification marking for areas that cannot be validated by runtime.

Focus UX documentation to onboarding + daily operations of the team.
Content structure overhauled to be linear from concept → implementation → operations.