@natjswenson/devlog 0.14.0 → 0.14.2

package/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 All notable changes to `@natjswenson/devlog` are documented here.
 
+## 0.14.2 (2026-09-17)
+
+### Added
+
+- Completed issueflow integration and made initialization host-aware.
+
+## Unreleased
+
+- Make init host-aware: Claude retains standalone skill installation while
+  Codex writes shared personal assets without shadowing the marketplace plugin.
+
+## 0.14.1 (2026-09-10) — native branded cover generation
+
+- Require Codex covers to use native generated raster artwork in the established
+  monochrome technical-engraving PRESS style; reject wireframes and SVG substitutes.
+- Require copyable agent handoffs and validated covers before publication.
+- Fix cover backfills when the target repository stores entries below `targetDir`.
+
 ## 0.14.0 (2026-09-09) — verified concept guides and AI cover composition
 
 - Add an explicit concept-guide draft workflow: select one transferable reader

package/README.md

@@ -1,7 +1,7 @@
 # devlog
 
-<!-- >>> press:masthead v0.9.0 sha256:4b48a8031589 GENERATED by @natjswenson/press, do not edit -->
-**NS** · NATE SWENSON · CLAUDE CODE + CODEX SKILL · PRESS v0.9.0 · linkedin.com/in/natejswenson
+<!-- >>> press:masthead v0.11.0 sha256:582134ecd7a5 GENERATED by @natjswenson/press, do not edit -->
+**NS** · NATE SWENSON · CLAUDE CODE + CODEX SKILL · PRESS v0.11.0 · linkedin.com/in/natejswenson
 
 ---
 <!-- <<< press:masthead -->
@@ -65,13 +65,16 @@ $devlog
 ```
 
 ```sh
