Tags: E-G-C/dude
Tags
Release v0.4.9: theme-agnostic, technology-independent design workflow The design workflow no longer assumes a theme or an implementation technology. It proposes and validates visual design against the target it is actually for: Functional Realism now checks each affordance against the capability envelope the target's own implementation owner declares, replacing the old fixed static Hugo/Docsy premise, and it routes implementation to whichever installed specialist owns that target instead of a built-in default. The design lane names and depends on no Strata, Hugo, Docsy, React, SCSS, or Microsoft Brand Central default. Strata is now an explicitly selected visual system rather than an ambient default. Its broad instructions artifact is removed, and its stylist agent and skill activate only on explicit Strata identity or existing Strata evidence: the Strata name, --strata-* flags, the pigment or spectrum palettes, or an existing Strata surface. Generic requests to theme an app, fix contrast, adjust focus rings, change the spacing scale, round corners, or drop shadows no longer pull Strata in. Strata's substantive rules, tokens, prompt, validator, and not-a-branding-service carve-out are unchanged. Both installed packs were refreshed transactionally, the now-false design -> strata sibling-warning example was dropped from the compose guidance and generated core rebuilt, and new pack-root independence regressions guard both packs against re-coupling. Delivered as Feature 032. Additive and corrective, with no breaking interface change.
Release v0.4.8: backlog lifecycle sync (030) + transactional pack ref… …resh (031) The committed backlog (.dude/backlog.md and .html) now refreshes at the three task-state mutation points, so it no longer goes stale and shows an empty board while features are still in flight. Ideas can now reach a terminal "resolved" state, which exposed and fixed a defect where recovery.mjs accepted only draft and defined ideas and broke inspect() once a resolved ledger existed. New "compose refresh <pack>" subcommand re-projects an installed pack from its current source in one all-or-restored transaction. Editing a pack source used to leave it stuck: remove refuses on the recorded-source digest guard, and add --force early-returns as already installed. Refresh proves installed-side authority, stages the current source through the normal add pipeline, and applies the destination difference. It deliberately skips the uninstall digest guard because it expects the source to have changed; add --force and remove semantics are unchanged. The Tester and Reviewer agents gain the YAGNI rule the other agents already carry, and the good-enough-delivery idea is resolved as already covered by the existing YAGNI, materially-ready, and escalation rules.
PreviousNext