Changelog

0.5.0(2026-09-29)

A breaking release: the project is now SweetUI. Every product, module, and command changes name, and every item declares the 0.5.0 floor. The repository moved to github.com/mangobyte-dev/sweetui; GitHub redirects the old URL. The website moves to https://sweetui.dev.

Changed

RegistryTheme, registryTheme(_:), registryItem(_:), and every other registry prefixed API keep their names.

Migrating an app

1. Package: .package(url: "https://github.com/mangobyte-dev/sweetui.git", .upToNextMinor(from: "0.5.0")) and .product(name: "SweetUIFoundations", package: "sweetui"), plus .product(name: "SweetUIDesignSurface", package: "sweetui") if the app links the design surface. In an Xcode project, remove the old package and add the new URL with the same products.

2. Sources: replace SwiftUIRegistry with SweetUI in every import.

3. Receipts: the tool reads only .sweetui/ and rejects a receipt that names another registry. In each install destination run:

   mv .swiftui-registry .sweetui
   sed -i '' -e 's/SwiftUIRegistry/SweetUI/g' -e 's/swiftui-ui-registry/sweetui/g' .sweetui/receipt.json

   Step 2 changed each installed file, so info reports it modified; install <item> --update merges it back to up-to-date.

4. Theme file: preset apply reads the header // sweetui preset <code>. Rename the old // swiftui-registry preset header, or pass --force.

5. Tool: brew uninstall swiftui-registry, then brew install mangobyte-dev/tap/sweetui. Register the MCP server as sweetui mcp. The old cache MAY be deleted.

0.4.0(2026-09-19)

A minor release, source compatible with 0.3.x. brew upgrade swiftui-registry installs the tool. A package pinned .upToNextMinor(from: "0.3.0") resolves it, and every item keeps the 0.3.0 floor, since none needs anything newer.

Three things drove it. A Point-Free audit in two passes (docs/point-free-audit.md) hardened the engine with no schema change. A build of a shop front from the released tool, read by hand, found seven problems an agent meets. A measured study then had an agent build four small apps five times each, changed the registry one thing at a time, and kept only what lowered the count (docs/case-studies.md).

Added

• Case studies (docs/case-studies.md, also on the website): the four apps, their screenshots, the items they used, and what the measurement found.
• validated-input 0.1.0: a text field with a floating label, a rounded border that follows focus and validity, and rules checked while typing and again on blur. Rules are required, email, phone, custom, and the statics password, matching, numberRange, internationalPhone, and pattern; the first failing rule's message shows under the field, is the accessibility hint, and is announced. A validity binding reports every change so a form can gate its submit. Based on the owner's earlier enum-driven text field.
• A fifth generator, swiftui-registry generate usage-checks, writes UsageSnippetChecks.swift: one View per installable item that compiles the item's usage snippet, so a snippet naming an undeclared symbol fails the Showcase build instead of shipping. Symbols a snippet leaves to the adopter are stand-ins in the hand-written UsageSnippetPlaceholders.swift.
• describe lists Signatures:: every public initializer, function, static member, and enum of the item's sources, one line each, prefixed with the owning type, with labels, types, defaults, and enum cases. The JSON and MCP describe_item payloads carry them as signatures.

Changed

• Thirteen items gained the words a shop developer searches first: product, cart, price, checkout, rating, and their neighbors now resolve to item, badge, button, field, empty, metric-card, and the rest. Search itself is unchanged: every term must still match.

• Fourteen more items gained the words a chat, settings, or finance developer searches first: unread and counter reach badge; send, submit, and refresh-button reach button; composer reaches input-group; email, phone, and password reach input and field; sign-out and logout reach alert-dialog; notifications reaches settings-section; filter reaches accordion and checkbox; range reaches slider; total reaches table and metric-card; profile-header reaches avatar; refreshed reaches toast.

• field 0.1.2: Field also takes its error as a String?, so a message computed at runtime no longer needs wrapping in a LocalizedStringResource. The resource initializer stays preferred.

