diff --git a/.claude/settings.local.json b/.claude/settings.local.json
index 8b22210..490c095 100644
--- a/.claude/settings.local.json
+++ b/.claude/settings.local.json
@@ -1,8 +1,12 @@
 {
   "permissions": {
     "allow": [
+      "Bash(*)",
       "WebSearch",
-      "Bash(xargs wc:*)"
+      "Bash(xargs wc:*)",
+      "Bash(claude plugin *)",
+      "Bash(where claude *)",
+      "Bash(cmd /c \"claude plugin marketplace add JuliusBrussee/caveman && claude plugin install caveman@caveman\")"
     ]
   }
 }
diff --git a/.planning/ROADMAP.md b/.planning/ROADMAP.md
index 3f48119..bf1e1f9 100644
--- a/.planning/ROADMAP.md
+++ b/.planning/ROADMAP.md
@@ -109,7 +109,7 @@ Full details: [`milestones/v1.0-ROADMAP.md`](milestones/v1.0-ROADMAP.md)
 | 9. UX Tech Debt Closure      | 3/3 | Complete    | 2026-04-13 | 2026-04-13 |
 | 10. Real-World Runtime Validation | v1.1 | 3/3 | Complete    | 2026-04-13 |
 | 11. UI Enhancements               | 4/4 | Complete    | 2026-04-15 |            |
-| 15. UX Driver Upload Feedback Fix | v1.1 | 1/1 | Complete | 2026-04-16 |
+| 15. UX Driver Upload Feedback Fix | v1.1 | Complete    | 2026-04-16 | 2026-04-16 |
 
 ### Phase 12: i18n bugfixes — full translation coverage and browser language auto-detection
 
@@ -130,5 +130,5 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. After uploading a driver on /printers/new, the upload success feedback (driver name + confirmation) is visible on the page
   2. The DriverDesc dropdown still refreshes correctly via OOB swap (no regression)
-**Plans:** 1 plan
+**Plans:** 1/1 plans complete
   - [x] 15-01-PLAN.md — Fix hidden #driver-list div on /printers/new + smoke-test upload feedback visible (UX-01 integration gap)
diff --git a/.planning/STATE.md b/.planning/STATE.md
index cfc0792..265c014 100644
--- a/.planning/STATE.md
+++ b/.planning/STATE.md
@@ -1,3 +1,19 @@
+---
+gsd_state_version: 1.0
+milestone: v1.1
+milestone_name: Hardening & Validation
+current_plan: 1
+status: completed
+stopped_at: Completed 15-ux-driver-upload-feedback-fix/15-01-PLAN.md
+last_updated: "2026-04-16T14:37:17.811Z"
+last_activity: 2026-04-16
+progress:
+  total_phases: 6
+  completed_phases: 6
+  total_plans: 21
+  completed_plans: 21
+---
+
 ---
 gsd_state_version: 1.0
 milestone: v1.1
