Repository navigation
shruggie-brandbuilder 3.1.1
shruggie-brandbuilder v3.1.1
Skill version: 3.1.1
Canon version: 2.1.0
Interface Canon version: 1.0.1
Component recipe version: 1.1.0
Web/React adapter version: 1.1.0
egui adapter version: 1.0.2
WordPress adapter version: 1.0.0
Version policy: 2.3.1
Existing kits need migration: no required identity migration. Regenerate and repin the seven changed brand packages to adopt their approved message roles and corrected Next.js and WordPress description behavior. Existing packages remain immutable recovery inputs. The hosted site adopts the S073 portfolio and References layout. Brand Canon 2.1.0, approved geometry, palettes, fonts, social compositions and adapter APIs remain unchanged. Ten owned brand archives are release-authorized; three client kits remain hosted candidates.
Governed release impact
No approved identity redesign is included.
| Surface | Classification | Guidance |
|---|---|---|
| Identity | unaffected | Approved logo geometry and source masters remain unchanged. Seven edited brands receive patch package versions for messaging; identity remains governed by their existing continuity records. |
| Palette | unaffected | Existing palette values and WCAG 2.1 AA rules remain unchanged. |
| Typography | unaffected | Approved local font families, faces, and licenses remain unchanged. |
| Platform Assets | optional | Regenerate and repin to adopt exact approved messaging in generated packages. Approved logo geometry, platform icon layouts and social-image compositions remain unchanged. |
| Web React | unaffected | Web and React adapter APIs and interface token behavior remain unchanged. |
| Egui | unaffected | The egui adapter API and output semantics remain unchanged. |
| Wordpress | optional | Regenerate WordPress starters to adopt exact approved site descriptions and omit the hero description when the canonical site-metadata role is absent or unresolved. WordPress adapter 1.0.0 retains its public API. |
| Documentation | required | Publish seven brands' exact approved message decisions, corrected portfolio heading and complete card-title layout, and all 68 labeled References entries. Brand Canon 2.1.0 and existing adapter APIs remain unchanged. |
| Recovery | required | Repinning BrandBuilder 3.1.1 requires exact new package IDs and checksums. The site hosts thirteen verified brands; ten owned archives join the skill and portable distribution, while three client kits remain hosted candidates. Previously published packages remain immutable recovery inputs. |
Release changes
Changed
- Record seven brands' exact owner-approved messaging decisions, including four short descriptions for portfolio cards and formal brand outputs. Preserve unresolved optional roles and independent social-image wording.
- Group the home page portfolio introduction beneath its heading, fit complete card titles and affiliation markers within the card, and present all 68 References entries as compact labeled fields (S073).
- Pin patched WordPress validation fixture dependencies so its documented audit gate remains green.
- Consolidate pending Python and site dependency updates, align Fumadocs Core and UI with MDX, and pin the patched source-map-js transitive package.
- Assign patch versions to seven edited brand packages and BrandBuilder so the approved copy and corrected generated output receive immutable package identities.
Fixed
- Stop generated Next.js and WordPress starters from publishing legacy descriptors when a canonical short description is absent or unresolved. Retain meaningful title-only alternative text.
Decisions
- 2026-10-27: Apply only the owner's recorded short-description decisions and defer all other optional copy under the no-questions cleanup direction. The next release slice must assign patch versions to the changed brand packages and compiler together with dated release history and impact metadata. S072 does not tag or publish a release.
- 2026-10-28 (S074): Publish the merged S072 and S073 changes as BrandBuilder 3.1.1 with seven brand patch versions. Retain Brand Canon 2.1.0 and adapter versions because their contracts are compatible; deploy the site through the existing CI-built version-tag release workflow.