@flashdsm/genome 0.3.0 → 0.4.0

package/README.md

@@ -32,10 +32,16 @@ In your app's folder, in a terminal or in your AI editor's chat:
 npx @flashdsm/genome@latest connect
 ```
 
-`connect` scans the folder (stylesheets, CSS inside JS/TS, Tailwind config, theme modules, tokens files; nothing else is read) and opens Flash in your browser, showing what it found and a short code that matches the one in your terminal. Click **Connect** there: Flash creates the system in your account, and the command links the repo (`genome.config.json`), writes the system into it (`pull --confirm`) and stores a token bound to that system under `~/.config/flash-dsm/`. Inside Claude Code it also adds Genome as the project's MCP server; elsewhere it prints the line to add. `--name` overrides the name, which otherwise comes from `package.json`; `--no-open` prints the link instead of opening it.
+`connect` scans the folder (stylesheets, CSS inside JS/TS, Tailwind config, theme modules, tokens files; nothing else is read) and opens Flash in your browser, showing what it found and a short code that matches the one in your terminal. Click **Connect** there: Flash creates the system in your account, and the command links the repo (`genome.config.json`), writes the system into it (`pull --confirm`), writes the files an agent reads (AGENTS.md, the skill, the Cursor rule) and stores a token bound to that system under `~/.config/flash-dsm/`. Inside Claude Code it also adds Genome as the project's MCP server; elsewhere it prints the line to add. `--name` overrides the name, which otherwise comes from `package.json`; `--no-open` prints the link instead of opening it.
+
+Run `connect` again in a folder that is already connected and it updates that system instead of making another: no scan, no Connect click; it pulls, refreshes the agent files and the live preview. `connect --new` makes a new system anyway. If the linked system is gone or this machine can't open it, connect says why and connects the folder as a new system.
+
+Your app keeps running on its own CSS: `tokens.css` is Flash's copy, and nothing imports it until you say so. `connect` ends with one question for you (or your agent to ask you): use Flash's colours, so a change in Flash shows up in the app? The steps it prints keep every variable name and leave the screen the same in light and dark. AGENTS.md carries the same steps, plus how changes move: while `genome watch` runs in the background, both ways happen by themselves. Change a token in Flash and Genome rewrites `tokens.css` within seconds, no Publish; save the app's CSS and Flash takes the change. Genome never writes over a hand edit to `tokens.css` that Flash doesn't hold. Without it, `pull --confirm` and `push --confirm` do the same once.
 
 When your app's dev server is running, `connect` also leaves a live preview in the background (localhost:4747): Flash's editor shows your real app and recolours it as you edit tokens, through its CSS variables. Nothing is written to your code. `npx @flashdsm/genome@latest preview` starts it again; `preview --stop` ends it.
 
+`connect` also leaves Genome watching the folder. Change a colour, a theme or a type size in your app's own stylesheets and, a couple of seconds after you save, Flash takes it and the editor says what changed, with Undo. Only what you changed comes in: a token edited in Flash since keeps Flash's value (the notice says so), nothing in Flash is deleted, and a comment or whitespace save does nothing. Genome's own files (`tokens.css`, `design-tokens.json`, `genome/`) are never read back. It rescans once an hour as a backup, and keeps running after the terminal closes; the watcher and the live preview are one background process. `npx @flashdsm/genome@latest watch` starts it again, `watch --stop` ends both, and `watch --once` sends one scan in the foreground and says what Flash did with it. The log is `~/.config/flash-dsm/genome-watch.log`.
+
 The link works once and expires after 15 minutes. `init --code` does the same with a setup code instead of the browser.
 
 ## Quick start
@@ -304,7 +310,8 @@ otherwise only added).
 }
 ```
 
-`state` is one of `in-step`, `flash-ahead` (Flash published since the pull),
+`state` is one of `in-step`, `flash-ahead` (Flash changed since the pull: its
+revision moved, published or not),
 `repo-dirty` (a pulled file changed or is missing), `both`, `never-pulled`.
 `flashAhead` and `dirty` are the booleans behind it; `changedTokens` lists
 the token values the repo changed (`code: "repo-edit"`, what `push` would

package/dist/index.d.ts

@@ -83,16 +83,22 @@ declare function parseCliArgs(argv: string[]): {
     name?: string;
     /** connect: print the link instead of opening the browser. */
     noOpen: boolean;
+    /** connect: a new system even when this folder is already connected. */
+    fresh: boolean;
     /** preview: run the proxy in this process (what the background child runs). */
     serve: boolean;
-    /** preview: stop the background proxy. */
+    /** preview / watch: stop the background process. */
     stop: boolean;
+    /** watch: one scan, sent in the foreground, then exit. */
+    once: boolean;
     /** preview --serve: the app's dev server, the system, Flash's origin. */
     devUrl?: string;
     system?: number;
     origin?: string;
     /** pull / push: write, rather than print the plan. */
     confirm: boolean;
+    /** pull: write even when it renames variables the app reads. */
+    acceptRename: boolean;
     /** pull / push / drift: one JSON object on stdout. */
     json: boolean;
 };