Repository Possession Prompt Sequence

Using the repository inventory, trace one representative user action from its entry point through user interface, route or handler, service logic, data access, external dependency, and returned result. Cite the exact files, functions, classes, and configuration involved.

Present the flow first in plain language and then as a compact sequence diagram. Mark authentication, authorization, validation, persistence, external calls, failure handling, and logging boundaries. Identify any step that is inferred rather than proven.

Do not run the application, change code, call external services, or inspect secrets unless I separately approve those actions.