Complete Promptkit adoption handoff and verification record

docs/roadmap/implementation.md

@@ -447,7 +447,7 @@ The broader upstream policy template remains separate future work.
 
 ## Stage 10: Verify The Integrated End State And Prepare The Handoff
 
-**Status: Pending.**
+**Status: Complete to the pre-release boundary.**
 
 1. Review the feature roadmap against implemented code and stage evidence.
    Confirm definition conformance, maintained profiles, retry inheritance,
@@ -480,9 +480,37 @@ Acceptance: the integrated implementation satisfies the feature roadmap, normal
 validation passes, and the release handoff is accurate. Actual source
 publication still follows the existing release policy and requires authorization.
 
+### Release-Note Handoff
+
+- This adoption merits a minor Scriptorium version under the release policy.
+  Version selection, the matching release note, release-candidate validation,
+  tag creation, and publication belong to release preparation and have not
+  occurred here.
+- Promptkit v0.11.0 selects the `/v2` catalogs. The removed
+  `deepseek-3-2`, `deepseek-4-flash`, and `deepseek-4-pro` profile IDs have no
+  aliases; migrate to an available catalog profile, a maintained Promptkit
+  name, or a complete application-owned profile.
+- Promptkit's built-in transient retry default is now two additional attempts.
+  This can increase latency, provider calls, and cost; application or request
+  `transient_retries: 0` selects a single attempt. Repair generations have
+  separate transient budgets.
+- Generation timeouts apply per attempt. CLI `--run-timeout` and HTTP
+  `run_timeout_seconds` opt into a whole-run deadline. A failed HTTP run whose
+  execution context ended reports `504 deadline_exceeded` or
+  `408 request_canceled`; live-context provider attempt failures retain 502.
+- CLI `--execution-report` files and HTTP `include_execution_report` expose
+  opt-in terminal reports. They are omitted without a terminal observation,
+  carry potentially sensitive identifiers, and do not replace result usage.
+  HTTP report bytes count toward the response limit; CLI report writes are
+  separate and nontransactional.
+- Distribution uses repository-hosted [attribution and dependency license
+  texts](../oss/attribution.md). Each future release note needs the
+  version-specific `LICENSE | ATTRIBUTION` footer described by the
+  [release procedure](../release.md); no historical release was changed.
+
 ## Open Questions
 
 None currently. The previously open distribution question is resolved by
 Stage 9's repository-hosted attribution/license texts and release footer.
-Its implementation remains pending; resolution of the decision does not imply
-that the notices or footer already exist.
+The materials and future-release instructions are in place. Actual release
+preparation and publication remain outside this implementation plan.