Add artifact vault contents

projects/dotfiles/052-pi-subagents-final-deployment-verification-task.md

@@ -0,0 +1,37 @@
+---
+status: open
+parent: "[[027-pi-subagents-implementation-spec-task]]"
+blocked-by:
+  - "[[047-pi-subagents-lifecycle-controls-task]]"
+  - "[[048-pi-subagents-config-agents-tool-profiles-task]]"
+  - "[[049-pi-subagents-batch-concurrency-task]]"
+  - "[[050-pi-subagents-fork-context-task]]"
+  - "[[051-pi-subagents-status-ui-task]]"
+tags:
+  - ticket/task/afk
+---
+
+# Finalize deployment and verification for the subagent extension
+
+## Question
+
+Wire the completed subagent extension through the existing dotfiles Pi module path and record a final verification pass across Nix, reload, spawning, status, results, cancellation, context modes, and UI toggling.
+
+## What to build
+
+Finish the implementation as a deployed feature rather than a collection of working slices.
+The managed Pi extensions source should contain the complete extension, Nix evaluation should prove the deployment seam, and the manual verification checklist from the implementation spec should be exercised and recorded.
+Any intentionally deferred choices should be written down as follow-up scope.
+
+## Acceptance criteria
+
+- [ ] The managed Pi extensions source includes the subagent extension.
+- [ ] `nix flake check` passes.
+- [ ] Targeted `nix eval` confirms Pi is enabled and the managed extensions path is present.
+- [ ] Manual Pi checks from the spec are recorded in the task notes.
+- [ ] Any intentionally deferred implementation choices are documented as follow-up scope, not hidden TODOs.
+
+## Implementation Notes
+
+This is the final integration slice.
+Do not start it until the prerequisite behavior slices are complete.