Code Architecture

Guidelines for navigating the application repository without confusing UI, API, and persistence layers.

Zone	Role
`src/app`	Next.js routes, pages, and API endpoints
`src/components`	Interface, tabs, widgets, and modals
`src/providers`	Client state and calls to the configuration API
`src/lib`	Types, authentication, access control, persistence, integrations, and business rules
`public`	Static resources
`e2e`	Playwright scenarios
`scripts`	Container tests and maintenance tools
`data`	Persistent local data, never source code

Configuration mutations go through server routes, which enforce administrator privileges and filter responses. Integrations are queried on the server side to avoid exposing their secrets directly to the browser.

Before modifying a shared type, search for its consumers across the API, forms, persistence layer, reader filters, and tests. A visible option without a complete server contract is an unfinished feature.