fix(tasks,implement): address review — remove duplicate format note and fix context-loss gap

Remove governed-operation hint from tasks-template.md Format Legend; the
generation rule in tasks.md is the single authoritative source, so the legend
entry was redundant duplication.

Add Task-level re-read instruction to implement.md step 6: before executing
each task the agent re-reads that task's entry from tasks.md on disk. This
closes the gap the reviewer identified — the initial tasks.md load can be
compacted out of context during a long session, but a per-task re-read ensures
embedded governed commands are always in active context at execution time.

Author: ayeshakhalid192007-dev

templates/commands/implement.md

@@ -142,10 +142,11 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 6. Execute implementation following the task plan:
    - **Phase-by-phase execution**: Complete each phase before moving to the next
-   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  
+   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
    - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
    - **File-based coordination**: Tasks affecting the same files must run sequentially
    - **Validation checkpoints**: Verify each phase completion before proceeding
+   - **Task-level re-read**: Before executing each individual task, re-read that task's entry from tasks.md to get its complete body. This ensures any embedded commands (e.g., governed operations with exact flags and env vars) are in active context even if the initial tasks.md load was compressed out during a long session.
 
 7. Implementation execution rules:
    - **Setup first**: Initialize project structure, dependencies, configuration

templates/tasks-template.md

@@ -17,7 +17,6 @@ description: "Task list template for feature implementation"
 - **[P]**: Can run in parallel (different files, no dependencies)
 - **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3)
 - Include exact file paths in descriptions
-- For **governed operations** (commands the constitution defines with specific syntax): append the exact command — e.g., `Push packages: \`dotnet nuget push "*.nupkg" --api-key $KEY --source $URL\``
 
 ## Path Conventions