8.9 KiB
phase, plan, type, wave, depends_on, files_modified, autonomous, requirements, must_haves
| phase | plan | type | wave | depends_on | files_modified | autonomous | requirements | must_haves | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 11-real-world-rollout-feedback | 02 | execute | 2 |
|
|
false |
|
|
Purpose: RWR-02 requires that the deployed instance actually produces value — not just that it runs. "Package reached real endpoints" is the core proof.
Output: A real printer visible on a real endpoint, plus .planning/phases/11-real-world-rollout-feedback/deploy/ROLLOUT-RUN.md recording the rollout.
<execution_context> @C:/Users/SebastienQUEROL/.claude/get-shit-done/workflows/execute-plan.md @C:/Users/SebastienQUEROL/.claude/get-shit-done/templates/summary.md </execution_context>
@.planning/phases/11-real-world-rollout-feedback/deploy/DEPLOYMENT.md @.planning/phases/11-real-world-rollout-feedback/11-01-deploy-container-to-msp-SUMMARY.md @.planning/phases/10-real-world-runtime-validation/RUNTIME-VALIDATION.md Task 1: Scaffold ROLLOUT-RUN.md .planning/phases/11-real-world-rollout-feedback/deploy/ROLLOUT-RUN.md Create `.planning/phases/11-real-world-rollout-feedback/deploy/ROLLOUT-RUN.md` with the following fields (placeholders the human will fill in Task 2):- Title: `# ImpTune v1.1 Rollout — First Real Package Run`
- Source instance:
- `imptune_url:` (copy from DEPLOYMENT.md)
- `imptune_commit_sha:` (copy from DEPLOYMENT.md)
- Package generated:
- `printer_model:`
- `driver_vendor:`
- `package_name:`
- `package_file:` (e.g. `FloorPrinter_A.intunewin`)
- `generated_at:` (ISO8601)
- Delivery channel (exactly one):
- `delivery_channel:` — `intune` OR `ninjarmm`
- If intune: `tenant:`, `app_id:`, `assigned_group:`
- If ninjarmm: `org:`, `policy_or_script_id:`, `target_device_group:`
- Target endpoint:
- `device_name:`
- `os_build:`
- `push_started_at:`
- `install_observed_at:`
- Outcome:
- `printer_visible_on_endpoint:` (yes/no)
- `evidence:` (path to screenshot or log excerpt, or short attestation line if human-only)
- `issues_encountered:` (free text, bullet list)
Pre-fill `imptune_url:` and `imptune_commit_sha:` by reading DEPLOYMENT.md. Do NOT attempt to call Intune/NinjaRMM APIs — delivery is human-driven in Task 2.
Built so far: ROLLOUT-RUN.md scaffold with source instance facts pre-filled.
Steps for the human operator:
Human-only steps (requires Intune/NinjaRMM tenant + real target endpoint — no CLI the agent owns can perform these):
1. Open the deployed ImpTune URL (`imptune_url:` from DEPLOYMENT.md) in a browser.
2. Upload the real printer driver (any real printer model in the MSP fleet — not the Phase 10 test printer unless that's still the target).
3. Create a printer in the form (name, IP, driver, model). Confirm port auto-fill works (UX-02 already validated, but spot-check).
4. Export the package from the printer detail page — download the `.intunewin`.
5. Push via ONE of the two channels:
- **Intune**: Upload `.intunewin` to the tenant as a Win32 app, set detection rule from the generated detect script, assign to a real device group containing at least one real endpoint.
- **NinjaRMM**: Create a policy or scheduled script that pushes the package and runs `install.ps1`, target at least one real endpoint.
6. Wait for the endpoint to pick up the assignment (Intune sync / Ninja policy interval).
7. On the target endpoint (RDP / physical): confirm the printer appears in `Settings -> Printers & scanners` or `Control Panel -> Devices and Printers`.
8. Capture evidence (screenshot preferred; log excerpt acceptable). Save under `.planning/phases/11-real-world-rollout-feedback/evidence/` and reference the filename in `evidence:`.
9. Fill in every blank field in ROLLOUT-RUN.md, including `printer_visible_on_endpoint:` and `issues_encountered:`.
10. Commit ROLLOUT-RUN.md (+ evidence files).
Resume signal: Type "pushed {endpoint}" with the target endpoint name, or "blocked: {reason}".
Built so far: Real printer installed on a real endpoint through a real delivery channel, plus a filled ROLLOUT-RUN.md.
Steps for the human operator:
-
Open ROLLOUT-RUN.md — no blank placeholder fields remain. 2.
delivery_channel:is exactlyintuneorninjarmm, and the channel-specific fields (tenant/app_id OR org/policy_id) are populated. 3.printer_visible_on_endpoint:isyes. 4.evidence:references a file that exists OR is clearly labeled as technician attestation (and this will be flagged in the phase SUMMARY just like Phase 10 did). 5. Re-confirm on the target endpoint that the printer still prints a test page (optional but strongly recommended — catches "installed but broken" gap).Resume signal: Type "verified" or list the gaps. MISSING — checkpoint is human-gated; verification is operator attestation captured via the resume-signal. Agent should confirm the referenced artifact file was updated (e.g. grep for the newly-filled field in the target doc) before accepting the resume signal. Human operator has performed the steps above, updated the referenced artifact, and replied with the resume signal.
<success_criteria> A package generated by the deployed ImpTune instance (not a local dev build) was pushed to a real endpoint via Intune or NinjaRMM and the printer is installed and visible on that endpoint, with the full chain recorded in ROLLOUT-RUN.md. </success_criteria>
After completion, create `.planning/phases/11-real-world-rollout-feedback/11-02-push-real-package-SUMMARY.md`