Current Task

AUTH-001 (Revised)

This task resumes AUTH-001 after resolving the documented conflict recorded in:

docs/ai/memory/30_AUTH001_conflict.md

This is a continuation of AUTH-001.

It is NOT a new task.

Do NOT begin AUTH-002.

Do NOT begin AUTH-003.

Do NOT begin AUTH-004.

---

Mandatory Reading

Before continuing implementation, review:

Governance

- AI.md v1.1
- AI_DEVELOPMENT_SYSTEM.md
- WORKFLOW.md
- PROJECT.md

Architecture

- DBP_v1.1
- ADR v1.0
- MASTER_IMPLEMENTATION_BACKLOG_v1.1

Sprint Documents

- SPRINT2_PLANNING.md
- SPRINT2_EXECUTION_GUIDE.md
- SPRINT2_PROMPT_LIBRARY.md

Previous Prompt

- docs/ai/prompts/37_AUTH001.md

Conflict Record

- docs/ai/memory/30_AUTH001_conflict.md

---

Conflict Resolution

The previously reported conflict has been reviewed.

Decision:

Sprint 2 must respect the frozen Sprint 0 framework.

BaseController::render() remains unchanged.

No kernel modification is permitted.

Authentication controllers remain module-based.

Views shall follow the existing centralized view architecture provided by Sprint 0.

Therefore:

Authentication views are implemented under

app/views/

instead of

app/modules/Auth/views/

This is an approved implementation clarification.

It is NOT a kernel change.

It is NOT an architecture redesign.

It is NOT permission to redesign the framework.

---

Implementation Rules

Continue implementing AUTH-001.

Reuse every completed implementation where possible.

Do NOT discard completed work.

Only modify files necessary to resolve the approved clarification.

Do NOT introduce additional changes.

Do NOT create undocumented files.

Do NOT modify app/core.

Do NOT modify BaseController.php.

Do NOT override render().

Do NOT duplicate rendering logic.

---

View Rules

Authentication controllers remain inside

app/modules/Auth/

Authentication views are rendered through the existing BaseController::render() mechanism.

Views therefore reside under

app/views/auth/

using the standard render() convention.

---

Scope

Continue ONLY AUTH-001.

No additional features.

No improvements.

No refactoring.

No cleanup outside AUTH-001.

---

Validation

Before finalizing verify:

✓ BaseController remains unchanged.

✓ No kernel file modified.

✓ Authentication controller renders correctly through BaseController.

✓ View path matches the existing framework convention.

✓ Files Expected remain correct.

✓ Acceptance Criteria still pass.

---

If any NEW documentation conflict is discovered:

STOP.

Explain.

Wait for approval.

Do not guess.

---

After implementation provide

1. Updated Implementation Summary

2. Files Created

3. Files Modified

4. Conflict Resolution Verification

5. Acceptance Criteria Verification

6. Security Checklist Verification

7. Definition of Done

8. Proposed Git Commit Message
(do NOT execute)

9. Documentation Deviations
(if any)

10. Dependency Verification

AUTH-001 ends after implementation.

Do NOT continue to AUTH-002.

Wait for approval.