-npx @natjswenson/devlog init      # create the repo, install the skill, write config
+npx @natjswenson/devlog init      # create the repo, install the Claude skill, write config
 npx @natjswenson/devlog preview   # see it rendered at http://localhost:5173
 ```
 
 `init` creates `<your-username>/daily-dev-log` on GitHub (or uses an existing
-repo), installs the skill at `~/.claude/skills/devlog/`, writes its config, and
-lets you register one or more projects in a single run.
+repo), writes shared config and personal assets to `~/.claude/skills/devlog/`,
+and lets you register one or more projects in a single run. It defaults to the
+Claude standalone installation; use `init --host codex` when configuring the
+Codex plugin. Codex keeps the marketplace-installed $devlog plugin
+authoritative and does not create or update a standalone skill copy.
 
 > **Run from any directory *outside* a clone of this repo.** Running inside it
 > causes a `package.json` name collision and `npx` fails with
@@ -91,7 +94,9 @@ lets you register one or more projects in a single run.
 ## Requirements
 
 - **Claude Code:** Authenticate `gh` in the shell and allow web research for release guides.
-- **Codex:** Use the same authenticated `gh` CLI and available web tools. `init` still writes its legacy Claude skill copy; the Codex plugin is installed separately above.
+- **Codex:** Use the same authenticated `gh` CLI and available web tools. Run
+  `init --host codex` to write shared config and personal assets; install or
+  update the marketplace plugin separately using the Codex commands above.
 - **Personal data:** Both hosts retain config, voice fallback and image-style assets in `~/.claude/skills/devlog/`; an existing `~/.claude/ghostwriter/voice` can also supply the voice.
 
 See [Codex migration notes](../../docs/codex-migration.md) for host tools and retained data paths.
@@ -125,7 +130,7 @@ not apply to a dev log.
 
 | Command | What it does |
 |---|---|
-| `devlog init` | One-time setup: create dev-log repo, install skill, write config |
+| `devlog init [--host claude or codex]` | One-time setup (Claude by default); write config and host-appropriate assets |
 | `devlog add-project` | Register a project (interactive; `--yes --path <p>` for agent use) |
 | `devlog remove-project <key> --yes` | Unregister a project (published entries stay) |
 | `devlog set <field> <value>` | Update one config field |
@@ -211,6 +216,13 @@ Netlify or Cloudflare Pages, build with `vite build`, deploy `dist/`.
 **Other stacks (Next, Astro, plain HTML):** it is static JSON and Markdown on
 GitHub. Build whatever UI you want against the data contract below.
 
+## Producer and website onboarding
+
+Follow the [complete producer and website onboarding guide](https://github.com/natejswenson/claude-skills/blob/main/skills/devlog/skills/devlog/SKILL.md#producer-and-website-onboarding).
+The guide ships inside SKILL.md for plugin, standalone Claude and npm installations.
+It covers inspecting and preserving registration, privacy, monorepo release scoping,
+and the website registry, manifest and verification required before setup is complete.
+
 ## Data contract
 
 The dev-log repo has this layout, all served as raw files from

package/SKILL.md

@@ -2,6 +2,7 @@
 name: devlog
 description: Turn releases into researched how-to posts, or explicitly draft one complete concept guide readers can implement with their own coding agent. Supports Codex AI cover drafts and conversational devlog configuration.
 user_invocable: true
+version: 0.14.2
 ---
 
 ## Codex runtime
@@ -10,6 +11,11 @@ When running in Codex, invoke this skill as `$devlog`. Resolve scripts, assets,
 and references from the directory containing this SKILL.md, regardless of the
 current working directory. Existing `~/.claude/` personal-data paths remain valid
 and are still used by the bundled scripts; they do not require Claude to run.
+The Codex marketplace plugin is the authoritative $devlog entrypoint. When
+running init from Codex, use --host codex so the CLI writes shared config,
+voice, and image-style assets without creating or updating a standalone skill
+copy in the retained legacy directory. Claude init remains the standalone
+skill-copy installation path.
 Map `Read`/`Write`/`Edit`/`Bash` to the available file and shell tools, and
 `WebSearch`/`WebFetch` to available web tools. For `AskUserQuestion`, use an
 available question tool or a concise chat question; wait for answers that gate
@@ -19,6 +25,10 @@ apps by capability rather than assuming Claude MCP tool names exist.
 
 # /devlog — Release How-To Generator
 
+<!-- press:runtime -->
+In Claude Code, load `/press`; in Codex, load `$press`; then follow the shared PRESS terminal/UI contract from `brand/agent-ui.md`. Do not copy or override that contract here.
+<!-- press:runtime -->
+
 In the default Generate mode, you turn each **new version release** (a semver git tag) in the user's projects into a
 published blog post, written in **the user's own voice**, and pushed to the GitHub repo
 configured in `~/.claude/skills/devlog/config.json`.
@@ -104,13 +114,24 @@ from a working page, not from the repo. Without it a run can push but cannot con
 anything went live. Set with `set siteUrl 'https://example.com'`, clear with
 `set siteUrl ''`.
 
-For **add-project**: resolve the path first (the repo the user named, or the cwd), then
-detect what the CLI will use — key = directory basename, remote = `git -C '<path>' remote
-get-url origin`. In a monorepo, suggest a `--path-filter` (the project's subdir) and a
-`--tag-prefix` (e.g. `myproj-v`). Confirm the resolved values with the user in ONE
-`AskUserQuestion` (options: "looks right" / sensible alternatives), then run with `--yes`
-and show the resulting project list. For **remove-project**, confirm once before running;
-tell the user published entries are not deleted.
+For **add-project**: inspect validated config first with `config --json`, then
+resolve the user's absolute repository path and compare key, label, path, remote,
+pathFilter, tagPrefix and the effective private value (omitted means false). A private
+repository requires private: true; report a privacy mismatch for correction before
+considering setup complete. Preserve a matching existing row unchanged and skip the
+add. Run add-project only when the key is absent. Report a mismatch instead of
+removing/recreating the existing row automatically; duplicate-key rejection remains
+intentional. Detect the default key from the directory basename and remote with
+`git -C '<path>' remote get-url origin`. In a monorepo, use the project's subdirectory
+as `--path-filter` and its release namespace as `--tag-prefix`. Confirm unresolved
+values with the user before adding; values already supplied or authorized need no
+second confirmation. For **remove-project**, confirm once before running; tell the
+user published entries are not deleted.
+
+Complete the [producer and website onboarding guide](#producer-and-website-onboarding)
+before declaring setup complete. It covers the exact Issue Flow monorepo fields,
+retained shared configuration, and the website registry-plus-manifest requirement.
+Registration does not publish an article; preserve any existing website content.
 
 **Private repos.** If the user says the repo is private (or a source repo happens to be
 private on GitHub even though it's configured normally), pass `--private`. A private
@@ -126,6 +147,106 @@ If any command prints `{"error": "config-missing", ...}`, tell the user to run
 `npx @natjswenson/devlog init` first. On `config-invalid`, show the message and offer to
 fix the named field via `set`.
 
+## Producer and website onboarding
+
+Registering a source project makes releases discoverable; it does not publish an
+article or finish website onboarding. Use this checklist before the first publication
+and when checking an existing integration. Invoke `/devlog` in Claude Code or
+`$devlog` in Codex; both retain personal configuration at
+`~/.claude/skills/devlog/config.json`. Keep that file outside the plugin.
+
+### Inspect and preserve the producer registration
+
+Run the host-independent CLI to inspect validated configuration first:
+
+```sh
+npx -y @natjswenson/devlog@0.14.1 config --json
+```
+
+For Issue Flow in the monorepo, compare the existing row with this example.
+Replace the example path with the user's absolute monorepo checkout path:
+
+```json
+{
+  "key": "issueflow",
+  "label": "Issue Flow",
+  "path": "/absolute/path/to/claude-skills",
+  "remote": "natejswenson/claude-skills",
+  "pathFilter": "skills/issueflow",
+  "tagPrefix": "issueflow-v"
+}
+```
+
+Compare all six fields above and the effective private value (omitted means false).
+This public Issue Flow example expects private: false; a private repository requires
+private: true and --private when adding it. If exactly one row matches, preserve it
+unchanged and skip add-project. Report any mismatch, including privacy, for correction
+before considering setup complete;
+do not remove and recreate it automatically. Direct duplicate adds are rejected.
+Only when the key is absent, run:
+
+```sh
+npx -y @natjswenson/devlog@0.14.1 add-project --yes \
+  --path '/absolute/path/to/claude-skills' --key issueflow --label 'Issue Flow' \
+  --remote natejswenson/claude-skills --path-filter skills/issueflow \
+  --tag-prefix issueflow-v
+npx -y @natjswenson/devlog@0.14.1 config --json
+```
+
+Then inspect release discovery with
+`npx -y @natjswenson/devlog@0.14.1 scan --json --project issueflow`.
+Expect only `issueflow-v` release tags and `skills/issueflow` commit/diff history;
+other skills' releases and changes must remain outside this project. An empty
+new-release list may mean entries already exist; inspect scan status and skipped
+reasons before concluding that registration failed.
+
+### Register the website and its manifest together
+
+In `natejswenson/natejswenson.io`, inspect the current remote branch before editing:
+a stale local checkout can omit an integration that already exists upstream.
+Check `PROJECTS` in `src/data/site.js` for exactly one `issueflow` row labeled
+`Issue Flow`, and check `content/devlog/issueflow/manifest.json`. Preserve an
+existing registry row and populated manifest; never replace published entries
+with the empty example below.
+
+For a new project, add its PROJECTS row and a valid manifest in the same change.
+Match neighboring registry fields. Before any article exists, the manifest is:
+
+```json
+{"entries": []}
+```
+
+The loader visits registered projects only and requires every manifest. A directory
+alone is insufficient; a missing manifest fails the build. An empty entries array
+allows the project route to render its empty state. Source, config and documentation
+changes follow the website's own PR flow, even when content publishing has a separate
+flow. Keep existing content intact and link the companion website PR from the
+producer setup PR. Consult the website README and contributor instructions for its
+current branch policy.
+
+For this target, verify `targetRepo`, `targetDir: content/devlog`, and the publishing
+branch in shared config. Set `siteUrl` from a working public page: the repository
+name is not necessarily the served domain. Do not change these settings just to
+register another source project.
+
+### Verify both halves
+
+Run the website's `npm run test:ci`, `npm run build`, and relevant
+`npm run test:e2e` checks. In a disposable fixture or preview, verify an empty
+manifest builds with an Issue Flow project route and other projects still available.
+Use an existing article or a temporary representative fixture to check the Issue Flow
+listing/filter and tag search, hash restoration, project/article links, canonical/OG
+metadata and a successful cover response (including the established fallback).
+Inspect generated sitemap routes and RSS; the RSS feed includes only the latest 30
+entries, so use a latest-dated fixture when specifically testing inclusion.
+Never commit or publish a fake article for setup, or empty a populated production
+manifest to test the pre-publication state.
+
+Record the checked commits and command outcomes in both PRs. A local producer config
+row alone is not evidence that the website integration is complete. Publishing new
+articles, backfilling old releases and merging/deploying website changes are separate
+actions from this onboarding check.
+
 ## Status mode
 
 Run `npx -y @natjswenson/devlog@latest scan --json --summary` and render a compact table:
@@ -392,9 +513,12 @@ The `--clone` flag always points at the CONTENT ROOT: `<abs-tmp>/<repo-name>` wh
 `targetDir` is empty, `<abs-tmp>/<repo-name>/<targetDir>` when it's set. Git commands
 always run against the clone root `<abs-tmp>/<repo-name>` regardless.
 
-In this legacy Generate path, each release also gets a cover image, composed inline in this same loop right before that
-release's own `publish-entry` call — a self-contained HTML/CSS (or inline SVG) document,
-rasterized locally, never sent to any external service:
+In this Generate path, each release also gets a cover image, created inline in this same loop right before that
+release's own `publish-entry` call. In Codex, the dominant artwork MUST come from the native
+image-generation tool as a persisted raster source; wireframes, hand-authored SVG, CSS drawings,
+and title-only placeholders are not covers. The deterministic compositor may add PRESS typography
+around that generated artwork, but it must never substitute for native image generation.
+The cover must carry a custom illustration or other meaningful visual material; a cover that just re-renders the title in large text is a failure.
 
 ```bash
 mktemp -d    # → record the absolute path, e.g. /var/folders/.../tmp.abc
