Admin

Overview

Domain page auto-seeded by wiki bootstrap for new source lane.

Covered files

• apps/portal/admin/README.md
• apps/portal/admin/__init__.py
• apps/portal/admin/admin_settings.py
• apps/portal/templates/admin/file_tree.html
• apps/portal/templates/admin/home.html
• apps/portal/tests/test_admin_env_isolation_check_api.py
• apps/portal/tests/test_admin_file_tree_api.py
• apps/portal/tests/test_admin_monitoring_api.py
• apps/portal/tests/test_admin_resilience_drills_api.py
• apps/portal/tests/test_admin_settings_api.py

File map

README.md

• Path: apps/portal/admin/README.md
• What: apps/portal/admin/ contains admin control-plane handlers for environment/runtime operations. This boundary currently has 3 direct file(s) and 0 direct subfolder(s).
• Does: It implements runtime-facing product behavior and integration wiring (dominant direct file kinds: .py:2, .md:1).
• Why: This is where user-visible behavior is delivered, so clear ownership is critical for reliable iteration.

__init__.py

• Path: apps/portal/admin/__init__.py
• What: init module for apps/portal/admin.
• Does: Implements module routines used by this runtime surface.
• Why: Keeps behavior boundaries explicit so wiki maps stay useful without reading full files.

admin_settings.py

• Path: apps/portal/admin/admin_settings.py
• What: Typed admin settings catalog and deterministic validation helpers.
• Does: Defines editable/read-only settings metadata plus payload validation policy.
• Why: Implements TASK-124 initial admin settings contract for API clients.

file_tree.html

• Path: apps/portal/templates/admin/file_tree.html
• What: Template for file tree UI surface in apps/portal/templates.
• Does: Defines rendered structure, states, and UI hooks consumed by Portal routes.
• Why: Keeps operator-facing behavior predictable and discoverable without digging into route code.

home.html

• Path: apps/portal/templates/admin/home.html
• What: Template for home UI surface in apps/portal/templates.
• Does: Defines rendered structure, states, and UI hooks consumed by Portal routes.
• Why: Keeps operator-facing behavior predictable and discoverable without digging into route code.

test_admin_env_isolation_check_api.py

• Path: apps/portal/tests/test_admin_env_isolation_check_api.py
• What: Test admin env isolation check api module for apps/portal/tests.
• Does: Implements TestAdminEnvIsolationCheckApi used by this runtime surface.
• Why: Keeps behavior boundaries explicit so wiki maps stay useful without reading full files.

test_admin_file_tree_api.py

• Path: apps/portal/tests/test_admin_file_tree_api.py
• What: Tests for admin file tree page and JSON browsing/preview APIs.
• Does: Verifies operator-facing file tree routes, root scoping, search, and file preview guardrails.
• Why: Locks the Admin File Tree contract so Portal can safely expose VPS and project structure browsing.

test_admin_monitoring_api.py

• Path: apps/portal/tests/test_admin_monitoring_api.py
• What: Test admin monitoring api module for apps/portal/tests.
• Does: Covers drift-check and smoke-probe admin endpoints.
• Why: Ensures monitoring scripts map to stable API contracts and failures surface as 502.

test_admin_resilience_drills_api.py

• Path: apps/portal/tests/test_admin_resilience_drills_api.py
• What: Test admin resilience drill api module for apps/portal/tests.
• Does: Covers backup/restore drill and degraded-mode drill endpoints.
• Why: Ensures admin drill APIs map script success/failure to stable HTTP contracts.

test_admin_settings_api.py

• Path: apps/portal/tests/test_admin_settings_api.py
• What: Tests for admin settings catalog/validation APIs and audit event append behavior.
• Does: Verifies positive and negative validation payloads plus JSONL audit writes.
• Why: Locks TASK-124/TASK-125 initial API and audit contract.

Test coverage

• (no explicit Tests headers found)