diff --git a/.planning/phases/15-ux-driver-upload-feedback-fix/15-VERIFICATION.md b/.planning/phases/15-ux-driver-upload-feedback-fix/15-VERIFICATION.md
new file mode 100644
index 0000000..ceed886
--- /dev/null
+++ b/.planning/phases/15-ux-driver-upload-feedback-fix/15-VERIFICATION.md
@@ -0,0 +1,111 @@
+---
+phase: 15-ux-driver-upload-feedback-fix
+verified: 2026-04-16T00:00:00Z
+status: passed
+score: 3/3 must-haves verified
+gaps: []
+human_verification:
+  - test: "Upload a real driver ZIP on /printers/new in a browser"
+    expected: "Driver name and confirmation table appear inline below the upload form immediately after upload, without a page reload"
+    why_human: "HTMX DOM swap visibility cannot be asserted programmatically — requires a live browser session to confirm the rendered result is visible to the user"
+---
+
+# Phase 15: UX Driver Upload Feedback Fix — Verification Report
+
+**Phase Goal:** Make the driver upload success feedback visible on /printers/new so technicians see confirmation after uploading a driver.
+**Verified:** 2026-04-16
+**Status:** PASSED
+**Re-verification:** No — initial verification
+
+---
+
+## Goal Achievement
+
+### Observable Truths
+
+| # | Truth | Status | Evidence |
+|---|-------|--------|----------|
+| 1 | GET /printers/new renders `#driver-list` div with no `style="display:none"` attribute | VERIFIED | `printers_new.html` line 98: `<div id="driver-list"></div>` — no style attribute present; `grep display:none` returns no matches; `test_printers_new_driver_list_visible` passes |
+| 2 | After uploading a driver with `caller=printer_form`, the response fragment contains the driver name (upload confirmation visible) | VERIFIED | `driver_upload_with_oob.html` includes `driver_list.html` which renders `item.driver.original_filename` and `item.names`; upload handler at `drivers.py:113` branches on `caller == "printer_form"` and returns the OOB template with `parsed` and `driver_data`; `test_upload_feedback_visible_on_printers_new` asserts `"Test LaserJet Pro" in resp.text` and passes |
+| 3 | OOB select (`hx-swap-oob="true"`) still present in upload response (no regression) | VERIFIED | `driver_upload_with_oob.html` line 3: `<select name="driver_id" id="printer-form-driver-select" hx-swap-oob="true">`; `test_upload_feedback_visible_on_printers_new` asserts `hx-swap-oob="true" in resp.text` and passes |
+
+**Score:** 3/3 truths verified
+
+---
+
+### Required Artifacts
+
+| Artifact | Expected | Status | Details |
+|----------|----------|--------|---------|
+| `imptune/templates/printers_new.html` | Printer new page template with visible `#driver-list` anchor | VERIFIED | File exists, line 98 reads `<div id="driver-list"></div>` — style attribute removed; `id="driver-list"` present |
+| `tests/test_printer_form.py` | Smoke tests for driver-list visibility and upload feedback | VERIFIED | File exists, substantive (139 lines), exports `test_printers_new_driver_list_visible` and `test_upload_feedback_visible_on_printers_new` — both functions confirmed at lines 84 and 109 |
+
+---
+
+### Key Link Verification
+
+| From | To | Via | Status | Details |
+|------|----|-----|--------|---------|
+| `imptune/templates/printers_new.html` | `partials/driver_upload_with_oob.html` | HTMX `hx-target="#driver-list"` outerHTML swap | VERIFIED | `printers_new.html` lines 87–90: `hx-post="/drivers/upload" hx-target="#driver-list" hx-swap="outerHTML"`; `id="driver-list"` div present at line 98 without `style="display:none"` |
+| `POST /drivers/upload?caller=printer_form` | `driver_upload_with_oob.html` primary fragment | `caller == "printer_form"` sentinel in upload handler | VERIFIED | `imptune/api/drivers.py` line 113: `if caller == "printer_form":` returns `TemplateResponse("partials/driver_upload_with_oob.html", ...)` with `driver_data`, `new_driver_id`, and `parsed` in context |
+
+---
+
+### Requirements Coverage
+
+| Requirement | Source Plan | Description | Status | Evidence |
+|-------------|-------------|-------------|--------|----------|
+| UX-01 | 15-01-PLAN.md | After a new driver is uploaded on the printer form, the DriverDesc dropdown refreshes automatically (no manual page reload) — verified live in browser | SATISFIED (integration gap closure) | The OOB wiring was implemented in Phase 9; Phase 15 closes the integration gap where the outerHTML swap target `#driver-list` was hidden, making the confirmation invisible despite the server response being correct. Both `test_printers_new_driver_list_visible` and `test_upload_feedback_visible_on_printers_new` pass. The automated portion of UX-01 is satisfied; live browser confirmation is flagged under Human Verification. |
+
+**Note on requirement traceability:** REQUIREMENTS.md maps UX-01 to Phase 9 (the original OOB implementation). Phase 15 claims UX-01 as an integration gap closure. ROADMAP.md explicitly documents this at Phase 15: "Requirements: UX-01 (integration gap closure)". There is no conflict — Phase 9 delivered the server-side wiring; Phase 15 fixes the DOM visibility gap that prevented the feature from working end-to-end.
+
+No orphaned requirements: REQUIREMENTS.md does not map any additional IDs to Phase 15 beyond UX-01.
+
+---
+
+### Anti-Patterns Found
+
+| File | Line | Pattern | Severity | Impact |
+|------|------|---------|----------|--------|
+| None found | — | — | — | — |
+
+No `display:none`, `TODO`, `FIXME`, `PLACEHOLDER`, stub returns, or empty handlers found in any modified file.
+
+The three `placeholder="..."` occurrences in `printers_new.html` are standard HTML input placeholder attributes — not anti-patterns.
+
+---
+
+### Human Verification Required
+
+#### 1. Live Browser Upload Confirmation
+
+**Test:** Open `/printers/new` in a browser, upload a valid driver ZIP file, and observe the result without reloading the page.
+**Expected:** The driver name and a confirmation table appear inline below the upload form immediately after the file is submitted. The DriverDesc dropdown also updates to include the new driver.
+**Why human:** HTMX DOM swaps and rendered visibility require a live browser session. The server response fragment is correct (verified by test), but whether the replaced `#driver-list` content is actually visible on screen can only be confirmed by a human.
+
+---
+
+### Test Suite Results
+
+Full suite (excluding e2e): **124 passed, 46 warnings** in 4.14s
+
+| Test | Result |
+|------|--------|
+| `test_printers_new_driver_list_visible` | PASSED |
+| `test_upload_feedback_visible_on_printers_new` | PASSED |
+| All pre-existing tests in `test_printer_form.py` | PASSED |
+| All tests in `test_driver_upload.py` (OOB regression) | PASSED |
+| Full suite `pytest tests/ -x -q --ignore=tests/e2e` | 124/124 PASSED |
+
+---
+
+### Gaps Summary
+
+No gaps. All three observable truths are verified. The single-line template change (`style="display:none"` removed from `#driver-list` in `printers_new.html` line 98) is confirmed. Both new test functions exist and pass. The OOB select regression guard passes. The full test suite is green.
+
+One item is flagged for optional human confirmation (live browser upload flow) — this does not block phase completion as it verifies UX feel, not correctness.
+
+---
+
+_Verified: 2026-04-16_
+_Verifier: Claude (gsd-verifier)_
diff --git a/README.md b/README.md
index bf47bc2..0832718 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,3 @@
 # ImpTune
 
 
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
-* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.arescom.fr/infra_rsx/imptune.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-* [Set up project integrations](https://git.arescom.fr/infra_rsx/imptune/-/settings/integrations)
-
-## Collaborate with your team
-
-* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
-* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
-* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
-* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
-* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
-* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
-* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
-* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
-* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
diff --git a/tests/__pycache__/test_printer_form.cpython-314-pytest-9.0.3.pyc b/tests/__pycache__/test_printer_form.cpython-314-pytest-9.0.3.pyc
index 3c8a25f..ff4ad38 100644
Binary files a/tests/__pycache__/test_printer_form.cpython-314-pytest-9.0.3.pyc and b/tests/__pycache__/test_printer_form.cpython-314-pytest-9.0.3.pyc differ