@ifloppy/maxcraftmc-ui-svelte 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 0.1.2
+
+- Added explicit AI-generated project notices.
+- Removed internal/local consumer documentation from the public docs.
+- Updated published package metadata and public usage snippets.
+
 ## 0.1.0
 
 Initial MaxCraft compatibility package.

package/README.md

@@ -19,6 +19,13 @@ projects:
 The implementation is derived from Carbon Svelte 0.89.4 under Apache-2.0. The
 theme tokens and visual overrides are MaxCraft-specific.
 
+## AI Generated Notice
+
+This project was generated entirely by AI. Treat it as experimental software:
+review the source, dependency behavior, accessibility, security, and licensing
+fit before using it in production. MaxCraft-specific styling and compatibility
+claims should be validated in each consuming application.
+
 ## Install
 
 ```sh
@@ -31,18 +38,7 @@ alias after the package is published:
 ```json
 {
   "dependencies": {
-    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.0",
-    "carbon-icons-svelte": "^13.5.0"
-  }
-}
-```
-
-During local development inside `mpc-solution`, use a file dependency:
-
-```json
-{
-  "dependencies": {
-    "carbon-components-svelte": "file:../maxcraft-ui",
+    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.2",
     "carbon-icons-svelte": "^13.5.0"
   }
 }
@@ -105,16 +101,6 @@ npm run build
 exist. `npm run build` also runs `npm pack --dry-run` to prove the package can be
 published.
 
-## Consumer Status
-
-Current local consumers in `mpc-solution`:
-
-- `mpc-web`: SvelteKit app using the component package through a local file alias.
-- `maxcraftmc-wiki`: Hugo site using `css/maxcraft.css` through Hugo module mounts.
-
-Use [Consumer migration checklist](docs/consumer-checklist.md) when adding new
-apps or moving consumers from local file aliases to the published npm package.
-
 ## Attribution
 
 The component source and type surface are derived from

package/docs/compatibility.md

@@ -31,6 +31,8 @@ cannot see.
 - This package does not replace `carbon-icons-svelte`.
 - This package does not guarantee visual parity with IBM Carbon; MaxCraft visual
   language is the intended output.
+- This package does not provide a human-authored guarantee of correctness. It
+  was generated entirely by AI and must be reviewed before production use.
 
 ## Adding Or Changing Components
 
@@ -39,7 +41,6 @@ Before changing a component API:
 1. Compare against `carbon-components-svelte@0.89.4`.
 2. Preserve existing prop/event/slot names unless a breaking release is planned.
 3. Run `npm run check`.
-4. Verify `mpc-web` with `npm run check` and `npm run build`.
 
 If a component needs MaxCraft-specific behavior, prefer CSS/token customization
 first. Add new props only when CSS cannot express the requirement.

package/docs/consumer-checklist.md

@@ -5,26 +5,25 @@ Use this checklist when connecting a Svelte or Hugo consumer to
 
 ## Svelte Consumer
 
-- Replace `carbon-components-svelte` with a local file alias during development:
-  `file:../maxcraft-ui`.
-- Replace the local alias with `npm:@ifloppy/maxcraftmc-ui-svelte@<version>` after
-  publishing.
+- Replace `carbon-components-svelte` with
+  `npm:@ifloppy/maxcraftmc-ui-svelte@<version>`.
 - Keep `carbon-icons-svelte` installed.
 - Remove `carbon-components` unless the app imports it directly.
 - Import `carbon-components-svelte/css/all.css` once in the root layout.
 - Import `carbon-components-svelte/css/maxcraft.css` once after `all.css`.
 - Keep existing component imports unchanged when using the alias.
 - Run `npm install --ignore-scripts`.
-- During local file-link development, also run `npm install --ignore-scripts`
-  inside `maxcraft-ui`.
 - Run `npm run check`.
 - Run `npm run build`.
 - Manually verify navigation, form controls, modals, notifications, tiles, tags,
   and dark mode.
+- Because this package was generated entirely by AI, review source behavior,
+  accessibility, security, and compatibility in the consumer app before
+  production use.
 
 ## Hugo Consumer
 
