Prepare the managed credential implementation sprint

docs/roadmap/mvp.md

@@ -255,9 +255,27 @@ application-role releases in one source repository.
 - Debug output is not enabled by the MVP. Any later debug feature must either
   produce world-readable non-secret D&D diagnostics or identify and justify a
   narrower application contract before deployment.
-- Credential material will live beneath a restricted `secrets/` subdirectory
-  owned by `narratio:narratio`, with directories mode `0750` and files mode
-  `0640`. Ordinary configuration contains only credential reference names.
+- Credential material lives beneath the conventional
+  `/usr/local/etc/narratio/secrets` subdirectory owned by
+  `narratio:narratio`, with directory mode `0750` and file mode `0640`.
+  Membership in the `narratio` group is an explicit authorization to use the
+  suite's shared credentials. This deliberately differs from Narratio's
+  general single-user `0700` and `0600` recommendation while retaining no
+  world access. Ordinary configuration contains only credential reference
+  names.
+- The pipeline role exposes one empty-by-default credential mapping. Non-null
+  entries manage files named for valid environment variables; null explicitly
+  removes the named file; omitted names remain unmanaged. Credential values
+  are expected to come from encrypted inventory such as Ansible Vault and are
+  suppressed from task output.
+- Narratio's native ConfigKit secrets bootstrap owns loading these files and
+  process-environment precedence. The suite does not add a wrapper, shell
+  profile, service environment file, or parallel credential loader.
+- The suite coordinates Audita proposal and validation on the
+  `AUDITA_LLM_API_KEY` reference and selects `OPENROUTER_API_KEY` for
+  Notarius's production extraction profile. Narratio v2.1.0 resolves those
+  typed references and forwards only the selected credentials to the
+  corresponding subprocesses.
 - [Decision 0002](../decisions/0002-shared-readable-pipeline-filesystem-policy.md)
   records the complete rationale and boundary for this policy.
 
@@ -309,8 +327,9 @@ application-role releases in one source repository.
   cache beneath `/var/cache/notarius`. That FHS cache root is owned by the
   `narratio` account and group with mode `2775` and the suite's shared default
   ACL policy. Notarius v0.7.0 leaves cache-entry access to that deployment
-  policy. Chunk plans are reused automatically; checkpoints are recorded but
-  Narratio does not yet request their reuse.
+  policy. Chunk plans are reused automatically. Narratio v2.1.0 requests reuse
+  of compatible recorded checkpoints during ordinary extraction; forced
+  extraction omits checkpoint loading and refreshes the active chunk plan.
 - The standalone Notarius role exposes Notarius v0.7.0's native ConfigKit
   import list while remaining independent of D&D content. The pipeline role
   owns an imported `pipelines/dnd-session.yml` fragment containing its
@@ -378,7 +397,6 @@ The following areas require investigation and decisions before implementation:
 
 - The mechanism used to incorporate the independently developed pipeline role
   into collection releases
-- Secret injection and storage
 - Optional suite-level operator-selection and group-membership management
 - Upgrade, downgrade, and removal behavior
 - Collection bootstrap and end-to-end validation details beyond the locked