Merge TASK-051 (per-route hooks via http_resource::add_hook) into feature/v2.0

Author: etr

specs/tasks/M5-routing-lifecycle/TASK-051.md

@@ -8,12 +8,12 @@
 Add a per-resource scope to the hook bus so a hook can be attached to one route instead of every request. Required to give #273-style early-413 a per-route flavor (different size caps per endpoint), to put per-route timing in `response_sent`, etc.
 
 **Action Items:**
-- [ ] Add `http_resource::add_hook(hook_phase, ...)` overloads — but ONLY for phases that fire after route resolution: `before_handler`, `handler_exception`, `after_handler`, `response_sent`, `request_completed`. Passing any earlier phase throws `std::invalid_argument` with a message naming the phase and the constraint.
-- [ ] Add per-resource storage on `http_resource`: `std::array<std::vector<std::function<...>>, hook_phase::count_>` (most slots unused per the constraint above, but the array shape simplifies indexed access) + `std::array<std::atomic<bool>, hook_phase::count_> any_hooks_` + `std::shared_mutex hook_table_mutex_`. Memory footprint is a fixed-size array of empty vectors; revisit if TASK-039's `sizeof(http_resource)` budget is tight (a single `std::vector` of `std::pair<hook_phase, function>` is the fallback if so).
-- [ ] In `webserver_impl::dispatch_resource_handler`, fire the per-route hook chain at each of the five applicable phases AFTER the server-wide chain at that phase, BEFORE checking for a server-wide short-circuit's result. (If server-wide short-circuited, do NOT run per-route — the response is already fixed.)
-- [ ] In `webserver_impl::request_completed`, locate the resource that handled the request (carried on `modded_request` as a `weak_ptr<http_resource>` populated at dispatch time) and fire its `request_completed` per-route chain after the server-wide one. If the resource was unregistered between dispatch and completion, the `lock()` returns null and the per-route chain is skipped.
-- [ ] Lock order: `route_table_mutex_` (already held by dispatch) → resource's `hook_table_mutex_` → server-wide `hook_table_mutex_`. Documented in `specs/architecture/05-cross-cutting.md` §5.6 and verified by TSan.
-- [ ] `hook_handle` returned by `http_resource::add_hook` carries the same RAII semantics as the server-wide handle — destruction removes the registration. The handle holds a `weak_ptr<http_resource>`; if the resource is destroyed before the handle, `remove()` is a no-op.
+- [x] Add `http_resource::add_hook(hook_phase, ...)` overloads — but ONLY for phases that fire after route resolution: `before_handler`, `handler_exception`, `after_handler`, `response_sent`, `request_completed`. Passing any earlier phase throws `std::invalid_argument` with a message naming the phase and the constraint.
+- [x] Add per-resource storage on `http_resource`: `std::array<std::vector<std::function<...>>, hook_phase::count_>` (most slots unused per the constraint above, but the array shape simplifies indexed access) + `std::array<std::atomic<bool>, hook_phase::count_> any_hooks_` + `std::shared_mutex hook_table_mutex_`. Memory footprint is a fixed-size array of empty vectors; revisit if TASK-039's `sizeof(http_resource)` budget is tight (a single `std::vector` of `std::pair<hook_phase, function>` is the fallback if so).
+- [x] In `webserver_impl::dispatch_resource_handler`, fire the per-route hook chain at each of the five applicable phases AFTER the server-wide chain at that phase, BEFORE checking for a server-wide short-circuit's result. (If server-wide short-circuited, do NOT run per-route — the response is already fixed.)
+- [x] In `webserver_impl::request_completed`, locate the resource that handled the request (carried on `modded_request` as a `weak_ptr<http_resource>` populated at dispatch time) and fire its `request_completed` per-route chain after the server-wide one. If the resource was unregistered between dispatch and completion, the `lock()` returns null and the per-route chain is skipped.
+- [x] Lock order: `route_table_mutex_` (already held by dispatch) → resource's `hook_table_mutex_` → server-wide `hook_table_mutex_`. Documented in `specs/architecture/05-cross-cutting.md` §5.6 and verified by TSan.
+- [x] `hook_handle` returned by `http_resource::add_hook` carries the same RAII semantics as the server-wide handle — destruction removes the registration. The handle holds a `weak_ptr<http_resource>`; if the resource is destroyed before the handle, `remove()` is a no-op.
 
 **Dependencies:**
 - Blocked by: TASK-045, TASK-048, TASK-049, TASK-050
@@ -31,4 +31,4 @@ Add a per-resource scope to the hook bus so a hook can be attached to one route
 **Related Requirements:** PRD-HOOK-REQ-002, PRD-HOOK-REQ-003, PRD-HOOK-REQ-004, PRD-HOOK-REQ-006, PRD-HOOK-REQ-007
 **Related Decisions:** DR-012, §4.10, §5.6
 
-**Status:** Not Started
+**Status:** Done

specs/tasks/_index.md

@@ -133,7 +133,7 @@ Nominally: **13 sequential tasks**, each S–XL. Most other tasks parallelize of
 | TASK-048 | Fire `route_resolved` and `before_handler`; wire 404/405/auth aliases | M5 | Done | TASK-045, TASK-027, TASK-031 |
 | TASK-049 | Fire `handler_exception`; wire `internal_error_handler` alias | M5 | Done | TASK-045, TASK-031 |
 | TASK-050 | Fire `after_handler` (post-handler short-circuit), `response_sent`, `request_completed`; wire `log_access` alias | M5 | Done | TASK-045 |
-| TASK-051 | Per-route hooks (`http_resource::add_hook`) | M5 | Not Started | TASK-045, TASK-048, TASK-049, TASK-050 |
+| TASK-051 | Per-route hooks (`http_resource::add_hook`) | M5 | Done | TASK-045, TASK-048, TASK-049, TASK-050 |
 | TASK-052 | Hook bus documentation, examples, benchmark, stress-test extension (touches back into TASK-040/041/042/043) | M5 | Not Started | TASK-045, TASK-046, TASK-047, TASK-048, TASK-049, TASK-050, TASK-051 |
 | TASK-037 | CI test for build-flag invariance | M6 | Done | TASK-034 |
 | TASK-038 | Sanitizer-clean tests for `http_response` move semantics | M6 | Done | TASK-009, TASK-036 |