-- Import `github.com/FloppyBetaStudio/maxcraft-ui` as a Hugo module and mount
+- Import `github.com/ifloppy/maxcraftmc-ui-svelte` as a Hugo module and mount
   its `css` directory to `assets/maxcraft-ui`.
 - If adding project-level mounts, explicitly restore default mounts for
   `assets`, `content`, `layouts`, `static`, and any other site folders in use.
@@ -36,7 +35,7 @@ Use this checklist when connecting a Svelte or Hugo consumer to
 
 ## Release Consumer
 
-- Update the consumer lockfile after changing from `file:` to `npm:`.
+- Update the consumer lockfile after changing package versions.
 - Run consumer checks after every package version bump.
 - Check for accidental duplicate CSS imports.
 - Keep `carbon-icons-svelte` version compatible with the consuming app.

package/docs/contributing.md

@@ -10,14 +10,6 @@ npm install --ignore-scripts
 npm run check
 ```
 
-When developing against `mpc-web`:
-
-```sh
-cd ../mpc-web
-npm install --ignore-scripts
-npm run check
-```
-
 ## What To Change First
 
 - For visual work, prefer `tokens/maxcraft.css` and `css/maxcraft.css`.
@@ -45,7 +37,7 @@ npm run check
 
 ## Verification
 
-Run from `maxcraft-ui`:
+Run from the package root:
 
 ```sh
 npm run check
@@ -61,20 +53,8 @@ The local checks cover:
 - CSS entrypoint existence
 - documentation and README link integrity
 
-Run consumers when shared CSS or package metadata changes:
-
-```sh
-cd ../mpc-web
-npm run check
-npm run build
-
-cd ../maxcraftmc-wiki
-hugo --gc --minify
-```
-
-## GitNexus
+## AI Generated Notice
 
-When editing existing symbols, run impact analysis before changes and
-`gitnexus detect-changes` before committing. Documentation-only changes usually
-do not map to symbols, but still run detect-changes before commit when the root
-repository requires it.
+This project was generated entirely by AI. Contributions and releases should
+include human review for source correctness, accessibility, security, licensing,
+and compatibility before production use.

package/docs/hugo-integration.md

@@ -15,7 +15,7 @@ Then import the public MaxCraft UI module and mount its CSS directory:
 
 ```toml
 [[module.imports]]
-path = "github.com/FloppyBetaStudio/maxcraft-ui"
+path = "github.com/ifloppy/maxcraftmc-ui-svelte"
 
 [[module.imports.mounts]]
 source = "css"
@@ -61,13 +61,13 @@ Include `maxcraft.css` before site-specific overrides:
 {{ end }}
 ```
 
-For `maxcraftmc-wiki`, the intended order is:
+The intended order is:
 
-1. Tailbliss/Tailwind base CSS
+1. Site base CSS
 2. `maxcraft-ui/maxcraft.css`
-3. Wiki-specific `css/site.css`
+3. Site-specific overrides
 
-This order gives the wiki the shared tokens while preserving its custom page
+This order gives the site the shared tokens while preserving its custom page
 layouts and animations.
 
 ## 3. Use Shared Tokens

package/docs/installation.md

@@ -7,6 +7,9 @@ This package supports two consumption modes:
 
 ## Published Package
 
+This project was generated entirely by AI. Review the code, behavior,
+accessibility, security, and licensing fit before relying on it in production.
+
 Install the package and keep `carbon-icons-svelte` as the icon source:
 
 ```sh
@@ -27,7 +30,7 @@ unchanged:
 ```json
 {
   "dependencies": {
-    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.0",
+    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.2",
     "carbon-icons-svelte": "^13.5.0"
   }
 }
@@ -41,34 +44,6 @@ import "carbon-components-svelte/css/all.css";
 import "carbon-components-svelte/css/maxcraft.css";
 ```
 
-## Local Development In mpc-solution
-
-Use the local file alias while editing the UI package beside consumers:
-
-```json
-{
-  "dependencies": {
-    "carbon-components-svelte": "file:../maxcraft-ui",
-    "carbon-icons-svelte": "^13.5.0"
-  }
-}
-```
-
-Then install in both projects:
-
-```sh
-cd maxcraft-ui
-npm install --ignore-scripts
-
-cd ../mpc-web
-npm install --ignore-scripts
-```
-
-The `maxcraft-ui` install is needed during local file-link development because
-Vite resolves package source files through the real path and dependencies such
-as `flatpickr` must exist beside that source tree. Published npm installs do not
-need this extra step.
-
 ## Required CSS Entrypoints
 
 The package preserves Carbon's original CSS entrypoints:

package/docs/publishing.md

@@ -5,14 +5,12 @@
 The intended public repository is:
 
 ```sh
