@mozole/cli 1.4.0 → 1.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (38) hide show
  1. package/CHANGELOG.md +18 -1
  2. package/README.md +7 -1
  3. package/dist/commands/adopt.d.ts +1 -1
  4. package/dist/commands/adopt.d.ts.map +1 -1
  5. package/dist/commands/adopt.js +312 -102
  6. package/dist/commands/adopt.js.map +1 -1
  7. package/dist/platform/process.d.ts.map +1 -1
  8. package/dist/platform/process.js +4 -0
  9. package/dist/platform/process.js.map +1 -1
  10. package/dist/scaffold/adoption.d.ts +17 -0
  11. package/dist/scaffold/adoption.d.ts.map +1 -0
  12. package/dist/scaffold/adoption.js +279 -0
  13. package/dist/scaffold/adoption.js.map +1 -0
  14. package/dist/scaffold/design.d.ts +4 -0
  15. package/dist/scaffold/design.d.ts.map +1 -0
  16. package/dist/scaffold/design.js +51 -0
  17. package/dist/scaffold/design.js.map +1 -0
  18. package/dist/scaffold/legacy.d.ts +4 -0
  19. package/dist/scaffold/legacy.d.ts.map +1 -0
  20. package/dist/scaffold/legacy.js +139 -0
  21. package/dist/scaffold/legacy.js.map +1 -0
  22. package/dist/scaffold/routes.d.ts +3 -0
  23. package/dist/scaffold/routes.d.ts.map +1 -0
  24. package/dist/scaffold/routes.js +37 -0
  25. package/dist/scaffold/routes.js.map +1 -0
  26. package/dist/scaffold/standalone.d.ts +2 -1
  27. package/dist/scaffold/standalone.d.ts.map +1 -1
  28. package/dist/scaffold/standalone.js +43 -19
  29. package/dist/scaffold/standalone.js.map +1 -1
  30. package/dist/scaffold/templates.d.ts.map +1 -1
  31. package/dist/scaffold/templates.js +26 -5
  32. package/dist/scaffold/templates.js.map +1 -1
  33. package/dist/version.d.ts +4 -2
  34. package/dist/version.d.ts.map +1 -1
  35. package/dist/version.js +3 -1
  36. package/dist/version.js.map +1 -1
  37. package/docs/agent-audit.md +2 -2
  38. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,7 +1,24 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.4.2
4
+
5
+ - Package the default Tailwind CSS 4.3.3 and `@tailwindcss/vite` integration for Vite, React Router and PHP scaffolds.
6
+ - Keep generated starter styles in the Tailwind base layer and verify that utility CSS is emitted in production builds.
7
+ - Extend design guidance with static utility classes, semantic theme tokens and styling-pipeline checks for adopted projects.
8
+
9
+ ## 1.4.1
10
+
11
+ - Include Tailwind CSS 4.3.3 and its Vite plugin in every new project; keep starter styles in the base layer and verify generated utilities in production CSS.
12
+
13
+ - Make `adopt` reconcile legacy and previously optimized projects with the current canonical project system without requiring an integration flag.
14
+ - Archive Mozole-owned legacy state and managed files during migration, preserve unrelated user integrations and design exports, and restore managed changes if installation fails.
15
+ - Refresh managed instruction blocks, standalone verification/QA scripts, PHP templates, tooling pins and configured project verifiers idempotently.
16
+ - Keep CCE, governor, telemetry and token-optimization layers strictly opt-in through explicit integration flags.
17
+
3
18
  ## 1.4.0
4
19
 
20
+ - Add provider-neutral design handoff and shared AGENTS.md guardrails for spacing, typography, contrast, assets and responsive validation; preserve user exports under docs/design/.
21
+
5
22
  - Make default scaffolds independent of the CLI: no CCE, governor, telemetry, caches, MCP, hooks, or optimization dependency. Environment variables cannot enable integration mode.
6
23
  - Keep useful basic AGENTS.md and CLAUDE.md guidance in plain projects. Require explicit integration flags for new/adopt; refresh managed agent blocks and hook definitions while preserving user content.
7
24
  - Track CCE retrieval through PostToolUse MCP events and provide a valid reason from the visual QA workflow.
@@ -10,4 +27,4 @@
10
27
  - Preserve failed creation logs before staging cleanup.
11
28
  - Add standalone browser QA and integration coverage for plain, PHP, and optimized scaffolds; provision PHP in Windows/Linux CI.
12
29
 
13
- Migration: default generated projects use standalone npm scripts rather than a project-local `mozole` executable. Use the globally installed CLI when desired, or pass `--cce-install` to generate the optional integration mode. Plain adoption preserves existing user integrations and requires the flag to update an already optimized project.
30
+ Migration: default generated projects use standalone npm scripts rather than a project-local `mozole` executable. Use the globally installed CLI when desired, or pass `--cce-install` to generate the optional integration mode. Plain adoption migrates previously optimized projects to the current standalone system, archiving Mozole-owned integration remnants and preserving unrelated user integrations. Explicit flags select optimized adoption. Legacy PHP templates, managed scripts, instruction blocks and tooling pins are reconciled; customized backend files receive a review notice. Failed installation restores managed files and moved state.
package/README.md CHANGED
@@ -29,6 +29,10 @@ npm run qa:visual
29
29
 
