Version 1.1.2

.github/workflows/npm-publish.yml

@@ -6,7 +6,7 @@ on:
   workflow_dispatch:
     inputs:
       release_tag:
-        description: "Release tag to publish, for example v1.1.1"
+        description: "Release tag to publish, for example v1.1.2"
         required: true
         type: string
 

CHANGELOG.md

@@ -2,7 +2,14 @@
 
 All notable changes to `layout-style-css` are documented here.
 
-This project follows semantic versioning. The `1.1.1` release is additive and keeps the existing `ly-*` public contract intact.
+This project follows semantic versioning. The `1.1.2` release is a patch recovery for the `1.1.1` package and keeps the existing `ly-*` public contract intact.
+
+## [1.1.2] - 2026-07-08
+
+### Fixed
+
+- Reissued the release metadata, package lock, README install examples, wiki checklist, and publish workflow recovery tag under `1.1.2`.
+- Kept the additive `1.1.1` CSS and documentation contract intact while moving the publish target to a clean patch version.
 
 ## [1.1.1] - 2026-07-05
 

README.md

@@ -18,7 +18,7 @@ The versioned wiki source lives in this repository so docs can be reviewed with
 | [Layout styles](docs/wiki/Layout-Styles.md) | All layout personalities, including F-Pattern, Z-Pattern, Split-Screen, Mondrian, and Synthwave. |
 | [UI Style Kit compatibility](docs/wiki/UI-Style-Kit-Compatibility.md) | Prefix aliases and the boundary between structure and visual styling. |
 | [Demo and GitHub Pages](docs/wiki/Demo-And-GitHub-Pages.md) | Demo QA, Pages artifact behavior, and deployment setup. |
-| [Release and publishing](docs/wiki/Release-And-Publishing.md) | v1.1.1 release checklist, npm verification, and tag guidance. |
+| [Release and publishing](docs/wiki/Release-And-Publishing.md) | v1.1.2 release checklist, npm verification, and tag guidance. |
 | [Security and support](docs/wiki/Security-And-Support.md) | Security model, supported versions, and reporting path. |
 | [Contributing](docs/wiki/Contributing.md) | Local development, CSS rules, and review expectations. |
 | [Wiki sidebar source](docs/wiki/_Sidebar.md) | Navigation file for a GitHub Wiki mirror. |
@@ -41,7 +41,7 @@ Use as a standalone layout system with all styles or just one layout personality
 
 ```bash
 # Install the full layout system
-npm install layout-style-css@1.1.1
+npm install layout-style-css@1.1.2
 ```
 
 Then import whichever CSS entrypoints you need:
@@ -54,13 +54,13 @@ import "layout-style-css/minimal-saas.css";
 Pair with UI Style Kit CSS for a complete layout and visual system. Themes and layouts can mix and match UI styles.  Set the vibe with color schemes that offer a range of moods, from minimal to maximal, from Bauhaus to Brutalism.
 
 ```bash
-npm install layout-style-css@1.1.1 ui-style-kit-css@2.0.1
+npm install layout-style-css@1.1.2 ui-style-kit-css@2.0.1
 ```
 
 Additionally installing Interactive Surface CSS sets you up with a complete reactive layout and surface system.
 
 ```bash
-npm install layout-style-css@1.1.1 ui-style-kit-css@2.0.1 interactive-surface-css@1.2.5
+npm install layout-style-css@1.1.2 ui-style-kit-css@2.0.1 interactive-surface-css@1.2.5
 ```
 
 ## Quick Start
@@ -592,7 +592,7 @@ The check command builds `dist/`, runs Stylelint, runs contract tests, runs resp
 Before publishing:
 
 ```bash
-npm view layout-style-css@1.1.1 version --json
+npm view layout-style-css@1.1.2 version --json
 npm run release:verify
 npm audit --audit-level=moderate
 ```
@@ -602,7 +602,7 @@ Publish and verify:
 ```bash
 npm login
 npm publish --access public
-npm view layout-style-css@1.1.1
+npm view layout-style-css@1.1.2
 ```
 
 After publish, verify these CDN URLs:
@@ -612,7 +612,7 @@ https://unpkg.com/layout-style-css@1/dist/layout-style-css.min.css
 https://cdn.jsdelivr.net/npm/layout-style-css@1/dist/layout-style-css.min.css
 ```
 
-Tag the release as `v1.1.1` in `Foscat/layout-style-css`. The npm publish workflow runs when that release is published and can be recovered manually from Actions with `release_tag` set to `v1.1.1`.
+Tag the release as `v1.1.2` in `Foscat/layout-style-css`. The npm publish workflow runs when that release is published and can be recovered manually from Actions with `release_tag` set to `v1.1.2`.
 
 ## Compatibility
 

docs/wiki/Home.md

@@ -1,6 +1,6 @@
 # Layout Style CSS Wiki
 
-Version 1.1.1 documents the professional library contract for `layout-style-css`: install paths, package exports, layout primitives, recipes, UI Style Kit compatibility, demo deployment, security, and release workflow.
+Version 1.1.2 documents the professional library contract for `layout-style-css`: install paths, package exports, layout primitives, recipes, UI Style Kit compatibility, demo deployment, security, and release workflow.
 
 ## Start Here
 
@@ -13,7 +13,7 @@ Version 1.1.1 documents the professional library contract for `layout-style-css`
 | [Layout Styles](Layout-Styles.md) | All layout personalities and when to use them. |
 | [UI Style Kit Compatibility](UI-Style-Kit-Compatibility.md) | Prefix aliases and ownership boundaries. |
 | [Demo And GitHub Pages](Demo-And-GitHub-Pages.md) | Demo QA and Pages deployment. |
-| [Release And Publishing](Release-And-Publishing.md) | npm v1.1.1 verification and publish checklist. |
+| [Release And Publishing](Release-And-Publishing.md) | npm v1.1.2 verification and publish checklist. |
 | [Security And Support](Security-And-Support.md) | Security model, supported versions, and reporting path. |
 | [Contributing](Contributing.md) | Contribution workflow and review expectations. |
 

docs/wiki/Release-And-Publishing.md

@@ -1,12 +1,12 @@
 # Release And Publishing
 
-This page is the release checklist for `layout-style-css@1.1.1`.
+This page is the release checklist for `layout-style-css@1.1.2`.
 
 ## Version Contract
 
-- `package.json` version is `1.1.1`.
-- `package-lock.json` is synchronized with `1.1.1`.
-- `CHANGELOG.md` contains a `1.1.1` entry.
+- `package.json` version is `1.1.2`.
+- `package-lock.json` is synchronized with `1.1.2`.
+- `CHANGELOG.md` contains a `1.1.2` entry.
 - README and wiki docs link to the current public API.
 
 ## Verification
@@ -30,7 +30,7 @@ Expected result: every command exits with status `0`. `git diff --check` may pri
 Before publishing, confirm npm does not already have the target version:
 
 ```bash
