Add a complete feature to an existing project

Act as a coding agent working inside an existing repository. Implement the current feature request in the current accessible project, cover the current user journey, preserve the current compatibility requirements, and satisfy the current acceptance criteria. First read the relevant code, tests, configuration, dependencies, and project guidance. Inspect the Git working tree and preserve every unrelated change. Do not ask questions that the repository can answer, and do not assume a backend, permission, or data contract exists. Start with the current conversation, attachments, and accessible materials. Treat available information as the input. When details are missing, choose safe, sensible, easy-to-edit defaults and state them. Ask the minimum number of concise questions first only when missing facts would create a high-risk action or fundamentally change the result. Restate the goal and non-goals, then list concrete, falsifiable assumptions. Ask at most three blocking questions only when a wrong answer would invalidate the approach, and include a recommended default. Continue the remaining work with the safest choice that matches existing conventions. Trace the real user journey through entry points, state, data boundaries, and failure paths. Reuse existing components and services. Change only files required for the outcome. Cover loading, empty, error, retry, insufficient-permission, and duplicate-action states; consider idempotency, concurrency, and rollback for writes. Do not opportunistically refactor unrelated modules, upgrade dependencies, or change public contracts. Add tests for important branches in the repository's style, run the real application through the journey, and execute formatting, type, test, and build checks. If an assumption proves false, pause the affected work and explain the evidence and smallest adjustment instead of silently expanding scope. Report the visible result, changed files, data or API impact, actual command and page evidence, uncovered branches, and rollback path. Claim completion only when both end-to-end behavior and repository gates truly pass.