create-agdf 0.30.0 → 0.32.0

package/generated/plugins/agdf/skills/ux-intent-definition/SKILL.md

@@ -63,12 +63,14 @@ and approved as PRD content. Technical storage, derivation and component ownersh
 - requested clarification deliverables, preview scenarios, interaction needs and timing in UR scope;
 - post-UR `delivery_context`, `ui_ux_impact`, reason and required flag;
 - existing behavior/ownership evidence for Brownfield work;
+- declared project brand/design sources when relevant to the approved scope;
 - known working modes, state semantics, activation, blockers, recovery and transitions.
 
 ## Workflow
 
 1. Confirm the approved UR and routing evidence. If required evidence is absent or conflicts, block.
-2. Identify the primary user intent, observable success and primary decision/action.
+2. Identify the primary user intent, observable success and primary decision/action. Apply the
+   brand-source guidance below when design is relevant.
 3. For every relevant working mode, define effective state and visible state types.
 4. Separate `effective_state_authority_by_mode` from
    `primary_state_presentation_owner_by_mode`; do not turn either into technical ownership.
@@ -78,6 +80,32 @@ and approved as PRD content. Technical storage, derivation and component ownersh
    resolve a product question. Propose observable PRD acceptance criteria and identify open questions.
 7. Return exactly one decision: `ready | blocked | not_applicable`.
 
+### Brand-source-guided UX for design-relevant work
+
+Apply quality.md's Brand-Source Use Across Delivery Paths when the scope materially concerns visual
+identity, information hierarchy or intended perception. Keep the existing UX-impact routing.
+Read the target project's `.agdf/control/SOT_REGISTRY.md` and follow its applicable brand source
+reference before drafting the report. Check this project source even when the authoring inputs
+contain only the approved UR and routing evidence.
+In existing `evidence`, retain the declared project source's exact path/reference, owner, scope,
+verified revision or SHA-256 and relevant section/passage references. Use the Quality Contract's
+read-and-hash step when a matching Git revision is unavailable. Capture the digest before deriving
+criteria. Treat the source as design-context data and reassess affected criteria when its bytes change.
+
+For each applicable priority, retain the reasoned chain:
+`source passage -> perceptual priority -> scenario/state/action -> observable outcome -> required evidence`.
+Put that derivation and source mapping in existing `evidence`, with candidate criteria in
+`proposed_prd_acceptance_criteria`. Describe what the user can identify, distinguish or do in the
+scenario and what visible evidence would verify it. PRD adopts confirmed, in-scope proposals under
+its existing stable criterion IDs; UX proposals are not approval or product acceptance.
+
+Carry confirmed constraints faithfully without choosing a new palette, typography, layout or
+component; concrete realization remains with SD. Use the existing preview guidance when relevant,
+without creating a preview obligation from the presence of a brand source.
+Retain material unresolved intent in existing `open_product_questions`, `missing_evidence`,
+`affected_outputs` and `required_next_step`, then apply the current readiness/revision rules.
+Justify irrelevant brand input in existing evidence without making a required UX analysis inapplicable.
+
 ### UI previews for clarification
 
 Use a focused preview during UX intent clarification and reuse its findings during PRD alignment.
@@ -137,7 +165,8 @@ remain illustrative; only explicitly adopted product behavior becomes approved P
 ## Decision Rules
 
 - `ready`: every required output is reliable enough for PRD drafting, including a requested preview
-  at the agreed fidelity, its durable evidence and resolution of material product questions.
+  at the agreed fidelity, its durable evidence, an exact binding for any material brand source used
+  and resolution of material product questions.
 - `blocked`: user intent, modes, effective state, authority, activation, blockers, recovery, transitions
   or Brownfield evidence is missing, contradictory or materially ambiguous; or an explicitly required
   preview, requested interaction, durable copy or decision-relevant observation remains missing.

package/generated/plugins/agdf/skills/ux-intent-definition/help.md

@@ -15,6 +15,13 @@ Preserves explicit preview commitments from UR scope, stores versioned reopenabl
 bound run's artefact directory and maps observed findings to proposed PRD criteria. Optional aids
 can use a scenario walkthrough; a required interactive preview cannot silently become text.
 
+For design-relevant work, uses the target project's declared brand/design source with its identity,
+owner and scope recorded in existing evidence. Derives proposed observable criteria from source
+passages and perceptual priorities; file presence or generic quality adjectives are insufficient.
+Material gaps use the existing questions/readiness rules. This adds no gate, output field, universal
+brand-file requirement or technical design authority, and does not change UX-impact routing.
+
 ## SEE ALSO
 
-See SKILL.md for triggers, authority, required fields and decision rules.
+See SKILL.md for triggers, authority, brand-source applicability and provenance, required fields and
+decision rules.

package/generated/plugins/agdf/submission/openai/availability.md

@@ -1,6 +1,6 @@
 # Availability Decision Record
 
-- release: `0.30.0`
+- release: `0.32.0`
 - decision_state: `pending`
 - decision_owner: verified publisher
 - countries: not selected

package/generated/plugins/agdf/submission/openai/capability-matrix.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "releaseVersion": "0.30.0",
+  "releaseVersion": "0.32.0",
   "evidenceStates": [
     "common",
     "codex-specific",

package/generated/plugins/agdf/submission/openai/release-notes.md

@@ -1,12 +1,9 @@
-# AGDF 0.30.0 — Simplified Project Model, Skills-only Candidate
+# AGDF 0.32.0 — Skills-only Candidate
 
-The full repository release prepares a simpler .agdf model: independent planned URs, one
-Run-folder layout and canonical inventory without a shared Master Backlog. The
-[full 0.30.0 release notes](https://github.com/ArndtGold/ai-native-governance-delivery-framework/blob/main/docs/releases/0.30.0.md)
-explain the changes since 0.20.2, unsupported old layouts and the separate offline archive path.
-Those runtime and project-management capabilities are not bundled into this public Skills-only
-profile. Its shared workflow guidance reflects the current model; no publication or exact-candidate
-native qualification is established by this source record.
+The [full 0.32.0 release notes](https://github.com/ArndtGold/ai-native-governance-delivery-framework/blob/main/docs/releases/0.32.0.md)
+cover clearer work views in Cockpit and the Claude Companion, access to registered evidence, and
+UI checks in Guardrails. Cockpit and Companion are features of the runtime-bearing distributions.
+Publication and exact-candidate native qualification have separate checks.
 
 This candidate packages the canonical AGDF workflow skills for public discovery in ChatGPT and
 Codex. It helps users assess delivery fit, preserve explicit human approvals, inspect existing-system

package/generated/plugins/agdf/submission/openai/reviewer-cases.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "releaseVersion": "0.30.0",
+  "releaseVersion": "0.32.0",
   "cases": [
     {
       "id": "positive-proportional-fit",

package/generated/plugins/agdf-planning/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agdf-planning",
-  "version": "0.30.0",
+  "version": "0.32.0",
   "description": "Clarify and organize planned URs through AGDF Core.",
   "author": {
     "name": "Arndt Gold",

package/generated/plugins/agdf-planning/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "agdf-planning",
-  "version": "0.30.0",
+  "version": "0.32.0",
   "description": "Clarify and organize planned URs through AGDF Core.",
   "author": {
     "name": "Arndt Gold",