-npm view layout-style-css@1.1.1 version --json
+npm view layout-style-css@1.1.2 version --json
 ```
 
 Publish:
@@ -43,19 +43,19 @@ npm publish --access public
 Verify:
 
 ```bash
-npm view layout-style-css@1.1.1
+npm view layout-style-css@1.1.2
 ```
 
 ## Tag
 
 Tag the release:
 
 ```bash
-git tag v1.1.1
-git push origin v1.1.1
+git tag v1.1.2
+git push origin v1.1.2
 ```
 
-The npm publish workflow runs when the `v1.1.1` GitHub release is published. If the release event needs to be replayed, run the `Node.js Package` workflow manually from the default branch with `release_tag` set to `v1.1.1`.
+The npm publish workflow runs when the `v1.1.2` GitHub release is published. If the release event needs to be replayed, run the `Node.js Package` workflow manually from the default branch with `release_tag` set to `v1.1.2`.
 
 ## GitHub Wiki Mirror
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "layout-style-css",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "Shell-first CSS layout primitives that complement ui-style-kit-css@2.0.1.",
   "type": "module",
   "license": "MIT",

test/layout-css-contract.test.mjs

@@ -623,7 +623,7 @@ assert(!minified.includes("@import"), "Minified bundle must be layout-only and f
 
 const packageJson = JSON.parse(readFileSync(join(root, "package.json"), "utf8"));
 assert.equal(packageJson.name, "layout-style-css");
-assert.equal(packageJson.version, "1.1.1");
+assert.equal(packageJson.version, "1.1.2");
 assert.equal(packageJson.license, "MIT");
 assert.equal(packageJson.private, undefined);
 assert.equal(packageJson.description.includes("ui-style-kit-css@2.0.1"), true);
@@ -882,8 +882,8 @@ for (const link of readmeLinks.filter(isLocalMarkdownLink)) {
 const changelog = readFileSync(join(root, "CHANGELOG.md"), "utf8");
 assert(changelog.includes("# Changelog"), "CHANGELOG.md should use a standard changelog heading");
 assert(
-  changelog.includes("## [1.1.1] - 2026-07-05"),
-  "CHANGELOG.md should describe the 1.1.1 release candidate"
+  changelog.includes("## [1.1.2] - 2026-07-08"),
+  "CHANGELOG.md should describe the 1.1.2 patch recovery"
 );
 assert(changelog.includes("F-Pattern"), "CHANGELOG.md should mention the new F-Pattern layout");
 assert(changelog.includes("Synthwave"), "CHANGELOG.md should mention the new Synthwave layout");
@@ -892,7 +892,14 @@ assert(changelog.includes("wiki"), "CHANGELOG.md should mention the new wiki doc
 
 const wikiHome = readFileSync(join(root, "docs/wiki/Home.md"), "utf8");
 assert(wikiHome.includes("# Layout Style CSS Wiki"), "Wiki home should use a clear product heading");
-assert(wikiHome.includes("Version 1.1.1"), "Wiki home should identify the documented release");
+assert(wikiHome.includes("Version 1.1.2"), "Wiki home should identify the documented release");
+const releaseChecklist = readFileSync(join(root, "docs/wiki/Release-And-Publishing.md"), "utf8");
+assert(
+  releaseChecklist.includes("layout-style-css@1.1.2") &&
+    releaseChecklist.includes("git tag v1.1.2") &&
+    releaseChecklist.includes("release_tag` set to `v1.1.2`"),
+  "Release checklist should identify the 1.1.2 package, tag, and workflow recovery path"
+);
 for (const file of requiredDocumentationFiles.filter((file) => file.startsWith("docs/wiki/"))) {
   const content = readFileSync(join(root, file), "utf8");
   assert(content.includes("# "), `${file} should include a top-level heading`);
@@ -914,7 +921,7 @@ assert(
 assert(
   npmPublishWorkflow.includes("workflow_dispatch:") &&
     npmPublishWorkflow.includes("release_tag:") &&
-    npmPublishWorkflow.includes('description: "Release tag to publish, for example v1.1.1"'),
+    npmPublishWorkflow.includes('description: "Release tag to publish, for example v1.1.2"'),
   "npm publish workflow should expose a manual recovery dispatch with an explicit release tag"
 );
 assert(