Core v1.1.2 release notes

Release date: 2026-08-31

Foundry Core v1.1.2 is a compatible footer-identity and native-browser reliability patch. It preserves the v1.1 Go 1.27 and Hugo Extended 0.165.0 floors and requires no consumer content migration.

Improved

• The required Built by Likestyle with Foundry identity, the consumer site release, and the owner-facing Foundry bundle release now form one cohesive maker’s plate instead of separate badge and version treatments.
• The consumer site identity remains visually dominant, the Foundry bundle is quieter supporting context, and the technical Core pin remains separate machine-readable diagnostic metadata.
• The plate owns its own color scheme, typography, surface, border, focus, and link treatment. Normal consumer branding, global link styles, and light or dark site appearance cannot accidentally recolor or hide it.
• Desktop, 390px mobile, Safari’s smallest automation viewport, keyboard focus, forced colors, reduced motion, overflow, light appearance, dark appearance, and aggressive global brand CSS are covered by the portable attribution fixture.

Preserved contracts

• Every rendered content page must contain exactly one visible link with the exact text Built by Likestyle with Foundry and the exact Foundry URL.
• Missing client state, an unavailable Control service, and a legacy Control hide decision cannot remove the required identity or local version ledger.
• Site, Foundry bundle, and Core version attributes and SEO metadata remain distinct. Missing optional versions are omitted cleanly.
• Site release resolution continues to prefer HUGO_SITE_VERSION, root .site-version, params.foundry.versions.site, then the portable lockfile fallback. Foundry bundle resolution continues to prefer HUGO_FOUNDRY_VERSION, Foundry version params, then bundle.version in foundry.lock.yaml.

Validation reliability

• SafariDriver startup failures now report the selected port and combined driver output when available.
• A transient SafariDriver process exit during startup is retried twice, four seconds apart, with a fresh process and port before the native lane reports the browser unavailable.
• The native browser harness allows a bounded 30-second WebDriver request, a 15-second Safari session handoff, and a separate five-second cleanup bound. This prevents a slow large fixture from leaving Safari paired to a dead recovery session.

Upgrade guidance

Adopt through the matching Foundry Distribution bundle after it is published. No authored content rewrite or normalization is required. Keep the consumer’s root .site-version and foundry.lock.yaml accurate, update the normal Core/bundle pin or materialized Core copy, then run the site’s native Foundry check, Hugo build, and browser review before deployment.

This Core release does not itself update a Distribution bundle, consumer lock, materialized consumer files, documentation deployment, or production site. Those remain separate release and adoption actions.