• attachment 0.1.2 and item 0.2.2: a bare trailing closure on AttachmentRow or ItemRow now resolves to the content initializer instead of an ambiguity error; the actions-only and accessory-only initializers are disfavored.

• signup-form 0.1.2: SignUpForm takes isSubmitEnabled (default true) and disables its submit button and return-key submit while it is false.

• Installer.FileStatus.status and InstalledInventory.File.status are now enums (PlanFileStatus, UpdateFileStatus, InventoryFileStatus) instead of String. JSON and CLI text output are byte-identical; Swift code that links RegistryKit directly and compares .status against a string literal needs to compare against the matching case instead.

• RegistryKit's FileSystem and RegistrySource are structs of closures, the shape of its other six dependencies, instead of protocols. LocalFileSystem() and LocalRegistrySource() are FileSystem.local and RegistrySource.local; .unimplemented is each one's test default. write(_:to:) and repositoryRoot(override:refresh:) stay as methods, so call sites through @Dependency do not change; a type that conformed to either protocol now builds a value instead. The CLI and MCP output are unchanged.

• skeleton 0.2.2: the doc comment names what redaction does not cover. An effect the wrapped content starts itself (task, onAppear, a request) still runs; gate it on the same flag. No visible change, no recapture.

• The tuning panel's import sheet owns its draft and its failure state; a failed paste no longer outlives the sheet.

Fixed

• Five usage snippets did not compile as printed. field read $name and emailError without declaring them; auth-form, signup-form, message-scroller, and settings-section bound state they never declared. Each now declares the state it assumes. toast's snippet shows message: and carousel's names its placeholder collection.
• swiftui-registry search ... --format names printed nothing on zero matches. It now says No item matches ... on stderr and still exits 0.
• In a test, an un-overridden registryFileSystem or registrySource reached the real disk and the release snapshot. Both now fail at the boundary: the file system's throwing members throw, its queries report an issue, and the source throws. RegistryKit declares IssueReporting through xctest-dynamic-overlay, the identity swift-sharing already resolves; RegistryKitTests declares CustomDump for line diffs on multi-field assertions and generated text. Neither changes Package.resolved.

Known limitations

• Unchanged from 0.3.1: toggle-group's toggles report no frame inside a native ControlGroup, and the same six Showcase visual references fail on the pinned simulator by 4.1 to 5.5 percent (activity, auth, command, finance, nutrition, settings), on an unchanged tree.
• A search for quantity matches nothing. The native Stepper is the answer, and an item that only renames it is out of scope by the value gate.

0.3.1

A patch release: every change is source compatible. brew upgrade swiftui-registry installs the tool. A package pinned .upToNextMinor(from: "0.3.0") resolves it, and every item keeps the 0.3.0 floor, since none needs anything newer.

Added

• Recipes are selectable. A recipe's usage snippet ends its root with .registryItem("<name>"); copy it, and the design surface selects the recipe. A recipe whose snippet uses registry items declares them, so the panel scopes to the tokens they read. menubar carries no tag: its root is a Scene, and the tag is a View modifier.
• RegistryItemReport.ancestors: the tagged roots an item sits inside, outermost first. ItemSelection.chain(reports:at:) reads it.

Changed

• A child that fills its parent exactly is picked before the parent. Before, equal areas resolved by name, so an attachment won over the item inside it.
• The panel shows only what an export reproduces. A value that arrives off its slider grid (an import, a hand edited registry-tokens.json) renders and exports at the nearest step, and a custom color at 8 bits a channel.
• The System accent tints nothing while tuning. A consumer's export carries no accent for System, so its native controls keep their own colors; the tuner now shows the same.

Fixed

• swiftui-registry preset apply wrote a theme file that did not compile for a code with a font design, a surface step, a chart palette, or a color pair. Those arguments now follow metrics:, the order RegistryTheme.init declares. The Swift that preset decode prints, the MCP tools, and the website's Create page share the fix.
• Copy Swift rounded an off-grid number or a custom color to three decimals, which changed pixels. It now prints the fewest decimals that read back. The theme file prints each color channel the same way.
• Neither export wrote surfaceOpacity, so registrySurface(level:) drew a different elevated surface in the consumer. Both write it when it leaves 0.055.