-github1:FloppyBetaStudio/maxcraft-ui.git
+https://github.com/ifloppy/maxcraftmc-ui-svelte.git
 ```
 
-The root `mpc-solution` repository tracks this directory as a Git submodule.
-
 ## Pre-Publish Checks
 
-Run from `maxcraft-ui`:
+Run:
 
 ```sh
 npm install --ignore-scripts
@@ -24,18 +22,6 @@ npm run build
 The check step verifies API parity, export targets, a Vite/Svelte smoke build,
 placeholder markers, CSS entrypoints, and documentation links.
 
-Also verify consumers:
-
-```sh
-cd ../mpc-web
-npm install --ignore-scripts
-npm run check
-npm run build
-
-cd ../maxcraftmc-wiki
-hugo --gc --minify
-```
-
 ## Publish
 
 After the package is ready:
@@ -49,11 +35,17 @@ Then update consumers from local file aliases to npm aliases:
 ```json
 {
   "dependencies": {
-    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.0"
+    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.2"
   }
 }
 ```
 
+## AI Generated Notice
+
+This package was generated entirely by AI. Each release should be reviewed for
+source correctness, accessibility, security, licensing, and compatibility before
+production use.
+
 ## Attribution Requirements
 
 Keep these files in every published package:
@@ -70,5 +62,4 @@ from `carbon-components-svelte@0.89.4`, which is Apache-2.0 licensed.
 - Keep `css/maxcraft.css` self-contained for Hugo.
 - Keep `tokens/maxcraft.css` as the token source for future tooling.
 - Run API and CSS entrypoint checks before every release.
-- Test `mpc-web` and `maxcraftmc-wiki` before bumping the package version.
 - Avoid introducing a dependency on Carbon icons beyond `carbon-icons-svelte`.

package/docs/svelte-migration.md

@@ -1,27 +1,15 @@
 # Svelte Migration Guide
 
-This guide is for apps already using `carbon-components-svelte@0.89.4`, such as
-`mpc-web`.
+This guide is for apps already using `carbon-components-svelte@0.89.4`.
 
 ## 1. Replace The Dependency
 
-Local development:
-
-```json
-{
-  "dependencies": {
-    "carbon-components-svelte": "file:../maxcraft-ui",
-    "carbon-icons-svelte": "^13.5.0"
-  }
-}
-```
-
 Published package:
 
 ```json
 {
   "dependencies": {
-    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.0",
+    "carbon-components-svelte": "npm:@ifloppy/maxcraftmc-ui-svelte@0.1.2",
     "carbon-icons-svelte": "^13.5.0"
   }
 }
@@ -29,6 +17,8 @@ Published package:
 
 Remove the old `carbon-components` dependency unless the app imports it
 directly. `@ifloppy/maxcraftmc-ui-svelte` includes the CSS entrypoints it needs.
+This project was generated entirely by AI, so review compatibility and behavior
+in the consuming app before production use.
 
 ## 2. Keep Component Imports
 
@@ -109,15 +99,3 @@ Manually inspect:
 - Tiles and tags
 - Light/dark theme switching
 - Mobile layout
-
-## Known Local Development Detail
-
-When using `file:../maxcraft-ui`, install dependencies in `maxcraft-ui` itself:
-
-```sh
-cd ../maxcraft-ui
-npm install --ignore-scripts
-```
-
-This avoids Vite resolution failures for transitive dependencies such as
-`flatpickr`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ifloppy/maxcraftmc-ui-svelte",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "license": "Apache-2.0",
   "description": "MaxCraft themed compatibility build of carbon-components-svelte 0.89.4.",
   "type": "module",
@@ -69,7 +69,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+ssh://github1:FloppyBetaStudio/maxcraft-ui.git"
+    "url": "https://github.com/ifloppy/maxcraftmc-ui-svelte.git"
   },
   "keywords": [
     "carbon",