Record role documentation compatibility blocker
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Implementation Plan 0016: Deploy the D&D Pipeline to `pipeline-dnd`
|
||||
|
||||
Status: in_progress
|
||||
Status: blocked
|
||||
|
||||
Target executor: GPT-5.6-Terra
|
||||
|
||||
@@ -394,6 +394,16 @@ independent review.
|
||||
operational controller details, and Vault workflow/values remain Stage 3
|
||||
prerequisites. The acceptance session/audio selection remains a Stage 4
|
||||
prerequisite. No live deployment has begun.
|
||||
- Stage 2 consumer changes are prepared but not committed because required
|
||||
validation exposed a compatibility conflict in the reviewed dependency pins.
|
||||
Installation from the mixed public manifest succeeded, the playbook selected
|
||||
only `pipeline-dnd`, and syntax checking passed. With the required Ansible
|
||||
Core 2.21.3 toolchain, `ansible-doc -t role` resolves the pipeline, Seriatim,
|
||||
and Audita roles, but rejects the pinned `v0.1.0` Notarius, Scriptorium, and
|
||||
Narratio argument specifications because public options lack required
|
||||
`description` fields. The plan keeps those repositories read-only and
|
||||
requires reporting demonstrated pin conflicts rather than changing them, so
|
||||
Stage 2 and all dependent work are blocked pending an approved resolution.
|
||||
|
||||
## Open Questions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user