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
+The materials and future-release instructions are in place. Actual release
-that the notices or footer already exist.
+preparation and publication remain outside this implementation plan.

docs/roadmap/upgrade-kit.md

@@ -2,7 +2,10 @@
 
 ## Status And Intent
 
-Accepted feature direction, recorded on 2026-09-26; implementation is pending.
+Accepted feature direction, recorded on 2026-09-26. Implementation is complete
+to the pre-release boundary; version selection, release-candidate validation,
+and publication remain separate release preparation. The baseline descriptions
+below record the state when this roadmap was written, not current behavior.
 Upgrade directly from Promptkit v0.9.0 to v0.11.0, including the intervening
 v0.10.0 catalog transition. This document defines the desired end state and
 the changes from the current baseline. The [implementation plan](implementation.md)
@@ -259,11 +262,12 @@ boundaries.
   of the new public identities and context outcomes.
 - The licensing/distribution approach is resolved before upgraded binary
   distribution, and any required materials are included in the chosen workflow.
-- Affected contracts, examples, migration guidance, and release notes match
+- Affected current contracts, examples, and migration guidance match
   implemented behavior. Relevant tests remain offline and credential-free,
-  and normal development and release validation pass.
+  and normal development validation passes. Release-candidate validation and
+  the version-matched note remain release preparation.
 
-Concrete interface decisions and the remaining distribution question are recorded
+Concrete interface decisions and the selected distribution approach are recorded
-in the [implementation plan](implementation.md). They do not expand the product
+in the completed [implementation plan](implementation.md). They do not expand
-into conversations, follow-up messages, application-owned semantic retry loops,
+the product into conversations, follow-up messages, application-owned semantic
-prepared-handle coordination, or multi-step workflows.
+retry loops, prepared-handle coordination, or multi-step workflows.