@407dev/cli 0.1.0 → 0.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@407dev/cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "repository": {
     "type": "git",
@@ -40,8 +40,8 @@
     "tsup": "^8.4.0",
     "typescript": "^5.7.3",
     "vitest": "3.0.7",
-    "@407dev/config": "0.0.1",
-    "@407dev/api-client": "0.0.1"
+    "@407dev/api-client": "0.0.1",
+    "@407dev/config": "0.0.1"
   },
   "scripts": {
     "build": "tsup",

package/skills/407dev-cms-fields/SKILL.md

@@ -92,11 +92,17 @@ export const blog = defineCollection({
 Listing page:
 ```astro
 ---
-import { getEntries } from '@407dev/cms-astro';
+import { f, getEntries } from '@407dev/cms-astro';
 import { blog } from '../../cms/collections';
 const posts = getEntries(blog); // published only in production; includes drafts/scheduled in preview
 ---
-{posts.map((p) => <a href={`/blog/${p.slug}`}>{p.content.title}</a>)}
+<ul {...f.collectionAttrs(blog)}>
+  {posts.map((p) => (
+    <li {...f.entryScope(blog, p.slug).attrs()}>
+      <a href={`/blog/${p.slug}`}>{p.content.title}</a>
+    </li>
+  ))}
+</ul>
 ```
 Detail page (`src/pages/blog/[slug].astro`):
 ```astro

package/skills/407dev-cms-fields/references/helpers.md

@@ -63,6 +63,10 @@ const alt = typeof image === 'object' && image ? (image.alt ?? '') : '';
 - **Seed-once semantics:** `cms push` inserts seed entries once only when the collection has never been seeded (`collections.seeded_at IS NULL`) and has zero entries. Once seeded, `seeded_at` is recorded and the dashboard owns all content. Seeds are never re-applied, even if an editor deletes every item, and seeds are never a render-time fallback.
 - **Seeding is not publishing:** seeded entries land as `published` in the draft tables, but the live site only ever serves the last published `site_versions` snapshot. A rebuild or redeploy re-reads that old snapshot — it never publishes. Deploy tokens can't publish either, so ask the user to publish from the dashboard. `cms push` warns with `Unpublished: ...` on every push while any collection has published content missing from the live bundle, not just the push that seeded it.
 
+## Collection attributes (canvas editing)
+- `f.collectionAttrs(collection)` (or `cmsCollectionAttr(key)`): returns `{ 'data-cms-collection': key }`. Put on listing wrappers (e.g. `<ul {...f.collectionAttrs(blog)}>`) so clicking the listing in the visual canvas opens the collection editor modal.
+- `f.entryScope(collection, slug).attrs()` (or `cmsEntryAttr(key, slug)`): returns `{ 'data-cms-collection': key, 'data-cms-entry': slug }`. Put on each item wrapper so clicking opens that specific entry directly.
+
 ## Diagnostics
 | `cms check` message | Fix |
 | --- | --- |

package/skills/407dev-cms-setup/SKILL.md

@@ -87,12 +87,16 @@ In the dev server:
 ## 7. CI and deploy
 - The user creates a **deploy token** for the site in the dashboard. It's shown once and starts with `cms_dt_`. Store it as the CI secret `CMS_AUTH_TOKEN`. It only authorizes manifest pushes and migrations for that site.
 - The pipeline order is `pnpm exec cms check` → `pnpm exec cms push --yes` → `pnpm astro build`. Use `--yes` only in CI, where orphan prompts can't be answered. Review orphans locally first.
-- Cloudflare Pages env vars:
-  - Production: `CMS_SITE_ID`, `CMS_CONTENT_URL`.
-  - Preview deployment: `CMS_SITE_ID`, `CMS_CONTENT_URL`, `CMS_PREVIEW_BUILD=1`. (Site hosts hold zero preview secrets; content-worker verifies preview tokens directly).
+- Cloudflare Pages configuration:
+  - Compatibility: SSR preview builds require the `nodejs_compat` flag and a compatibility date ≥ `2025-04-01`.
+  - Environment variables:
+    - Production: `CMS_SITE_ID`, `CMS_CONTENT_URL`.
+    - Preview deployment: `CMS_SITE_ID`, `CMS_CONTENT_URL`, `CMS_PREVIEW_BUILD=1`. (Site hosts hold zero preview secrets; content-worker verifies preview tokens directly).
 - The Pages project name and branch are set on the site in the dashboard. Publishing in the CMS triggers the rebuild, so no webhook setup is needed in the repo.
 
 ## Gotchas
-- A missing or wrong `CMS_SITE_ID` doesn't fail the build: bundle fetch errors are swallowed and every field renders its default. If the content looks stale, check `.cms/bundle.json`.
+- Builds fail on unreachable content URLs or bundle fetch failures: `astro build` rethrows with the URL and HTTP status to prevent deploying empty or broken pages; a 404 (site has no published version yet) only warns so first builds and preview-twin builds succeed. In `astro dev`, bundle fetch failures still fail gracefully. Check `CMS_CONTENT_URL` and `CMS_SITE_ID` if the build fails.
+- Never commit `.cms/` or `.dev.vars` / `.env` to git. Ensure both `.env` and `.cms/` are in `.gitignore`.
+- SSR preview builds on Cloudflare Pages require `nodejs_compat` and compatibility date ≥ `2025-04-01` for `node:async_hooks` preview context isolation.
 - `cms push` skips unchanged manifests using `.cms/state.json`. `--force` pushes anyway.
 - Preview responses must stay `Cache-Control: no-store` and `noindex`, which the integration's middleware already handles. Don't add caching middleware in front of `/_preview/*`.