Known limitations

• A native ControlGroup never places its toggles, so toggle-group's toggles report no frame and Select picks the group. registryToggleGroup(_:)'s variant has no visible effect on iOS 27.
• Six Showcase visual references fail on the pinned simulator by 4.0 to 5.5 percent against the 1.5 percent tolerance (activity, auth, command, finance, nutrition, settings). They failed before this release too, on an unchanged tree.

0.3.0(public beta)

The design surface tunes a running app on the device. It ships as a second package product. Install or upgrade: brew install mangobyte-dev/tap/swiftui-registry or brew upgrade swiftui-registry.

Added

• SwiftUIRegistryDesignSurface. Add the product, import SwiftUIRegistryDesignSurface, apply designSurface() inside registryTheme(_:). A debug build gains a draggable Tune button. A floating, movable, resizable panel opens in the tool's own window. The window covers the whole app, live underneath on every tab, sheet, and cover. A release build returns the content unchanged. Tokens persist as registry-tokens.json in the app's Documents directory. Export them as a preset code any registry tool applies, or as Swift to paste.

• Tap to select. Select arms the next tap; the panel scopes to the tokens reaching the tapped item. Every tagged item on screen is outlined with its name and listed under On this screen. ItemSelection.chain names every item under the pick, innermost first. A host can offer the row around a button too. A pick on nothing clears the selection.

• Host tokens. Conform the app's token value to TokenDocument: a shipped value, a file name, pages of .number, .choice, and .color knobs, and apply(). Pass it to designSurface(tokens:). The panel gains an App tokens section that writes back to the app.

• Per item knobs. Register numeric knobs with designSurface(knobs:) and ItemKnob; read one with registryKnob(_:_:default:). They persist beside the tokens in design-knobs.json; only a moved value is written.

• The host hooks overload designSurface(enabled:tunesRegistryTheme:knobs:itemTitle:page:panelEnvironment:panel:), for an app that paints registry items from its own tokens. It compiles in every configuration.

  Parameter	Effect
  enabled	the app's own switch
  tunesRegistryTheme: false	drops the panel's theme sections
  panel	adds the app's sections
  page	pushes the app's page for a picked item
  panelEnvironment	wraps the panel's stack
  itemTitle	names rows and outlines

• Foundations gained registryItem(_:) and registryScreen(_:), the tags the surface selects and names screens by. It also gained the surface reporter and per item knobs in the environment. All are inert without a surface.

• A fourth generator, swiftui-registry generate item-tokens, writes the item to token map that scopes the panel. CI checks it for drift with the other outputs.

• CHANGELOG.md, a repository layout table in CONTRIBUTING.md, and docs/RELEASE-CHECKLIST.md, the list a release closes line by line.

Changed

• The tuning panel moved from the Showcase into the product, which the Showcase now consumes. It is a floating card in the tool's own window, not a sheet or inspector column. A drag bar moves it, a corner grip resizes it, a chevron collapses it. It can hang off the leading, trailing, and bottom edges; its grab strip stays inside the safe area, and it never goes above the top. On iPad, a drag against the trailing edge snaps it into a full height column. Its frame is remembered per size class and re clamped on rotation.
• The tool's chrome uses fixed system values, never the tuned theme: Tune button, card, selection ring, outlines, guides. Its motion is off under Reduce Motion.
• Every installable item declares the 0.3.0 foundations floor, because every one applies registryItem(_:). The installer prints from 0.3.0 up to the next minor version.
• swift-sharing is pinned to 2.9.x (from 2.9.1, below 2.10.0) with no traits. A consumer that already resolves xctest-dynamic-overlay is not forced onto a newer major.
• Planning, research, and run logs left the repository. It holds only what an adopter needs.

Fixed

• The tool no longer advertises an older Homebrew tag as an update; the notice needs a tag newer than the running tool.

• A tap on a List row under the card pushes again. The key window follows the text field that takes focus: a field in the app takes the keyboard, a field in the panel takes it back. Before, the key window switched during hit testing, which cancelled the touch.

