emdash-emit 0.1.7 → 0.1.9

package/README.md

@@ -32,7 +32,7 @@
   - [Media Management & Upload Workflow](#media-management--upload-workflow)
 - [🤖 The Golden Path for AI & Humans (4-Step Cycle)](#-the-golden-path-for-ai--humans-4-step-cycle)
   - [The 4-Step Authoring Cycle](#the-4-step-authoring-cycle)
-  - [Preflight Safety Guardrails (G1–G9)](#preflight-safety-guardrails-g1g9)
+  - [Preflight Safety Guardrails (G1–G12)](#preflight-safety-guardrails-g1g12)
 - [🛠 CLI Command Reference](#-cli-command-reference)
   - [`emit init`](#emit-init)
   - [`emit profile`](#emit-profile)
@@ -78,10 +78,10 @@ To prevent user expectations from misaligning with the tool's purpose, it is imp
 
 * **What Emit IS (Core Goal)**:
   * An **active authoring and editing workbench (Staging Desk)** where human authors and AI coding agents collaborate seamlessly.
-  * A tool focused on drafting, reviewing, polishing, diffing, and publishing current and recent articles with strict safety guards.
+  * A tool focused on drafting, reviewing, polishing, diffing, and publishing current and recent articles with strict safety guards—including **automatic offline draft image upload** (`media/drafts/`) for images referenced in the article being pushed.
 * **What Emit is NOT (Non-Goals)**:
-  * **Not a full-site database archiver / backup dumper**: Emit is not designed to clone an entire 15-year history of 20,000 blog posts onto your laptop.
-  * **Not an offline bulk mass-migration converter**: Emit does not perform batch transformation across thousands of historical posts at once.
+  * **Not a full-site database archiver / backup dumper**: Emit is not designed to clone an entire 15-year history of 20,000 blog posts or an entire multi-gigabyte media library onto your laptop.
+  * **Not an offline bulk mass-migration converter**: Emit does not perform batch transformation across thousands of historical posts or bulk media migrations at once.
 
 If your site contains thousands of articles, they remain safe, searchable, and intact in your Cloudflare D1 database. Emit only pulls the active working set into your local workspace, keeping your directory clean and searches instant. Need to edit a specific older article outside the active window? Simply pull it on demand using `emit pull <article-id>`.
 
@@ -116,7 +116,7 @@ By leveraging Node.js 22's built-in `node:sqlite` module (`DatabaseSync`), Emit
 
 To prevent concurrent race conditions when multiple authors or AI agents collaborate:
 
-* Emit acquires a distributed 7-minute lease via `POST /api/v1/content/lock` before writing to remote articles, with automatic heartbeats and `try/finally` release guarantees.
+* Emit acquires a distributed 7-minute lease via `POST /_emdash/api/content/{collection}/{id}/lock` before writing to remote articles, with automatic heartbeats and `try/finally` release guarantees.
 * If concurrent edits occur, Emit utilizes a **Hybrid 3-Way Merge** engine (`node-diff3`), merging YAML frontmatter fields and Markdown body text independently.
 
 ---
@@ -193,6 +193,9 @@ emit profile add my-blog \
 > [!NOTE]
 > Profiles are securely stored with `0600` permissions at `~/.config/emit/profiles.yaml` (on macOS / Linux) or `%USERPROFILE%\.config\emit\profiles.yaml` (on Windows).
 
+> [!NOTE]
+> **`emit profile add` updates in place.** Re-running it with only `--origin` (for example after rotating a domain) keeps the stored `--token` and the `--workspace` link that `emit init` created, and reports `Kept the existing token and workspace link`. Pass `--token`/`--workspace` explicitly to replace them; an empty `--token ''` clears the credential on purpose.
+
 ### 2. Initialize a Workspace
 
 Navigate to your local repository directory and initialize it:
@@ -202,7 +205,7 @@ cd /path/to/local/blog-repo
 emit init
 ```
 
-This creates the `.emit/` directory with a default `config.json` and initializes the local baseline cache SQLite database (`.emit/cache.db`).
+This creates the `.emit/` directory with `config.json` (inheriting `origin` from your resolved profile when `--origin` is omitted, and automatically linking `workspace` back into `~/.config/emit/profiles.yaml` unless `--no-link` is passed) and initializes the local baseline cache SQLite database (`.emit/cache.db`).
 
 ### 3. Multi-Site Management (Directory-Driven & Zero Friction)
 
@@ -222,11 +225,60 @@ emit profile list
 ```
 
 **How Automatic Profile Resolution Works:**
-1. **Directory-Driven Auto Detection (Recommended)**: When you `cd ~/blogs/personal` and run `emit pull`, `emit push`, or launch an AI agent, Emit detects your current folder and automatically uses the `personal` profile. When you `cd ~/blogs/work`, it seamlessly connects to `work`.
+1. **Directory-Driven Auto Detection (Recommended)**: When you `cd ~/blogs/personal` and run `emit pull`, `emit push`, or launch an AI agent, Emit detects your current folder and automatically uses the `personal` profile. When you `cd ~/blogs/work`, it seamlessly connects to `work`. Directory comparison is symlink-safe (`fs.realpathSync`), so a workspace reached through a symlinked path (or a macOS `/tmp`-style alias) still resolves to the right profile.
 2. **Explicit Profile Flag**: You can explicitly specify `--profile <name>` (or pass `profile: "<name>"` in MCP) from any directory to override automatic detection.
 3. **Ambiguity Safeguard**: If you run a command outside of any registered workspace and omit `--profile`, Emit aborts with an `AmbiguousProfileError` instead of guessing or silently pushing to the wrong site.
 
-### 4. Recommended `.gitignore`
+### 4. Authentication Resolution Order & Token Auto-Refresh
+
+Emit resolves authentication credentials using a strict 4-tier priority chain (`src/client/auth.ts`):
+
+1. **Environment Variables (`EMDASH_TOKEN` or `EMDASH_API_TOKEN`)**: Highest priority; ideal for CI/CD pipelines and one-off overrides. `EMDASH_ORIGIN` (and `EMDASH_WORKSPACE`) are read here as well and documented under [Origin Resolution Precedence](#origin-resolution-precedence).
+2. **Site Profile Registry (`~/.config/emit/profiles.yaml`)**: Matched via `--profile <name>` (or MCP `profile`), current workspace directory auto-detection, or a single registered profile.
+3. **EmDash CLI Credentials (`~/.config/emdash/auth.json`)**: Fallback when no token is configured in the profile.
+4. **Emit Custom Credentials (`~/.config/emit/credentials.json`)**: Final fallback.
+
+**Automatic OAuth Token Refresh on HTTP 401 (`src/client/http.ts`)**:
+When credentials include a `refresh_token` (such as OAuth sessions in `~/.config/emdash/auth.json` or `~/.config/emit/credentials.json`) and a request returns `401 Unauthorized`, Emit automatically exchanges the `refresh_token` at `POST /_emdash/api/auth/token` (`grant_type: "refresh_token"`), persists the refreshed token back to `auth.json` when applicable, and transparently retries the request once.
+
+#### Origin Resolution Precedence
+
+The target instance (`origin`) is resolved by one shared function (`resolveOriginPriority()` in `src/cli/context.ts`, reused by the MCP server) so CLI and MCP always agree:
+
+1. **Explicitly selected profile** — `--profile <name>` (or MCP `profile: "<name>"`)
+2. **`EMDASH_ORIGIN`** — overrides an *implicitly* resolved profile so CI/staging overrides actually take effect
+3. **Auto-resolved profile** — current-directory match, unique origin match, or the single registered profile
+4. **Resolved auth origin** — carried by `~/.config/emdash/auth.json` / `~/.config/emit/credentials.json`
+5. **Workspace `.emit/config.json`** → then the `https://example.com` sentinel default
+
+> [!NOTE]
+> Every silent override is surfaced as a `⚠️ Warning` naming the **real source** of each value (`.emit/config.json` values are never mislabeled as `EMDASH_ORIGIN` or the reverse). When you select `--profile` explicitly, `EMDASH_ORIGIN` is ignored **and reported**. Comparisons ignore trailing slashes. `emit init` follows the same ranking (`--origin` > `EMDASH_ORIGIN` > auto-resolved profile) and refuses to link the workspace to a profile whose origin does not match the initialized origin.
+
+### 5. Workspace Configuration (`.emit/config.json`)
+
+Running `emit init` generates `.emit/config.json` with the following keys (`src/utils/config.ts`):
+
+```json
+{
+  "origin": "https://your-blog.example.com",
+  "defaultCollection": "posts",
+  "defaultLocale": "ja",
+  "postsSyncLimit": 100,
+  "mediaSyncLimit": 300,
+  "concurrency": 8
+}
+```
+
+| Key | Default | Description |
+| --- | --- | --- |
+| `origin` | `"https://example.com"` | Base URL of the target EmDash instance, exactly as written to disk. It is never rewritten in-memory by `EMDASH_ORIGIN`; see [Origin Resolution Precedence](#origin-resolution-precedence) for how the effective origin is chosen |
+| `defaultCollection` | `"posts"` | Default content collection when `--collection` is omitted |
+| `defaultLocale` | `"ja"` | Default locale used when scaffolding new drafts via `emit new` / `sync_new` |
+| `postsSyncLimit` | `100` | Sliding window size for batch article pulls (when `status: all`, fetches up to `postsSyncLimit` `published` + up to `postsSyncLimit` `draft` articles in parallel; also supports legacy `syncLimit` fallback) |
+| `mediaSyncLimit` | `300` | Default maximum items fetched by `emit pull-media` / `sync_pull_media` |
+| `concurrency` | `8` | Parallel HTTP fetch concurrency during batch pulls |
+
+### 6. Recommended `.gitignore`
 
 When tracking your local blog repository with Git, use the following recommended `.gitignore` configuration:
 
@@ -256,9 +308,8 @@ tmp/
 > [!TIP]
 > * `.emit/cache.db*` **must be excluded** from Git because it is a machine-local SQLite tracking database.
 > * `.emit/config.json` **can be safely committed** to Git because it contains workspace configuration (origin URL, default collections), while sensitive authentication tokens remain securely isolated in `~/.config/emit/profiles.yaml`.
-> * `media/*.yaml` metadata files can be committed to Git to track asset metadata alongside your Markdown articles.
-> 
-> 
+> * `media/*.yaml` metadata files can be committed to Git to track asset metadata (`storageKey`, `contentHash`, `status`, dimensions) alongside your Markdown articles.
+> * **Local-First Git Tracking for `media/`**: If you use your Git repository as a self-contained Local-First source of truth (including offline drafts in `media/drafts/`), keep `media/` tracked in Git (or via Git LFS). If you treat Cloudflare R2 as the sole binary store and want a lightweight Git repo, uncomment the `media/*.jpg` ignore rules above while keeping `media/*.yaml` tracked.
 
 ---
 
@@ -271,68 +322,104 @@ your-blog/
 ├── .emit/                          # [Hidden System Directory - Do not edit manually]
 │   ├── config.json                 # Workspace configuration (origin, postsSyncLimit, etc.)
 │   └── cache.db                    # SQLite baseline tracking & hash database
-├── categories/                     # Category definition files
-│   ├── tech.yaml
-│   └── lifestyle.yaml
-├── tags/                           # Tag definition files
-│   ├── typescript.yaml
-│   └── ai.yaml
-├── media/                          # Media files and metadata
-│   ├── 01M6ABCDEF.jpg
-│   └── 01M6ABCDEF.jpg.yaml
-└── posts/                          # Local Markdown Articles
-    ├── draft/                      # Draft articles (<yyyyMMdd>_<ulid>-<slug>.md)
-    │   └── 20261104_01M6...-my-new-post.md
-    └── published/                  # Live published articles (<yyyyMMdd>_<ulid>-<slug>.md)
-        └── 20261015_01M5...-getting-started.md
-
-```
+├── categories/                     # Category definition files (<id>-<label>.yaml)
+│   ├── 01M6CAT1-Tech.yaml
+│   └── 01M6CAT2-カメラ.yaml
+├── tags/                           # Tag definition files (<id>-<label>.yaml)
+│   ├── 01M6TAG1-Typescript.yaml
+│   └── 01M6TAG2-Ai.yaml
+├── media/                          # Media files and companion metadata (<yyyyMMdd>_<id>-<name>.<ext>)
+│   ├── drafts/                     # Staging folder for offline draft images (auto-uploaded on push)
+│   │   └── sunset.png
+│   ├── 20261101_01M6ABCDEF-header.jpg
+│   └── 20261101_01M6ABCDEF-header.yaml
+└── posts/                          # Local Markdown Articles (<yyyyMMdd>_<ulid>-<title>.md)
+    ├── draft/                      # Draft articles (named after title; falls back to slug if empty)
+    │   └── 20261104_01M6...-My-New-Post.md
+    ├── published/                  # Live published articles
+    │   └── 20261015_01M5...-Getting-Started.md
+    └── conflicts/                  # Read-only rescue copies of divergent local content (written by pull; never pushed or pruned)
+        └── 20261101_01M5...-Getting-Started.conflict.md
+
+```
+
+### Local SQLite Cache (`.emit/cache.db`)
+
+Emit maintains a local SQLite database via Node.js built-in `node:sqlite` (`src/db/cache.ts`) with 5 tables:
+
+| Table | Purpose |
+| --- | --- |
+| `entries` | Caches the latest remote JSON envelope and revision (`rev`) for each synced article |
+| `base_snapshots` | Stores the baseline Markdown body and baseline frontmatter at the last synced revision to power Hybrid 3-Way Merge (`frontmatter_yaml` holds a **JSON-encoded** `Frontmatter` object, not YAML text) |
+| `sync_state` | Tracks each article's workspace-relative file path and SHA-256 content hash to detect local modifications (`synced` vs `modified` vs `untracked`, plus `invalid` when YAML frontmatter fails parsing; `invalid` files are excluded from `emit push --all`, cached `invalid` files are automatically self-healed on batch `emit pull` / `sync_pull`, and uncached `invalid` files outside the sliding window can be repaired via `emit pull <ULID>` or `sync_pull(id: "<ULID>")`) |
+| `bylines` | Caches remote author records (`id`, `slug`, `display_name`, `is_guest`) synced automatically via `/_emdash/api/mcp` (`byline_list`) on pull, enabling slug ⇔ ULID resolution and default author selection |
+| `media_state` | Tracks offline draft image uploads (`local_hash`, `media_id`, `storage_key`, `url`, `workspace_path`, `status`: `pending` \| `uploaded` \| `ready` \| `failed`) for idempotency, retry recovery, and cross-article asset reuse |
 
 ---
 
 ## 📝 Markdown & YAML Frontmatter Specification
 
-Each article is stored as a Markdown file with a standard YAML frontmatter header.
+Each article is stored as a Markdown file with a validated YAML frontmatter header (`FrontmatterSchema` in `src/utils/frontmatter.ts`).
 
 ### Frontmatter Schema
 
 ```yaml
 ---
-id: 01M6ABCDEF1234567890123456     # EmDash canonical ULID (auto-generated; DO NOT EDIT)
+id: 01M6ABCDEF1234567890123456     # 26-char canonical ULID (auto-generated; DO NOT EDIT)
+slug: building-ai-powered-cms-tools
 title: "Building AI-Powered CMS Tools"
-slug: "building-ai-powered-cms-tools"
-status: draft                       # Status: "draft" or "published"
-publishedAt: null                   # ISO 8601 timestamp (null for drafts)
-updatedAt: "2026-11-04T12:00:00.000Z"
-excerpt: "A deep dive into building autonomous content workflows with EmDash and Emit."
-featuredImage: "01M6MEDIA123456"    # Media ULID or null
-categories:                         # Slugs matching definitions in categories/*.yaml
-  - tech
-tags:                               # Slugs matching definitions in tags/*.yaml
-  - typescript
-  - ai
-customFields:                       # Optional custom field definitions
-  canonicalUrl: ""
+collection: posts                  # Target collection (defaults to "posts")
+status: draft                      # "draft" or "published" (defaults to "draft")
+publishedAt: null                  # ISO 8601 timestamp string (e.g. "2026-11-04T12:00:00.000Z") or null
+locale: ja                         # Locale code (defaults to "ja")
+featuredImage: "01M67P0MBMJQQXH2K95HHCYRYB" # Optional: 26-char media ULID (uppercase-normalized) or null
+taxonomies:                        # Map of taxonomy key -> array of term slugs (or canonical term ULIDs)
+  categories:
+    - tech
+  tags:
+    - typescript
+    - ai
+seo:                               # Optional SEO metadata block
+  title: null                      # Custom SEO title string or null
+  description: null                # Meta description string or null
+  canonical: null                  # Absolute URL (e.g. "https://example.com/posts/...") or null
+  noIndex: false                   # Boolean (optional)
+  image: null                      # SEO image string or null
+bylines:                           # Author byline slugs (resolved via cached bylines table)
+  - aroooy
 ---
 
 Markdown body begins here...
 
 ```
 
+> [!IMPORTANT]
+> **Schema Validation & Serialization Rules (`src/utils/frontmatter.ts`)**:
+> * **Always nest categories and tags under `taxonomies:`**: `parseMarkdown()` validates frontmatter with Zod (`FrontmatterSchema`), which strips unknown top-level keys, and `serializeMarkdown()` regenerates the YAML header on every pull and push. Writing `categories:` or `tags:` at the top level will silently discard them without triggering Preflight Guard G4. `taxonomies` accepts `categories`, `tags`, and any additional custom taxonomy keys defined in EmDash (`z.record(z.array(z.string()))`).
+> * **`seo.canonical` must be an absolute URL**: Validated via `z.string().url().nullable().optional()`. Relative paths such as `"/posts/my-slug"` will fail frontmatter parsing; always specify a full `https://...` URL or `null`.
+> * **Author `bylines` auto-selection**: When scaffolding with `emit new` / `sync_new` without `--byline` / `byline`, Emit populates `bylines` with the first cached non-guest author ordered by `slug ASC` from `.emit/cache.db`. On single-author sites this is always your author slug; on multi-author sites, pass `-b, --byline <slug>` (or `byline` in MCP) or edit `bylines:` in frontmatter explicitly.
+> * **`id` and `featuredImage` normalization**: `id` must be an exact 26-character ULID. `featuredImage` values matching a 26-character Crockford base32 ULID are normalized to uppercase automatically.
+
 ### Critical Content Rules
 
 1. **Do Not Duplicate the Title in the Body**:
    - The article title is managed by the `title:` field in the frontmatter.
    - **Do not** add `# Article Title` as the first heading in the Markdown body. Doing so causes duplicate title displays on the site frontend. (Emit's preflight guard G7 will detect and automatically trim redundant top headings).
 2. **Taxonomy Slugs & Normalization**:
-   - Items under `categories:` and `tags:` should use existing slug names from `categories/` and `tags/` (e.g. `- tech`, `- nodejs`).
+   - Items under `taxonomies.categories` and `taxonomies.tags` should use existing slug names from `categories/*.yaml` and `tags/*.yaml` (e.g. `- tech`, `- nodejs`). Note that while taxonomy definition filenames include the ULID (`categories/<id>-<slug>.yaml`), the frontmatter entries use the **slug**.
    - If a valid term ULID is specified in the frontmatter, Emit automatically resolves it transparently to its corresponding slug for Preflight Guard G4 validation and maintains accurate term assignment on remote sync.
    - Do not duplicate the same term using both its slug and ULID within the same taxonomy (e.g. `[- tech, 01M6CAT1]`). Emit de-duplicates identical term assignments, but a slug and a ULID that resolve to **different** terms will both be assigned to the article.
-   - Never invent arbitrary IDs or invalid names; valid options are automatically displayed during `emit pull`, `emit pull-taxonomies`, `emit new`, `sync_pull`, `sync_pull_taxonomies`, and `sync_new`. Preflight Guard G4 strictly validates taxonomy terms before pushing.
+   - Never invent arbitrary IDs or invalid names; valid options are automatically displayed as hints during `emit pull`, `emit pull-taxonomies`, `emit new`, `sync_pull`, `sync_pull_taxonomies`, and `sync_new`. Hint lists are capped per command (with an `...and N more` marker), so the authoritative full list is always the `categories/` and `tags/` YAML files. Preflight Guard G4 strictly validates taxonomy terms before pushing.
 3. **Status Transitions**:
    - To publish a draft, update `status: published` in the frontmatter and execute `emit push <filePath> --allow-publish`.
    - Emit automatically updates the remote state and moves the file from `posts/draft/` to `posts/published/`.
    - **Never move or rename files manually using `mv`**.
+4. **Featured Image References**:
+   - `featuredImage` must be a 26-character canonical media ULID (e.g. `01M67P0MBMJQQXH2K95HHCYRYB`) or `null`. Emit normalizes the value to uppercase, so lowercase input is accepted and canonicalized on pull, merge, and push.
+   - To remove the hero image, set `featuredImage: null`. Omitting the field leaves the remote value untouched.
+   - When the referenced ULID matches the cached remote entry, Emit resends the original remote `featured_image` object verbatim (provider, `src`, `meta.storageKey`, dimensions, MIME type) so nothing is lost. When it does not match, Emit sends the bare `{ id: <ULID> }` and lets EmDash resolve the media record. **This contract is confirmed against a live EmDash instance:** `featured_image: { "id": "<ULID>" }` is accepted (HTTP 200) and the server stores the id and normalizes `"provider": "local"` itself.
+   - Emit never fabricates media metadata from local `media/*.yaml` files: companion files are used only to cross-check a reference. In a workspace that mirrors media (`media/` exists and is non-empty), a missing or mismatched companion file is reported as a push warning — it means Emit could not confirm the media ID exists, not that the payload is invalid. Workspaces that do not mirror media produce no such warning.
+   - Preflight Guard **G10** rejects local file paths and malformed values before pushing.
 
 ### EmDash Custom Block Preservation
 
@@ -348,18 +435,46 @@ EmDash supports rich visual blocks (e.g., galleries, callouts, audio players). W
 
 ### Media Management & Upload Workflow
 
-EmDash stores media files (images, documents) in Cloudflare R2 via multipart upload endpoints.
+EmDash stores media files (images, documents) in Cloudflare R2 and uses **two distinct identifier spaces**:
+
+| Usage | Identifier Used | Format / Example |
+| --- | --- | --- |
+| Frontmatter `featuredImage` | **Media Record `id`** | 26-character ULID (`01M67P0MBMJQQXH2K95HHCYRYB`) or `null` |
+| Body `![alt](...)` URL | **Media `storageKey`** | `/_emdash/api/media/file/<storageKey>` (e.g. `/_emdash/api/media/file/01M67P07X2VPW0MYRRRGMA6T5A.jpg` or double-ULID `01M6TF1XXBSC06QQG9M648B4K3.01M6TF1Y5YVG9YYQAY6H25270M.png`) |
+
+> [!IMPORTANT]
+> Never put a media record `id` into `/_emdash/api/media/file/<id>.<ext>`—the public file route resolves by **`storageKey`**, so using a record `id` returns HTTP 404.
+
+#### Workflow A: Offline Draft Image Auto-Upload (`media/drafts/` — Recommended for Body Images)
+
+You can author articles completely offline using local images and let `emit push` handle uploading, URL rewriting, and local file promotion automatically:
 
-**How to add and use images in your articles:**
+1. **Stage Image in `media/drafts/`**: Place your image in `<workspace>/media/drafts/<filename>` (supported extensions: `.jpg`, `.jpeg`, `.png`, `.webp`, `.gif`, `.avif`, `.svg`; max 50 MiB).
+2. **Reference on a Standalone Line**: In your Markdown body, reference the staged image on its own standalone line:
+   ```markdown
+   ![Sunset over clouds](../../media/drafts/sunset.png)
+   ```
+3. **Push the Article (`emit push` / `sync_push`)**: Emit automatically:
+   - Uploads the image via EmDash's 4-stage flow (`POST /_emdash/api/media/upload-url` with `sha1:<hex>` deduplication → `PUT` upload → `POST /_emdash/api/media/{id}/confirm`), cleaning up any orphan `pending` record if an upload fails midway.
+   - Rewrites the Markdown line in place to the canonical root-relative `/_emdash/api/media/file/<storageKey>` URL.
+   - Pushes the article to EmDash.
+   - Promotes the local file from `media/drafts/<filename>` to `media/<yyyyMMdd>_<mediaId>-<filename>` alongside a companion `.yaml` metadata file (`storageKey`, `contentHash`, `status`). The `<yyyyMMdd>` prefix reflects the media record's remote `createdAt` when available; if Emit only had a provisional local date, the next `emit pull-media` canonicalizes the filename.
+4. **Reuse Across Articles (no re-upload):** The same `media/drafts/<filename>` line can be used in several articles. After the first push promotes the asset, every later push resolves that reference through `media_state` / `media/*.yaml` and rewrites it to the already-confirmed `/_emdash/api/media/file/<storageKey>` URL instead of uploading again (reported as `[LOCAL_IMAGE_AUTO_UPLOAD] Reused N already-promoted media asset(s)`). A direct reference to the promoted path works as well. Emit verifies each reused record with `GET /_emdash/api/media/{id}`: if the record was deleted on the EmDash side the push aborts with `PROMOTED_MEDIA_NOT_FOUND_REMOTE` (run `emit pull-media` or re-stage the image in `media/drafts/`), and servers without that endpoint push successfully but warn with `[MEDIA_EXISTENCE_UNVERIFIED]`.
 
-1. **Upload New Images**: Upload images via the **EmDash Admin Web Dashboard** (`/admin/media`) or via the official EmDash MCP tool (`media_upload`). This generates a canonical ULID and uploads the asset to Cloudflare R2.
-2. **Sync Media Locally**: Run `emit pull-media` in your workspace. This downloads the images and companion `.yaml` metadata files into `media/`.
+#### Workflow B: Pre-Uploaded Media & Featured Hero Images
+
+1. **Upload via Admin / EmDash MCP**: Upload images via the **EmDash Admin Web Dashboard** (`/admin/media`) or via the official EmDash MCP tool (`media_upload`).
+2. **Sync Media Locally (optional)**: Run `emit pull-media` in your workspace to download images and companion `.yaml` metadata files into `media/`. Note that `emit pull-media --prune` safely ignores `media/drafts/`.
 3. **Embed in Articles**:
-   - For featured hero images: set `featuredImage: "01M6..."` in frontmatter.
-   - For inline images in body: use standard Markdown syntax with remote URLs: `![Alt text](https://your-blog.example.com/api/v1/media/01M6.../file.jpg)`.
+   - For featured hero images: set `featuredImage: "01M67P0MBMJQQXH2K95HHCYRYB"` (26-character canonical media record `id`) or `null` in frontmatter.
+   - For body images: use `![Alt text](/_emdash/api/media/file/<storageKey>)`.
 
 > [!WARNING]
-> **No Local Image Paths in Markdown**: Preflight Guard **G5** strictly forbids pushing articles containing local filesystem paths like `![pic](./my-image.png)`. Images must be uploaded to Cloudflare R2 before publishing to prevent broken images in production.
+> **Local Image Guardrails (G5 & G11)**:
+> - Arbitrary local paths (e.g. `![pic](./my-image.png)`, absolute filesystem paths, or a `media/` path that does not resolve to a promoted media record) are blocked by Preflight Guard **G5 (`LOCAL_IMAGE_DETECTED`)**. Paths under `media/drafts/` and already-promoted `media/<yyyyMMdd>_<id>-<name>.<ext>` paths are the only accepted local forms.
+> - Local images placed inline inside a paragraph (e.g. `Text ![pic](../../media/drafts/a.png) more text`) are blocked with `INLINE_LOCAL_IMAGE_NOT_SUPPORTED` because EmDash Portable Text requires images to be standalone top-level blocks.
+> - A `media/drafts/` reference whose file no longer exists and which has no promoted match is blocked with `MISSING_LOCAL_IMAGE_FILE` (the promoted location is reported in the error).
+> - Only **backtick** fences (```` ``` ````) are exempt from image scanning. Tilde fences (`~~~`) are not recognized as code by the Portable Text mapper, so they are scanned like normal prose (and emit a `G8` warning because they degrade to plain paragraphs). Write code examples with backticks.
 
 ---
 
@@ -390,21 +505,24 @@ Whether you are a human developer or an autonomous AI agent (Antigravity, Claude
 * To push a draft: `emit push posts/draft/<filename>.md`
 * To publish live: update `status: published` and run `emit push posts/draft/<filename>.md --allow-publish`.
 
-### Preflight Safety Guardrails (G1–G9)
+### Preflight Safety Guardrails (G1–G12)
 
-To ensure autonomous AI agents and automated scripts cannot corrupt workspace state or accidentally publish unintended content, Emit enforces 9 strict preflight guardrails before executing any write operation:
+To ensure autonomous AI agents and automated scripts cannot corrupt workspace state or accidentally publish unintended content, Emit enforces 12 strict preflight guardrails before executing any write operation:
 
 | Guard | Code Name | Description | Severity |
 | --- | --- | --- | --- |
 | **G1** | `SINGLE_TARGET_GUARD` | Enforces explicit target (`filePath`, `id`, or `--all`) for push/pull; forbids blind bulk push without inspection | Error |
 | **G2** | `ID_MISMATCH_ERROR` | Verifies that frontmatter `id` exactly matches the filename ULID; forbids manual `mv` renames | Error |
 | **G3** | `UNINTENDED_PUBLISH_GUARD` | Rejects promoting `draft` to `published` unless `--allow-publish` (`allowPublish: true`) is explicitly given | Error |
-| **G4** | `INVALID_TAXONOMY_ERROR` | Validates category and tag slugs against local YAML definitions to stop AI taxonomy hallucination | Error |
-| **G5** | `LOCAL_IMAGE_DETECTED` | Detects unresolved local image paths (`![alt](./path.png)`); requires remote R2 URLs | Error |
+| **G4** | `INVALID_TAXONOMY_ERROR` | Validates taxonomy terms against local definitions (transparently resolves valid term ULIDs) to stop AI taxonomy hallucination | Error |
+| **G5** | `LOCAL_IMAGE_DETECTED` / `INLINE_LOCAL_IMAGE_NOT_SUPPORTED` / `MISSING_LOCAL_IMAGE_FILE` | Rejects local image paths other than `media/drafts/<file>` (or an already-promoted `media/<yyyyMMdd>_<id>-<name>.<ext>` asset) and rejects inline paragraph local images (must be a standalone line) | Error |
 | **G6** | `UNRESOLVED_CONFLICT_MARKERS` | Scans for Git 3-way merge conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`) and blocks push | Error |
 | **G7** | `TITLE_DUPLICATION_AUTOTRIM` | Detects redundant `# Title` headings at the top of the body and automatically trims them safely | Warning |
 | **G8** | `UNSUPPORTED_SYNTAX_WARNING` | Warns if unsupported block HTML or incompatible constructs are detected in Markdown | Warning |
 | **G9** | `MODIFIED_OPAQUE_BLOCK` | Verifies that `<!--ec:block ... -->` opaque fences have not been tampered with or corrupted | Error |
+| **G10** | `INVALID_FEATURED_IMAGE` | Verifies that `featuredImage` is a 26-character canonical media ULID (normalized to uppercase) or `null`. A remote media URL that contains a ULID is resolved with a warning; local file paths and malformed values are rejected | Error |
+| **G11** | `LOCAL_IMAGE_AUTO_UPLOAD` (`MISSING_LOCAL_IMAGE_FILE` / `INVALID_LOCAL_IMAGE_TYPE` / `LOCAL_IMAGE_SIZE_EXCEEDED` / `PROMOTED_MEDIA_NOT_FOUND_REMOTE` / `[MEDIA_EXISTENCE_UNVERIFIED]`) | Detects standalone `media/drafts/<file>` image lines (or reuses an already-promoted `media/` asset across articles), validates file existence, extension, and size (≤ 50 MiB), queues them for automatic upload, URL rewrite, and `media/` promotion during `push`, and verifies every reused asset against `GET /_emdash/api/media/{id}` before its URL is baked into the body | Info / Warning / Error |
+| **G12** | `QUARANTINED_COPY_NOT_PUSHABLE` | Refuses to push a rescue copy under `posts/conflicts/` (written by a pull that found divergent local content) before any network request, because it would overwrite the canonical article of the same ULID with stale content and recreate duplicate local files | Error |
 
 ---
 
@@ -460,7 +578,7 @@ emit profile use <name>
 Scaffolds a new draft article with a canonical 26-character ULID timestamp.
 
 ```bash
-emit new <slug> [-t, --title <title>] [-c, --collection <collection>] [-l, --locale <locale>]
+emit new <slug> [-t, --title <title>] [-c, --collection <collection>] [-l, --locale <locale>] [-b, --byline <slug>] [-p, --profile <name>]
 
 ```
 
@@ -468,6 +586,8 @@ emit new <slug> [-t, --title <title>] [-c, --collection <collection>] [-l, --loc
 * `-t, --title <title>`: Human-readable article title.
 * `-c, --collection <name>`: Collection name (defaults to `posts`).
 * `-l, --locale <locale>`: Locale code (defaults to `ja` or config).
+* `-b, --byline <slug>`: Author byline slug (defaults to the first cached non-guest author ordered by `slug ASC`).
+* `-p, --profile <name>`: Explicitly target a specific connection profile.
 
 **Example:**
 
@@ -480,7 +600,7 @@ emit new ai-workflow-guide --title "AI Workflow Guide"
 
 ```text
 ✅ Created new article scaffold (ID: 01M6ABCDEF1234567890123456)
-   Path: posts/draft/20261104_01M6ABCDEF1234567890123456-ai-workflow-guide.md
+   Path: posts/draft/20261104_01M6ABCDEF1234567890123456-AI-Workflow-Guide.md
 
 Available Categories:
   - tech (技術)
@@ -490,7 +610,7 @@ Available Tags:
   - ai, cloudflare, emit, typescript
 
 Next: Write your content in Markdown, then run:
-   emit push posts/draft/20261104_01M6ABCDEF1234567890123456-ai-workflow-guide.md
+   emit push posts/draft/20261104_01M6ABCDEF1234567890123456-AI-Workflow-Guide.md
 
 ```
 
@@ -506,21 +626,24 @@ emit pull [id] [options]
 ```
 
 * `[id]`: Optional article ID or ULID. If specified, pulls only that specific article (even if outside the window). Taxonomies are not pulled in single-article mode.
-* `-s, --status <draft|published|all>`: Filter by publication status (default: `all`).
+* `-s, --status <draft|published|all>`: Filter by publication status (default: `all`). When set to `all`, the sliding window (`postsSyncLimit`, default `100`) is applied **per status** (fetching up to `postsSyncLimit` `published` + up to `postsSyncLimit` `draft` articles in parallel).
 * `-c, --collection <collection>`: Collection name (default: `posts`).
 * `--no-prune`: Do not prune local articles that have fallen outside the sliding window (escape hatch; not intended for routine use).
 * `--force`: Force overwrite local files and bypass differential hash checking.
 * `--concurrency <n>`: Parallel processing task limit (default: `8`).
-* `--posts-only`: Skip automatic taxonomy (categories/tags) sync. Pull articles only.
-* `--media`: Also pull media assets and companion metadata into `media/`.
+* `--posts-only`: Skip automatic remote taxonomy sync. Pulls articles only (local taxonomy candidates hint is still displayed from cached definitions).
+* `--media`: Also pull media assets and companion metadata into `media/` (bounded by `mediaSyncLimit`, default `300`). Use `emit pull-media` for `--limit`, `--all`, and `--prune` control.
 * `--metadata-only`: With `--media`: download only metadata YAML, skip binary file downloads.
 
 > [!NOTE]
-> **Taxonomies are pulled by default in batch mode.** Categories and tags are lightweight (2 API calls) and required for valid push operations (Preflight Guard G4 validates taxonomy slugs). This eliminates a common source of push failures. Use `--posts-only` if you need articles only.
+> **Taxonomies are pulled by default in batch mode.** Categories and tags are lightweight (2 API calls) and required for valid push operations (Preflight Guard G4 validates taxonomy terms against these local definitions). This eliminates a common source of push failures. Use `--posts-only` if you need articles only.
 
 > [!NOTE]
 > **Why `--no-prune` is rarely needed:**  
-> Automatic pruning is mathematically loss-free: Emit's unpushed edits safeguard strictly aborts the pull if an older article contains local modifications. You only need `--no-prune` in exceptional circumstances, such as temporarily suppressing Git working-tree changes during a quick pull.
+> Automatic pruning is mathematically loss-free: Emit's unpushed edits safeguard inspects both the canonical file and any duplicate filenames sharing the same 26-character ULID, strictly aborting the pull (`SyncPruneConflictError`) if any of them contain local modifications. Clean duplicate files are removed alongside the canonical file. You only need `--no-prune` in exceptional circumstances, such as temporarily suppressing Git working-tree changes during a quick pull.
+
+> [!NOTE]
+> **Unpushed writing is never discarded.** When a pull finds local content that diverges from the last synced baseline, Emit first moves that file to `posts/conflicts/<name>.conflict.md` (a read-only rescue copy) and then writes the canonical article. Rescue copies are never pushed or pruned automatically, and pushing one directly is refused with `QUARANTINED_COPY_NOT_PUSHABLE` (Guard **G12**): read the copy, merge any valuable content into the canonical article, then delete it. If an invalid file also carries local edits, `--force` is the escape hatch (it quarantines the divergent copy, then writes the repaired file).
 
 **Example:**
 
@@ -547,11 +670,19 @@ emit pull 01M5XYZ9876543210123456789
 ```text
 Syncing categories and tags...
   ✅ Taxonomies: 12 categories, 34 tags
-Fetching articles from remote (posts, status: all, window: 100, concurrency: 8)...
-  [1/100] ✅ Pulled hello-world -> posts/published/20261101_01M5...-Hello-World.md
-  [2/100] ✅ Pulled draft-post -> posts/draft/20261104_01M6...-Draft-Post.md
 
-🎉 Articles: 100 total (12 updated, 88 skipped/up-to-date)
+Available Categories:
+  - tech (技術)
+  - column (コラム)
+
+Available Tags:
+  - ai, cloudflare, emit, typescript
+
+Fetching articles from remote (posts, status: all, window: 100/status, concurrency: 8)...
+  [1/169] ✅ Pulled hello-world -> posts/published/20261101_01M5...-Hello-World.md
+  [2/169] ✅ Pulled draft-post -> posts/draft/20261104_01M6...-Draft-Post.md
+
+🎉 Articles: 169 total [100 published, 69 draft] (12 updated, 157 skipped/up-to-date)
 
 ```
 
@@ -597,16 +728,20 @@ emit status [-c, --collection <collection>] [-p, --profile <name>]
 
 ```text
 --- Workspace Status (posts | origin: https://your-blog.example.com) ---
-  🟡 [modified] draft     posts/draft/20261104_01M6BBB...-ai-workflow-guide.md (AI Workflow Guide)
-  ⚪ [untracked] draft     posts/draft/20261104_01M6AAA...-notes.md (Draft Notes)
-  🟢 [synced  ] published posts/published/20261015_01M5ZZZ...-getting-started.md (Getting Started)
+  🟡 [modified] draft     posts/draft/20261104_01M6BBB...-AI-Workflow-Guide.md (AI Workflow Guide)
+  ⚪ [untracked] draft     posts/draft/20261104_01M6AAA...-Draft-Notes.md (Draft Notes)
+  🟢 [synced  ] published posts/published/20261015_01M5ZZZ...-Getting-Started.md (Getting Started)
+  🔴 [invalid ] published posts/published/20190405_01M6CCC...-Broken-Post.md (Broken-Post) [uncached] — bad indentation of a mapping entry at line 5
 
-Summary: 3 total (1 synced, 1 modified, 1 untracked)
+Summary: 4 total (1 synced, 1 modified, 1 untracked, 1 invalid)
 ```
 
 > [!NOTE]
 > Articles are sorted newest-first by date prefix and ULID. The date prefix reflects the article's publication or creation date, not the last-modified time. To locate currently active edits, look for files marked `[modified]`.
 
+> [!NOTE]
+> `[invalid]` marks a file whose YAML frontmatter could not be parsed (usually an older serializer wrote unquoted percent-encoded taxonomy slugs). Batch `emit pull` self-heals cached invalid files; files outside the sliding window are marked `[uncached]` and are repaired with `emit pull <ULID>` (MCP: `sync_pull` with `id: "<ULID>"`). When `<collection>/conflicts/` holds rescue copies, the count is reported separately (`conflicts`) and never counted as an article.
+
 ---
 
 ### `emit diff`
@@ -614,15 +749,19 @@ Summary: 3 total (1 synced, 1 modified, 1 untracked)
 Shows line-by-line differences between the working Markdown file and the baseline snapshot.
 
 ```bash
-emit diff [filePath]
+emit diff [filePath] [-i, --id <id>] [-p, --profile <name>]
 
 ```
 
+* `[filePath]`: Relative path to the local Markdown file (e.g., `posts/draft/20261104_01M6...-my-article.md`).
+* `-i, --id <id>`: Inspect by 26-character article ULID instead of file path.
+* `-p, --profile <name>`: Explicitly target a specific connection profile.
+
 ---
 
 ### `emit pull-taxonomies`
 
-Downloads categories and tags from EmDash and generates local YAML definitions under `categories/` and `tags/`. This is also performed automatically by `emit pull` in batch mode.
+Downloads categories and tags from EmDash and generates local YAML definitions under `categories/` and `tags/`. This is also performed automatically by `emit pull` in batch mode. If one taxonomy endpoint fails, existing local definitions for that taxonomy are preserved with a warning; if both endpoints fail, the command exits with code `1`.
 
 ```bash
 emit pull-taxonomies
@@ -635,6 +774,13 @@ emit pull-taxonomies
 Pulling categories and tags from remote...
 ✅ Successfully synced taxonomies: 12 categories, 34 tags.
 
+Available Categories:
+  - tech (技術)
+  - column (コラム)
+
+Available Tags:
+  - ai, cloudflare, emit, typescript
+
 ```
 
 ---
@@ -731,15 +877,18 @@ Emit features a first-class **Model Context Protocol (MCP)** server over stdio.
 
 | Tool | Purpose | Key Parameters |
 | --- | --- | --- |
-| `sync_status` | Inspect local sync state (articles returned newest-first) | `collection` |
-| `sync_pull` | Pull remote articles **and taxonomies** into local workspace | `id`, `force`, `status`, `noPrune`, `postsOnly`, `includeMedia`, `metadataOnly` |
-| `sync_new` | Scaffold new article with canonical ULID and frontmatter | `slug`, `title`, `locale`, `collection` |
-| `sync_push` | Push local article changes to remote with preflight checks | `filePath`, `id`, `allowPublish` |
-| `sync_diff` | Inspect diff between working file and baseline snapshot | `filePath` |
-| `sync_pull_taxonomies` | Pull remote category and tag definitions (standalone; also included in `sync_pull`) | (none) |
-| `sync_pull_media` | Pull remote media files and metadata into `media/` | `limit`, `all`, `prune`, `metadataOnly` |
+| `sync_status` | Inspect local sync state (articles newest-first, plus `invalid` and `conflicts` diagnostics) | `collection`, `profile` |
+| `sync_pull` | Pull remote articles **and taxonomies** into local workspace (includes taxonomy hints; preserves divergent local copies under `posts/conflicts/`) | `collection`, `id`, `filePath`, `status`, `force`, `noPrune`, `prune`, `postsOnly`, `includeMedia`, `metadataOnly`, `profile` |
+| `sync_new` | Scaffold new article with canonical ULID, frontmatter, default byline, and taxonomy hints | `slug` (required), `title`, `collection`, `locale`, `byline`, `profile` |
+| `sync_push` | Push local article changes to remote with preflight checks and `media/drafts/*` auto-upload; refuses `posts/conflicts/` rescue copies (G12) | `filePath` (required), `allowPublish`, `profile` |
+| `sync_diff` | Inspect diff between working file and baseline snapshot | `filePath`, `id`, `profile` |
+| `sync_pull_taxonomies` | Pull remote category and tag definitions (standalone; returns taxonomy hints) | `profile` |
+| `sync_pull_media` | Pull remote media files and metadata into `media/` | `limit`, `all`, `downloadFiles`, `profile` |
 | `profile_list` | List all configured connection profiles | (none) |
-| `profile_switch` | Switch active profile for multi-site environments | `name` |
+| `profile_switch` | Switch active profile for multi-site environments | `name` (required), `persist` |
+
+> [!NOTE]
+> **Every tool failure is a structured result, never a raw throw.** Handlers return `isError: true` with the same diagnostics the CLI prints — `[CODE]`, HTTP status, endpoint, and a `💡 Suggestion` line (or a `PREFLIGHT_VALIDATION_FAILED` JSON payload with guard codes). This includes workspace/profile resolution failures, which list the available profiles so the agent can retry with an explicit `profile` argument.
 
 ### Autonomous Agent Workflows
 
@@ -757,7 +906,7 @@ With Emit connected via MCP, you can give high-level natural language instructio
 
 To eliminate race conditions when multiple users or agents edit the same post:
 
-1. Emit issues a `POST /api/v1/content/lock` request to EmDash before pushing.
+1. Emit issues a `POST /_emdash/api/content/{collection}/{id}/lock` request to EmDash before pushing.
 2. EmDash grants a 7-minute mutual exclusion lease.
 3. If another author currently holds the lock, Emit aborts with an informative message indicating who owns the lock and when the lease expires.
 4. Emit guarantees lock release using strict `try/finally` execution.
@@ -804,6 +953,12 @@ Push your changes with 'emit push <file>' or discard them before pulling.
 
 **Solution**: Run `emit pull` or `sync_pull` (taxonomies are synced automatically), or use `emit pull-taxonomies` standalone to refresh your local category and tag list. Preflight Guard G4 will guide you with valid options.
 
+### Q: `[NETWORK_ERROR]`: Network request failed (`fetch failed`)
+
+**Cause**: The configured origin URL is unreachable due to DNS resolution failure, offline network/VPN state, or an incorrect origin in `~/.config/emit/profiles.yaml` or `.emit/config.json`.
+
+**Solution**: Verify the `origin` URL reported in `Endpoint:` and check `emit profile list` / `.emit/config.json`. If `.emit/config.json` and your active profile point to different origins, Emit prints an origin mismatch warning to help you reconcile them.
+
 ---
 
 ## 🧪 Testing & Quality Assurance

package/dist/cli/commands/new.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"new.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAGzC,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,eAAe,CAAC;AAExD,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,OAAO,EAAE,cAAc,EAAE,kBAAkB,GAAG,IAAI,CAkC7F"}
+{"version":3,"file":"new.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAGzC,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,eAAe,CAAC;AAExD,wBAAgB,kBAAkB,CAAC,OAAO,EAAE,OAAO,EAAE,cAAc,EAAE,kBAAkB,GAAG,IAAI,CAyC7F"}

package/dist/cli/commands/new.js

@@ -24,10 +24,11 @@ import { getLocalTaxonomiesSummary, formatTaxonomiesHint } from '../../sync/taxo
 export function registerNewCommand(program, resolveContext) {
     program
         .command('new <slug>')
-        .description('Create a new draft article template with an auto-generated ULID')
+        .description('Create a new draft article template with an auto-generated ULID and taxonomy hints')
         .option('-t, --title <title>', 'Article title')
         .option('-c, --collection <collection>', 'Target collection (defaults to "posts")')
         .option('-l, --locale <locale>', 'Article locale (defaults to "ja")')
+        .option('-b, --byline <slug>', 'Author byline slug (defaults to first cached non-guest author by slug)')
         .option('-p, --profile <name>', 'Explicitly use a specific connection profile')
         .action((slug, options) => {
         const ctx = resolveContext(options.profile);
@@ -38,6 +39,7 @@ export function registerNewCommand(program, resolveContext) {
             title: options.title,
             collection,
             locale,
+            byline: options.byline,
             workspaceRoot: ctx.root,
             cache: ctx.cache,
         });

package/dist/cli/commands/new.js.map

@@ -1 +1 @@
-{"version":3,"file":"new.js","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAGH,OAAO,EAAE,qBAAqB,EAAE,MAAM,mBAAmB,CAAC;AAC1D,OAAO,EAAE,yBAAyB,EAAE,oBAAoB,EAAE,MAAM,0BAA0B,CAAC;AAG3F,MAAM,UAAU,kBAAkB,CAAC,OAAgB,EAAE,cAAkC;IACrF,OAAO;SACJ,OAAO,CAAC,YAAY,CAAC;SACrB,WAAW,CAAC,iEAAiE,CAAC;SAC9E,MAAM,CAAC,qBAAqB,EAAE,eAAe,CAAC;SAC9C,MAAM,CAAC,+BAA+B,EAAE,yCAAyC,CAAC;SAClF,MAAM,CAAC,uBAAuB,EAAE,mCAAmC,CAAC;SACpE,MAAM,CAAC,sBAAsB,EAAE,8CAA8C,CAAC;SAC9E,MAAM,CAAC,CAAC,IAAI,EAAE,OAAO,EAAE,EAAE;QACxB,MAAM,GAAG,GAAG,cAAc,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QAC5C,MAAM,UAAU,GAAG,OAAO,CAAC,UAAU,IAAI,GAAG,CAAC,MAAM,CAAC,iBAAiB,CAAC;QACtE,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,IAAI,GAAG,CAAC,MAAM,CAAC,aAAa,CAAC;QAE1D,MAAM,GAAG,GAAG,qBAAqB,CAAC;YAChC,IAAI;YACJ,KAAK,EAAE,OAAO,CAAC,KAAK;YACpB,UAAU;YACV,MAAM;YACN,aAAa,EAAE,GAAG,CAAC,IAAI;YACvB,KAAK,EAAE,GAAG,CAAC,KAAK;SACjB,CAAC,CAAC;QAEH,OAAO,CAAC,GAAG,CAAC,uCAAuC,GAAG,CAAC,EAAE,GAAG,CAAC,CAAC;QAC9D,OAAO,CAAC,GAAG,CAAC,YAAY,GAAG,CAAC,QAAQ,EAAE,CAAC,CAAC;QAExC,MAAM,UAAU,GAAG,yBAAyB,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QACvD,MAAM,OAAO,GAAG,oBAAoB,CAAC,UAAU,EAAE,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC,CAAC;QAClE,IAAI,OAAO,EAAE,CAAC;YACZ,OAAO,CAAC,GAAG,CAAC,KAAK,OAAO,EAAE,CAAC,CAAC;QAC9B,CAAC;QAED,OAAO,CAAC,GAAG,CAAC,mDAAmD,CAAC,CAAC;QACjE,OAAO,CAAC,GAAG,CAAC,gBAAgB,GAAG,CAAC,QAAQ,EAAE,CAAC,CAAC;IAC9C,CAAC,CAAC,CAAC;AACP,CAAC"}
+{"version":3,"file":"new.js","sourceRoot":"","sources":["../../../src/cli/commands/new.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;GAoBG;AAGH,OAAO,EAAE,qBAAqB,EAAE,MAAM,mBAAmB,CAAC;AAC1D,OAAO,EAAE,yBAAyB,EAAE,oBAAoB,EAAE,MAAM,0BAA0B,CAAC;AAG3F,MAAM,UAAU,kBAAkB,CAAC,OAAgB,EAAE,cAAkC;IACrF,OAAO;SACJ,OAAO,CAAC,YAAY,CAAC;SACrB,WAAW,CACV,oFAAoF,CACrF;SACA,MAAM,CAAC,qBAAqB,EAAE,eAAe,CAAC;SAC9C,MAAM,CAAC,+BAA+B,EAAE,yCAAyC,CAAC;SAClF,MAAM,CAAC,uBAAuB,EAAE,mCAAmC,CAAC;SACpE,MAAM,CACL,qBAAqB,EACrB,wEAAwE,CACzE;SACA,MAAM,CAAC,sBAAsB,EAAE,8CAA8C,CAAC;SAC9E,MAAM,CAAC,CAAC,IAAI,EAAE,OAAO,EAAE,EAAE;QACxB,MAAM,GAAG,GAAG,cAAc,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QAC5C,MAAM,UAAU,GAAG,OAAO,CAAC,UAAU,IAAI,GAAG,CAAC,MAAM,CAAC,iBAAiB,CAAC;QACtE,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,IAAI,GAAG,CAAC,MAAM,CAAC,aAAa,CAAC;QAE1D,MAAM,GAAG,GAAG,qBAAqB,CAAC;YAChC,IAAI;YACJ,KAAK,EAAE,OAAO,CAAC,KAAK;YACpB,UAAU;YACV,MAAM;YACN,MAAM,EAAE,OAAO,CAAC,MAAM;YACtB,aAAa,EAAE,GAAG,CAAC,IAAI;YACvB,KAAK,EAAE,GAAG,CAAC,KAAK;SACjB,CAAC,CAAC;QAEH,OAAO,CAAC,GAAG,CAAC,uCAAuC,GAAG,CAAC,EAAE,GAAG,CAAC,CAAC;QAC9D,OAAO,CAAC,GAAG,CAAC,YAAY,GAAG,CAAC,QAAQ,EAAE,CAAC,CAAC;QAExC,MAAM,UAAU,GAAG,yBAAyB,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QACvD,MAAM,OAAO,GAAG,oBAAoB,CAAC,UAAU,EAAE,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC,CAAC;QAClE,IAAI,OAAO,EAAE,CAAC;YACZ,OAAO,CAAC,GAAG,CAAC,KAAK,OAAO,EAAE,CAAC,CAAC;QAC9B,CAAC;QAED,OAAO,CAAC,GAAG,CAAC,mDAAmD,CAAC,CAAC;QACjE,OAAO,CAAC,GAAG,CAAC,gBAAgB,GAAG,CAAC,QAAQ,EAAE,CAAC,CAAC;IAC9C,CAAC,CAAC,CAAC;AACP,CAAC"}

package/dist/cli/commands/profile.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"profile.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/profile.ts"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AASzC,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAuF9D"}
+{"version":3,"file":"profile.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/profile.ts"],"names":[],"mappings":"AAsBA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAUzC,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CA0I9D"}