chore(tasks): untrack local task files

- WHY: keep task lifecycle files local-only per gitignore policy
- WHAT: remove tracked .tasks entries from repository index
- RULE: apply repository workflow task folder behavior

.tasks/done/TASK-20260222-001.md

@@ -1,86 +0,0 @@
-# Stage 1 Task
-
-## 0. Header
-- Task ID: TASK-20260222-001
-- Title: Consolidate identity abstractions inside thalos-service plan
-- Status: Planned
-- Priority: P1
-- Target Repo: thalos-service
-- Target Branch: feature/thalos-service-001
-- Related Master Plan: plan/master-stage1-structural-normalization-2026-02-22.md
-- Related Mini Plan: plan/thalos-service-mini-plan.md
-
-## 1. Goal (What and Why)
-### What
-- Map legacy building block abstractions into service-owned modules
-- Document explicit prohibition of Blueprint ownership for identity abstractions
-
-### Why
-- Identity-specific abstractions must remain strictly within Thalos
-
-## 2. Scope
-### In Scope
-- Identity abstraction ownership and consolidation map
-
-### Out of Scope
-- Moving identity abstractions into Blueprint
-
-## 3. Constraints (Non-Negotiable)
-- Stage 1 planning only. No implementation changes.
-- Do not modify any file under legacy.
-- Do not run repo provisioning or CI generation.
-- Follow the approved architecture boundaries and protocol policy.
-- Keep identity abstractions inside Thalos repositories.
-
-## 4. Documentation Requirement
-- [ ] Capture planning decisions clearly for handoff.
-- [ ] Identify documentation and diagram updates expected in later stages.
-
-## 5. Context
-- This task derives from plan/thalos-service-mini-plan.md.
-- This task must remain decision-focused and implementation-ready.
-
-## 6. Proposed Approach
-- Define module ownership and anti-leakage rules for identity abstractions
-
-## 7. Execution Steps
-1. Review legacy evidence relevant to this task scope.
-2. Define target boundary decisions and contract implications.
-3. Record risks, dependencies, and compatibility notes.
-4. Produce clear handoff guidance for implementation stage.
-
-## 8. Acceptance Criteria
-- [ ] Decisions are explicit, scoped, and actionable.
-- [ ] Ownership boundaries are unambiguous.
-- [ ] Protocol policy alignment is explicit where applicable.
-- [ ] No forbidden Stage 1 actions were performed.
-
-## 9. Testing Plan
-### Unit Tests
-- Not applicable for Stage 1 planning artifacts.
-
-### Validation
-- Ensure consistency with master plan and mini plan.
-
-## 10. Definition of Done
-- [ ] Task content is complete and consistent with other task files.
-- [ ] References to master and mini plans are correct.
-- [ ] Handoff notes are clear enough for immediate implementation.
-
-## 11. Risks and Questions
-- Risk: boundary drift during implementation.
-- Mitigation: enforce repo intent metadata and mini plan ownership.
-
-## 12. Handoff Notes
-- Preserve approved constraints exactly.
-- Implementers should execute this task only after reading master and mini plans.
-
-END OF TASK
-
-## 13. Completion Metadata
-- Completion Stage: Stage 3 Execution
-- Completed On: 2026-02-22
-- Completed By: Codex
-- Completion Branch: feature/thalos-service-001
-- Completion Commit: 9f1790e
-- Lifecycle State: done