30
30
  React Router uses `ssr: false` and `prerender: true`. The starter builds real HTML for `/`, `/about`, and `/contact` into `build/client/`, plus `__spa-fallback.html`. Production requires no Node server. See [React Router prerendering](https://reactrouter.com/how-to/pre-rendering).
31
31
 
32
+ ## Design references and assets
33
+
34
+ Place exported `design.md`, images, icons, fonts and reference screens under `docs/design/`. Generated `AGENTS.md` treats these as design evidence, preserves their intent, and requires checks for spacing, loaded fonts, foreground/background contrast, responsive behavior and interaction states. It permits justified corrections instead of blindly copying tokens. `docs/design/README.md` explains the handoff; no provider-specific design is generated. Existing exports remain untouched during adoption. Routine QA stays screenshot-free; visual comparison remains opt-in.
35
+
32
36
  ## PHP backend
33
37
 
34
38
  ```sh
@@ -71,11 +75,13 @@ Optimized verification/QA reuses matching successful evidence. Use `--force` for
71
75
 
72
76
  ## Adopt an existing project
73
77
 
78
+ New projects include pinned Tailwind CSS v4 and `@tailwindcss/vite` by default in all modes, including PHP projects. `app/styles/global.css` imports Tailwind and keeps starter styles in the base layer. Adoption preserves existing CSS and Vite configuration; it does not automatically migrate older styling pipelines or inject Preflight into an existing design.
79
+
74
80
  ```sh
75
81
  mozole adopt ../existing-app
76
82
  ```
77
83
 
78
- Plain adoption adds standalone verification/QA, basic agent guidance, and missing test tools to a React project using Vite or React Router. Application source and existing user integrations are preserved. It never enables optimization tooling. An already optimized project requires `--cce-install` for managed integration updates rather than silently removing previously enabled integrations. Changed package metadata is backed up under `.mozole/backups/`; managed files are restored on failure.
84
+ Adoption reconciles a React/Vite or React Router project with the current project system. Without `--cce-install`, it removes Mozole-owned CCE integrations, optimization hooks and state, including from previously optimized projects, and installs standalone verification/QA. The flag explicitly selects the optimized system. User instructions, unrelated integrations, application source and design exports are preserved. Recognized unchanged legacy PHP templates are upgraded; customized backend files are retained with a review notice. Replaced files and obsolete state are archived under `.mozole/backups/adopt-*`; managed files are restored if installation fails. Tooling versions and npm dependencies are reconciled on every adoption. Custom verifier commands and configured QA servers remain in use. Repeating adoption does not duplicate managed instruction blocks.
79
85
 
80
86
  ## CLI commands
81
87
 
@@ -1,6 +1,6 @@
1
1
  import type { Output } from "../output.js";
2
2
  import { type ProgressState } from "../progress.js";
3
- export declare function detectRoutes(source: string): string[];
3
+ export { detectRoutes } from "../scaffold/routes.js";
4
4
  export declare function adoptCommand(input: string | undefined, cwd: string, output?: Output, options?: {
5
5
  cceInstall?: boolean | undefined;
6
6
  verbose?: boolean | undefined;
@@ -1 +1 @@
1
- {"version":3,"file":"adopt.d.ts","sourceRoot":"","sources":["../../src/commands/adopt.ts"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,cAAc,CAAC;AAG3C,OAAO,EAAE,KAAK,aAAa,EAAgB,MAAM,gBAAgB,CAAC;AAyFlE,wBAAgB,YAAY,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,CAKrD;AA+KD,wBAAsB,YAAY,CAChC,KAAK,EAAE,MAAM,GAAG,SAAS,EACzB,GAAG,EAAE,MAAM,EACX,MAAM,GAAE,MAAgB,EACxB,OAAO,GAAE;IACP,UAAU,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IACjC,OAAO,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IAC9B,UAAU,CAAC,EAAE,CAAC,CAAC,KAAK,EAAE,aAAa,KAAK,IAAI,CAAC,GAAG,SAAS,CAAC;CACtD,GACL,OAAO,CAAC,MAAM,CAAC,CA6TjB"}
1
+ {"version":3,"file":"adopt.d.ts","sourceRoot":"","sources":["../../src/commands/adopt.ts"],"names":[],"mappings":"AA0BA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,cAAc,CAAC;AAG3C,OAAO,EAAE,KAAK,aAAa,EAAgB,MAAM,gBAAgB,CAAC;AAgGlE,OAAO,EAAE,YAAY,EAAE,MAAM,uBAAuB,CAAC;AA+JrD,wBAAsB,YAAY,CAChC,KAAK,EAAE,MAAM,GAAG,SAAS,EACzB,GAAG,EAAE,MAAM,EACX,MAAM,GAAE,MAAgB,EACxB,OAAO,GAAE;IACP,UAAU,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IACjC,OAAO,CAAC,EAAE,OAAO,GAAG,SAAS,CAAC;IAC9B,UAAU,CAAC,EAAE,CAAC,CAAC,KAAK,EAAE,aAAa,KAAK,IAAI,CAAC,GAAG,SAAS,CAAC;CACtD,GACL,OAAO,CAAC,MAAM,CAAC,CA0XjB"}