@@ -415,24 +539,17 @@ Per release:
    returns the style guide, icon catalog, and up to 3 reference cover paths. **Read
    only the single most recent reference image** (image reads are the expensive part;
    open another only if you're genuinely unsure the new cover is distinct). On
-   `{"error": "style-guide-missing"}`: skip cover composition for this release entirely
-   and proceed straight to publish-entry with no `--cover` flag.
-   Never block publish on a missing style guide.
-2. **Compose** using ONLY this release's title/tags/summary/`## Shipped` text
-   (never the raw draft file, never `## Changelog`) plus the style guide and icon catalog. A
-   cover that just re-renders the title in large text is a failure — find the one
-   concrete mechanism this release is actually about (not the project name, not "a bug
-   fix") and draw ONE custom inline-SVG illustration of it as the dominant visual
-   element; title/kicker stay secondary; two releases should never produce visually
-   similar covers. Follow the style guide's hero-zone grid contract: the illustration
-   lives in a `#hero-zone` container at exactly `x:150 y:425 width:1300 height:400`
-   (render-cover mechanically enforces this), one of two slots (single centered hero,
-   or two-node before/after), interior points snapped to a 25px grid; catalog icons
-   never go inside `#hero-zone` (optional small accent glyph near the kicker only,
-   bottom edge above y:400). Write the document with the Write tool to
-   `'<abs-scratch>/<key>/<version>.html'` — full `<!DOCTYPE html>` document, sized
-   `html, body { margin:0; width:1600px; height:900px; }`, font referenced only as
-   `font-family: 'DevlogCoverFont', sans-serif`.
+   `{"error": "style-guide-missing"}`: stop this release and report that publication is
+   blocked. A release entry is not publishable without a cover and agent handoff.
+2. **Generate and compose.** Use ONLY this release's title/tags/summary/`## Shipped` text
+   (never the raw draft file, never `## Changelog`) plus the style guide and icon catalog to
+   brief the native image-generation tool. Request artwork only: one concrete mechanism,
+   no lettering, labels, numbers, logos, fake code, UI, wireframe, gradients, or watermark.
+   Persist and inspect the exact returned raster, then use `compose-art-cover` to add local
+   PRESS typography. Do not draw the dominant art as inline SVG or CSS. A cover that just
+   re-renders the title in large text is a failure. Match the established backfill look:
+   flat cream paper, monochrome technical engraving, black/gray ink, restrained crosshatching,
+   a quiet left field for the headline, and at most one small orange accent.
 3. **Rasterize.**
    `npx -y @natjswenson/devlog@latest render-cover '<abs-scratch>/<key>/<version>.html' --project '<key>' --slug '<version>' --out '<abs-scratch>'`
    The HTML is the source of truth and **survives the render**: to fix a visual
@@ -478,18 +595,20 @@ content on disk that the registry doesn't list is built right past, and the entr
 while every command in this skill reports success. Publishing a project's first entry is
 therefore a two-part job, and the CLI can only do the first part.
 
-When `firstEntryForProject` is true, **before the push**:
-
-1. Find the registry in the clone. It is a source file, not content — grep the site's
-   `src/` for the existing project keys (`grep -rn '<a-known-project-key>' <clone>/src`).
-   In an Astro/Next-style site it is typically a `PROJECTS` array the entry loader maps
-   over.
-2. Add the new project, matching the shape of the neighbouring rows exactly.
-3. **Build the site in the clone and confirm the route exists** (`npm ci && npx astro
-   build`, then check the output directory contains the new `<project>/<version>` path).
-   A registry edit that doesn't produce a route is not done.
-4. Run the site's own test suite if it has one, and commit the registry change together
-   with the content in the same push.
+Follow the [producer and website onboarding guide](#producer-and-website-onboarding)
+even before the first article. When `firstEntryForProject` is true, **before the push**:
+
+1. Inspect the current website branch and find its registry in the clone. Search the
+   site's `src/` for existing project keys with `rg`. An Astro/Next-style site typically
+   maps a `PROJECTS` array. Preserve a matching registration instead of adding a duplicate.
+2. For a new project, add the registry row and valid manifest in the same change,
+   matching neighboring rows. Never replace a populated manifest with an empty example.
+3. Build the site and confirm the project/article routes exist in its output. Run the
+   site's tests and check navigation, tag search, metadata, cover, feed and sitemap
+   behavior as described in the paired guide.
+4. Follow the site's own PR flow for registry/source/config/docs changes and link any
+   companion PR. Content publication alone does not authorize bypassing that flow;
+   do not report the route complete until the required website checks are observed.
 
 If you cannot find a registry, say so plainly rather than assuming there isn't one; the
 verification in Step 6 is what actually settles it.

package/bin/devlog.js

@@ -90,6 +90,10 @@ const log = {
   hint: (msg) => console.log(kleur.dim('  ' + msg)),
 };
 
+async function initPrompt(questions, options) {
+  return prompts(questions, options);
+}
+
 function readPackageVersion() {
   const pkg = JSON.parse(readFileSync(join(PACKAGE_ROOT, 'package.json'), 'utf8'));
   return pkg.version;
@@ -177,9 +181,10 @@ function detectProjectRemote(path) {
   return m ? m[1] : null;
 }
 
-async function confirmOverwrite(label, path) {
+async function confirmOverwrite(label, path, { autoConfirm = false } = {}) {
   if (!existsSync(path)) return true;
-  const { ok } = await prompts({
+  if (autoConfirm) return true;
+  const { ok } = await initPrompt({
     type: 'confirm',
     name: 'ok',
     message: `${label} already exists at ${path}. Overwrite?`,
@@ -296,7 +301,21 @@ async function promptForProject(defaults = {}) {
 }
 
 // ─── init ────────────────────────────────────────────────────────────────────
-async function cmdInit() {
+async function cmdInit(rest = []) {
+  const { values } = safeParseArgs({
+    args: rest,
+    options: {
+      host: { type: 'string', default: 'claude' },
+      yes: { type: 'boolean', default: false },
+    },
+    allowPositionals: false,
+  });
+  const host = values.host;
+  if (host !== 'claude' && host !== 'codex') {
+    log.err(`Unknown host "${host}". Use "claude" or "codex".`);
+    process.exit(2);
+  }
+
   log.info(kleur.bold('\ndevlog setup\n'));
   await preflight();
 
@@ -309,7 +328,12 @@ async function cmdInit() {
     voicePath: existsSync(GHOSTWRITER_VOICE_DIR) ? GHOSTWRITER_VOICE_DIR : '',
   };
 
-  const answers = await prompts([
+  const answers = values.yes ? {
+    gitAuthor: defaults.gitAuthor,
+    githubUser: defaults.githubUser,
+    targetRepoName: defaults.targetRepoName,
+    voicePath: '',
+  } : await initPrompt([
     { type: 'text', name: 'gitAuthor', message: 'Your name (retained for backward compatibility; not currently rendered on entries):', initial: defaults.gitAuthor, validate: VALIDATORS.gitAuthor },
     { type: 'text', name: 'githubUser', message: 'Your GitHub username:', initial: defaults.githubUser, validate: VALIDATORS.githubUser },
     { type: 'text', name: 'targetRepoName', message: 'Name of the repo where dev logs will be published:', initial: defaults.targetRepoName, validate: VALIDATORS.targetRepoName },
@@ -318,24 +342,26 @@ async function cmdInit() {
 
   // Optionally register projects in a loop. First time defaults to "yes".
   const projects = [];
-  let firstPrompt = true;
-  for (;;) {
-    const { add } = await prompts({
-      type: 'confirm',
-      name: 'add',
-      message: firstPrompt ? 'Register a project now?' : 'Register another project?',
-      initial: firstPrompt,
-    }, { onCancel: () => process.exit(1) });
-    firstPrompt = false;
-    if (!add) break;
-    const p = await promptForProject();
-    if (projects.find((x) => x.key === p.key)) {
-      log.warn(`Skipped (duplicate key): ${p.key}`);
-      continue;
+  if (!values.yes) {
+    let firstPrompt = true;
+    for (;;) {
+      const { add } = await initPrompt({
+        type: 'confirm',
+        name: 'add',
+        message: firstPrompt ? 'Register a project now?' : 'Register another project?',
+        initial: firstPrompt,
+      }, { onCancel: () => process.exit(1) });
+      firstPrompt = false;
+      if (!add) break;
+      const p = await promptForProject();
+      if (projects.find((x) => x.key === p.key)) {
+        log.warn(`Skipped (duplicate key): ${p.key}`);
+        continue;
+      }
+      if (p.tagPrefix === 'v') delete p.tagPrefix;
+      projects.push(p);
+      log.ok(`Registered: ${p.key}`);
     }
-    if (p.tagPrefix === 'v') delete p.tagPrefix;
-    projects.push(p);
-    log.ok(`Registered: ${p.key}`);
   }
 
   const targetRepo = `${answers.githubUser}/${answers.targetRepoName}`;
@@ -367,9 +393,16 @@ async function cmdInit() {
   log.info(`  Branch:         ${config.branch}`);
   log.info(`  Voice profile:  ${config.voicePath || '(ghostwriter if present, else bundled default)'}`);
   log.info(`  Projects:       ${config.projects.length === 0 ? '(none — add later with `devlog add-project`)' : config.projects.map((p) => p.key).join(', ')}`);
-  log.info(`  Skill location: ${CONFIG_DIR}`);
+  if (host === 'claude') {
+    log.info(`  Skill location: ${CONFIG_DIR}`);
+  } else {
+    log.info(`  Personal data:  ${CONFIG_DIR}`);
+    log.info('  Host:           Codex (marketplace plugin remains authoritative)');
+  }
 
-  const { proceed } = await prompts({ type: 'confirm', name: 'proceed', message: 'Continue?', initial: true }, { onCancel: () => process.exit(1) });
+  const { proceed } = values.yes
+    ? { proceed: true }
+    : await initPrompt({ type: 'confirm', name: 'proceed', message: 'Continue?', initial: true }, { onCancel: () => process.exit(1) });
   if (!proceed) process.exit(0);
   log.info('');
 
@@ -392,24 +425,26 @@ async function cmdInit() {
     log.ok(`Created ${CONFIG_DIR}`);
   }
 
-  if (await confirmOverwrite('SKILL.md', SKILL_DEST)) {
-    // These are versioned instructions, not personal config/voice/style files.
-    // Install references with the entrypoint so standalone hosts can resolve them.
-    const references = join(PACKAGE_ROOT, 'references');
-    const referenceDest = join(CONFIG_DIR, 'references');
-    mkdirSync(referenceDest, { recursive: true, mode: 0o700 });
-    for (const name of readdirSync(references)) {
-      if (name.endsWith('.md') && statSync(join(references, name)).isFile()) {
-        copyFileSync(join(references, name), join(referenceDest, name));
+  if (host === 'claude') {
+    if (await confirmOverwrite('SKILL.md', SKILL_DEST, { autoConfirm: values.yes })) {
+      // These are versioned instructions, not personal config/voice/style files.
+      // Install references with the entrypoint so standalone hosts can resolve them.
+      const references = join(PACKAGE_ROOT, 'references');
+      const referenceDest = join(CONFIG_DIR, 'references');
+      mkdirSync(referenceDest, { recursive: true, mode: 0o700 });
+      for (const name of readdirSync(references)) {
+        if (name.endsWith('.md') && statSync(join(references, name)).isFile()) {
+          copyFileSync(join(references, name), join(referenceDest, name));
+        }
       }
+      copyFileSync(SKILL_SRC, SKILL_DEST);
+      log.ok(`Installed SKILL.md → ${SKILL_DEST}`);
+    } else {
+      log.warn('Skipped SKILL.md');
     }
-    copyFileSync(SKILL_SRC, SKILL_DEST);
-    log.ok(`Installed SKILL.md → ${SKILL_DEST}`);
-  } else {
-    log.warn('Skipped SKILL.md');
   }
 
-  if (await confirmOverwrite('config.json', CONFIG_PATH)) {
+  if (await confirmOverwrite('config.json', CONFIG_PATH, { autoConfirm: values.yes })) {
     atomicWriteJSON(CONFIG_PATH, config);
     log.ok(`Wrote config → ${CONFIG_PATH}`);
   }
@@ -423,7 +458,7 @@ async function cmdInit() {
   for (const [src, dest] of [['voice-profile.example.md', 'voice-profile.md'], ['voice-notes.example.md', 'voice-notes.md']]) {
     const s = join(VOICE_SRC_DIR, src);
     const d = join(VOICE_DEST_DIR, dest);
-    if (existsSync(s) && (await confirmOverwrite(`voice/${dest}`, d))) {
+    if (existsSync(s) && (await confirmOverwrite(`voice/${dest}`, d, { autoConfirm: values.yes }))) {
       copyFileSync(s, d);
       log.ok(`Installed voice/${dest} → ${d}`);
     }
@@ -436,19 +471,19 @@ async function cmdInit() {
   }
   const styleGuideSrc = join(IMAGE_STYLE_SRC_DIR, 'style-guide.example.md');
   const styleGuideDest = join(IMAGE_STYLE_DEST_DIR, 'style-guide.md');
-  if (existsSync(styleGuideSrc) && (await confirmOverwrite('image-style/style-guide.md', styleGuideDest))) {
+  if (existsSync(styleGuideSrc) && (await confirmOverwrite('image-style/style-guide.md', styleGuideDest, { autoConfirm: values.yes }))) {
     copyFileSync(styleGuideSrc, styleGuideDest);
     log.ok(`Installed image-style/style-guide.md → ${styleGuideDest}`);
   }
   const fontSrc = join(IMAGE_STYLE_SRC_DIR, 'font.ttf');
   const fontDest = join(IMAGE_STYLE_DEST_DIR, 'font.ttf');
-  if (existsSync(fontSrc) && (await confirmOverwrite('image-style/font.ttf', fontDest))) {
+  if (existsSync(fontSrc) && (await confirmOverwrite('image-style/font.ttf', fontDest, { autoConfirm: values.yes }))) {
     copyFileSync(fontSrc, fontDest);
     log.ok(`Installed image-style/font.ttf → ${fontDest}`);
   }
   const iconsSrc = join(IMAGE_STYLE_SRC_DIR, 'icons.md');
   const iconsDest = join(IMAGE_STYLE_DEST_DIR, 'icons.md');
-  if (existsSync(iconsSrc) && (await confirmOverwrite('image-style/icons.md', iconsDest))) {
+  if (existsSync(iconsSrc) && (await confirmOverwrite('image-style/icons.md', iconsDest, { autoConfirm: values.yes }))) {
     copyFileSync(iconsSrc, iconsDest);
     log.ok(`Installed image-style/icons.md → ${iconsDest}`);
   }
@@ -470,7 +505,13 @@ async function cmdInit() {
 
   log.info('\n' + kleur.bold().green('Setup complete.') + '\n');
   log.info('Next steps:');
-  if (config.projects.length === 0) {
+  if (host === 'codex') {
+    log.info('  1. The marketplace-installed Codex plugin remains the authoritative $devlog entrypoint.');
+    log.info('  2. To install the plugin in Codex:');
+    log.info(`     ${kleur.cyan('codex plugin marketplace add <marketplace>')}`);
+    log.info(`     ${kleur.cyan('codex plugin add devlog@claude-skills')}`);
+    log.info(`  3. Preview locally: ${kleur.cyan('npx @natjswenson/devlog preview')}`);
+  } else if (config.projects.length === 0) {
     log.info(`  1. Add a project: ${kleur.cyan('npx @natjswenson/devlog add-project')}`);
     log.info('  2. Tag a release in the project (e.g. `git tag v0.1.0`)');
     log.info(`  3. In Claude Code, run: ${kleur.cyan('/devlog')}`);
@@ -1126,15 +1167,18 @@ async function cmdCommitCovers(rest) {
   // routinely runs well after the backfill/review session that produced the staging dir,
   // and reusing an hours-or-days-old clone would risk mutating a manifest that's since
   // moved on.
-  const cloneDir = mkdtempSync(join(tmpdir(), 'devlog-commit-covers-'));
+  const repoDir = mkdtempSync(join(tmpdir(), 'devlog-commit-covers-'));
   const branch = config.branch || 'main';
   const cloneUrl = `https://github.com/${config.targetRepo}.git`;
-  const cloneResult = spawnSync('git', ['clone', '--depth=1', '--branch', branch, cloneUrl, cloneDir], { encoding: 'utf8' });
+  const cloneResult = spawnSync('git', ['clone', '--depth=1', '--branch', branch, cloneUrl, repoDir], { encoding: 'utf8' });
   if (cloneResult.status !== 0) {
-    rmSync(cloneDir, { recursive: true, force: true });
+    rmSync(repoDir, { recursive: true, force: true });
     emitJSON({ error: 'clone-failed', message: cloneResult.stderr || 'git clone failed' }, 1);
     return;
   }
+  // Manifests live under the configured content root; git operations still run
+  // from the repository root.
+  const cloneDir = join(repoDir, config.targetDir || '');
 
   const summary = { written: [], skipped: [], failed: [], missingManifest: [] };
   let bulkForceOverwriteCount = 0;
@@ -1199,20 +1243,20 @@ async function cmdCommitCovers(rest) {
       ['commit', '-m', `chore(devlog): add ${summary.written.length} cover image(s)`],
     ];
     for (const args of steps) {
-      const r = spawnSync('git', ['-C', cloneDir, ...args], { encoding: 'utf8' });
+      const r = spawnSync('git', ['-C', repoDir, ...args], { encoding: 'utf8' });
       if (r.status !== 0) {
         emitJSON({ ok: false, ...summary, bulkForceOverwriteCount, error: 'git-commit-failed', message: r.stderr }, 1);
         return;
       }
     }
-    const push = spawnSync('git', ['-C', cloneDir, 'push', '--no-tags', 'origin', branch], { encoding: 'utf8' });
+    const push = spawnSync('git', ['-C', repoDir, 'push', '--no-tags', 'origin', branch], { encoding: 'utf8' });
     if (push.status !== 0) {
       emitJSON({ ok: false, ...summary, bulkForceOverwriteCount, error: 'git-push-failed', message: push.stderr }, 1);
       return;
     }
   }
 
-  rmSync(cloneDir, { recursive: true, force: true });
+  rmSync(repoDir, { recursive: true, force: true });
   emitJSON({ ok: summary.failed.length === 0, ...summary, bulkForceOverwriteCount });
 }
 
@@ -1330,7 +1374,7 @@ function printHelp() {
 ${kleur.bold('@natjswenson/devlog')} v${readPackageVersion()} — release dev log generator
 
 Setup & config:
-  ${kleur.cyan('npx @natjswenson/devlog init')}                     One-time setup: create your dev-log repo, install the skill, write config
+  ${kleur.cyan('npx @natjswenson/devlog init [--host claude|codex] [--yes]')}  One-time setup (defaults to Claude); Codex plugin is installed separately; --yes is non-interactive
   ${kleur.cyan('npx @natjswenson/devlog add-project')}              Register a project (interactive; add --yes --path <p> for non-interactive)
   ${kleur.cyan('npx @natjswenson/devlog remove-project <key> --yes')}  Unregister a project (entries stay published)
   ${kleur.cyan('npx @natjswenson/devlog set <field> <value>')}      Update one config field (${SETTABLE_FIELDS.join(', ')})
@@ -1385,7 +1429,7 @@ if (isMain) {
   const rest = process.argv.slice(3);
   switch (arg) {
     case 'init':
-      cmdInit();
+      cmdInit(rest);
       break;
     case 'add-project':
       cmdAddProject(rest);

package/image-style/style-guide.example.md

@@ -11,8 +11,9 @@ are how a from-scratch visual language stays consistent from post to post.
 
 ## What you're composing
 
-A single self-contained HTML document (inline `<style>`, inline SVG for any artwork) that
-renders, at exactly 1600×900px, as a cover image for one dev log entry. Compose from these
+A single PRESS editorial cover that renders, at exactly 1600×900px, as a cover image for
+one dev log entry. In Codex, the dominant image is a native generated raster illustration;
+the local compositor adds the typography and layout. Compose from these
 fields only — never open the post's raw markdown file, never reference any section other
 than `## Shipped` (no `## Changelog`, no gotchas, no sources):
 - `title`
@@ -34,11 +35,11 @@ Before writing any HTML, do this thinking step explicitly:
    key that doesn't fit, a git tag being distrusted like any other user input, one broken
    link in a chain, a filter separating signal from noise, a clock catching a stale
    timestamp, two paths diverging and one being cut off.
-3. Design ONE illustration — built from inline SVG shapes (lines, arcs, polygons,
-   simple geometric forms) — that depicts that concept. Not a photo, not a stock icon,
-   not a screenshot: a small original line-art scene, **editorial line art in ink with
-   sparing orange**, in the spirit of a newspaper diagram or a technical schematic, using
-   only the palette below.
+3. Design ONE native raster illustration that depicts that concept. Not a photo, stock
+   icon, screenshot, UI, wireframe, or geometric placeholder: a detailed original
+   **monochrome technical engraving in black and warm gray ink on flat cream paper**, in
+   the spirit of a historical engineering plate or newspaper field illustration, with at
+   most one small vermilion/orange focal accent. The art must look printed, not painterly.
 4. That illustration is the dominant visual element of the cover — roughly half the
    canvas, not a thumbnail in the corner. Title, kicker, and summary text support it;
    they do not replace it.
@@ -151,10 +152,10 @@ For the two-node slot specifically: the accent icon's presence must not be read
   `DevlogCoverFont` finishes loading. That's resolving a name the browser already has, not
   embedding or fetching a file — no different in kind from the fallback this rule already
   requires.
-- No external resources of any kind — no `<link>`, no `@import`, no remote `<img src>`,
-  no web fonts, no raster images. All artwork is inline SVG built from basic shapes
-  (`<path>`, `<circle>`, `<rect>`, `<line>`, `<polygon>`, `<polyline>`) — everything must
-  be inline HTML/CSS/SVG, hand-composed, not fetched or embedded from anywhere.
+- The final cover must be self-contained and offline-renderable. Native raster artwork is
+  persisted locally and embedded by `compose-art-cover`; no remote images or web fonts.
+  Typography is rendered locally and the generated artwork is never replaced by inline
+  SVG, CSS shapes, a wireframe, or a title-only placeholder.
 
 ## Visual direction
 
@@ -165,7 +166,7 @@ site, not a marketing graphic and not a repeated template.
 
 ### Palette
 
-<!-- >>> press:palette v0.9.0 sha256:5904c52d4168 GENERATED by @natjswenson/press, do not edit -->
+<!-- >>> press:palette v0.11.0 sha256:5904c52d4168 GENERATED by @natjswenson/press, do not edit -->
 - **Paper** `#F5F0E6` — Warm cream. Flat — never gradiented, never textured.
 - **Ink** `#181510` — Near-black. Text, headlines, and every structural rule.
 - **Dim** `#6E675C` — Muted secondary text; the serif commentary voice's color.
@@ -176,9 +177,10 @@ site, not a marketing graphic and not a repeated template.
   survives, and only inside a terminal element. Never on paper.
 <!-- <<< press:palette -->
 
-Prefer flat, limited color and solid/line fills over gradients or smooth shading — the
-render is compressed with lossy PNG palette quantization afterward, and gradients band
-visibly under that compression while flat fills don't.
+Prefer flat, limited color and solid/line fills over gradients or smooth shading. Native
+art should be predominantly cream paper plus black/gray engraving lines, with no broad
+color wash, no saturated palette, and no painterly digital lighting. The only bright color
+is the single small orange accent permitted by the accent law below.
 
 ### The accent law, carried to covers
 
@@ -304,7 +306,8 @@ summary as on-image text.
   cursor, no bare `_` suffix, no stray `$` prompt as decoration. The dark palette now
   belongs to exactly one place, the `.term` panel, and only when it's real code.
 - Don't embed a photograph, stock image, or anything requiring an external fetch — the
-  illustration is drawn from inline SVG primitives, not sourced from anywhere.
+  illustration is native-generated raster artwork persisted locally and embedded by the
+  compositor, never a hand-authored SVG substitute.
 - Don't reference any font file other than the bundled `'DevlogCoverFont'` — the serif
   and display voices lean on this rendering host's own system fonts, never a file you
   fetch or embed yourself.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@natjswenson/devlog",
-  "version": "0.14.0",
+  "version": "0.14.2",
   "description": "Release dev log generator — Claude Code skill + preview app for publishing version-release dev logs, written in your voice, to your site",
   "license": "MIT",
   "author": "Nate Swenson",

package/skill-invariants.json

@@ -72,9 +72,9 @@
       "rationale": "Cover composition must draw only from title/tags/summary/## Shipped \u2014 never the raw draft or Changelog \u2014 losing this line reopens off-scope content leaking into an auto-composed image."
     },
     {
-      "id": "cover-never-blocks-publish",
-      "pattern": "[Nn]ever block[\\s\\S]{0,10}publish on a missing style guide",
-      "rationale": "A missing/uninstalled style guide must degrade gracefully (no cover this run), never abort the whole publish."
+      "id": "cover-required-before-publish",
+      "pattern": "publication is[\\s\\S]{0,5}blocked",
+      "rationale": "A missing/uninstalled style guide must stop the release so Generate mode cannot publish an entry without its required cover."
     },
     {
       "id": "cover-review-gate",