Read Lucas Vitti's Development Guidelines, version 3.2.0, at: https://lucas.mat.br/development-guidelines/versions/3.2.0/guidelines.md Guideline material by Lucas Vitti (https://lucas.mat.br), licensed under CC BY 4.0: https://creativecommons.org/licenses/by/4.0/ Scope and attribution: https://lucas.mat.br/development-guidelines/versions/3.2.0/license.html This licenses guideline content only; application licenses remain separate. Also read the applicable repository instructions and project documentation. Confirm which edition you actually read and apply the relevant requirements. If the page is inaccessible, ask for the Markdown copy; do not claim to have read it. Respect the task's scope and existing authorization. Audit-only tasks remain read-only. Identify material conflicts or justified exceptions before the affected work. Keep independent authorized work moving. Do not add features just to satisfy a pattern. Before implementation, save and present an architecture and UX plan in the project's dedicated documentation folder, normally docs/. Include the DOC-09 parameter register: all internal hardcoded behavior/policy values and configuration defaults, plain-language effects, exact values/units, source and enforcement, overrides, rationale, change impact, approval, and checks. Declare coverage and gaps. Obtain explicit approval for its identified revision and scope; record the approver, date, and approval reference. Reuse approval covering unchanged scope. Revise the plan and obtain renewed approval for material scope changes before the affected work. Apply ARCH-07 through ARCH-13: define public boundary contracts, data/state ownership, allowed and prohibited dependencies, and keep handwritten source cohesive. Demonstrate a new application's baseline through a small working feature; adopt incrementally for an existing application. Use narrow external contracts and justified adapters; verify dependency restrictions and a relevant change-isolation scenario. Record the source/version of any reusable starter, distinguish generated and project-owned files, and review upgrades. Review touched files over 300 code lines and functions over 50; extract cohesive units or record a scoped exception before completion. Report the final source map, size-review dispositions, dependency review, and relevant behavior checks. For an audit, provide evidence-based findings and acceptance criteria without making fixes. For interface work, translate relevant visual principles into concrete choices and verify the rendered result. For new or materially changed pages/forms, document one main intent and where secondary tasks open. Maintain the project design guide, source map, page inventory, approved plans, decisions, full technical version journals, and separate user changelogs in the dedicated documentation folder. For every version, keep the full technical journal with evidence, compatibility impact, and honest release/deployment status. Also write a separate user changelog explaining practical changes, moved/removed controls or pages, fixes, affected users, and required actions in product language. Use matching version identities, dates, and actual availability in both records. For internal-only releases, retain a user entry saying "No user-visible changes in this version." Preserve both histories and append dated corrections. Reconcile parameter documentation with implementation and effective deployment constraints; explain changed limits/defaults in the journal without claiming proposals are deployed. Before deployment, present the result and both changelogs and confirm authorization covers the release and target; plan approval alone does not authorize deployment. An existing explicit approval may cover both plan and deployment; never infer approval from silence or the AI's own decision. Avoid competing nested interactions; distinguish navigation, filters, view controls, task surfaces, and scroll owners. Task: [describe the requested work and constraints]