• The collapse control has its own accessibility frame; the drag runs over the whole bar as a simultaneous gesture.

• The card is clamped into the window's safe area. Its strip neither sits under the status bar nor stops short of it.

• Edge cases:

  Case	Behavior
  non positive step, or shipped value outside its range	knob stays usable, logged
  token file that fails to decode (hand edited, newer version)	shipped values stay, logged once, not rewritten until a knob moves
  choice knob whose options no longer list its value	value kept
  empty item or screen name	tags nothing
  empty host title	falls back to the item's name
  equal frames	ties resolve by name
  item scrolled off the screen	not listed as on it

• Foundations compiles on macOS again after Color(uiColor:) crept into the selection ring. An unused anchor preference left the public API before it shipped.

Known limitations

• Two visual references, auth-light and nutrition-light, are stale after the tuning strip change: 2.70 and 1.54 percent against the 1.5 percent tolerance. Both are recaptured and await the owner's copy into ReferenceImages/. Until then those two Showcase UI tests fail (docs/visual-testing.md).
• The iPad simulator sometimes never reports idle after keyboard input. The UI suite passes -disable-animations on that destination. One test records a measured skip instead of a failure (docs/visual-testing.md).
• The tool's window installs over the first connected scene. A second window of the same app on iPad is not covered.
• Items installed from 0.1.0 or 0.2.0 carry no registryItem(_:) tag. Select and the outlines find nothing in them until swiftui-registry install <item> --update.
• The Showcase is portrait only on iPhone. Card rotation runs on the iPad destination and in the host apps.

0.2.0(2026-09-07)

The Stage 7 release. The same brew install mangobyte-dev/tap/swiftui-registry or brew upgrade swiftui-registry applies.

Added

• 16 items, growing the catalog from 57 to 73:
  • 6 chat and feedback components: attachment, bubble, marker, message, message-scroller, toast.
  • 7 recipes: carousel, chart-tooltip, date-picker, input-otp, menubar, sheet, typography.
  • 3 blocks: dashboard, signup-form, questionnaire.
• describe <item> prints metadata, usage snippet, accessibility contract, install order, package requirement, and files, with --source and --format json. info --destination <dir> reports every owned file as up to date, modified, or missing through the receipt.
• Preset code format version b. It appends to the version a fields and the custom accent block. The new fields: font design, a surface step that drives a four level elevation ladder, a chart palette. Optional light and dark pairs cover background, foreground, and secondary foreground. A code stays a while nothing appended leaves its default. Every existing code still decodes to the same theme.
• The SwiftUIRegistryFoundations 0.2.0 API, all defaulted so existing initializers compile:
  • fontDesign, surfaceOpacity, surfaceStep, chartPalette, background, foreground, secondaryForeground on RegistryTheme.
  • The mango preset, the sample design system (docs/mango.md).
  • RegistrySurfaceLevel with registrySurface(level:).
• Three agent skills under Skills/ (consuming, theming, authoring), mirrored to ~/.claude/skills/.
• iPad Pro 13 inch captures of every item, light and dark; the website shows both idioms.

Changed

• button, checkbox, accordion, and breadcrumb keep the iPadOS pointer effect. The sidebar recipe adds the sidebarAdaptable tab view.
• chart reads the chart palette and declares the 0.2.0 foundations floor. Every other item kept 0.1.0 at this release.

0.1.0(2026-09-06)

The first published contract.

Added

• 57 source owned items (31 components, 8 blocks, 18 recipes), the SwiftUIRegistryFoundations theme package, and the swiftui-registry tool.
• The tool installs items with receipt backed three way updates. It searches and validates the catalog, reads and writes preset codes, and serves every operation over MCP. It generates the catalog, the Showcase manifest, and the website data. Outside a clone it fetches this tag's registry snapshot on first use.
• The release workflow attaches swiftui-registry-macos-universal.tar.gz (arm64 and x86_64) plus its .sha256 for the Homebrew tap.
• The TodoCounter example, a second consumer on the Composable Architecture.