@skitterbyte/skitterspec 1.0.1 → 2.0.0

package/assets/scripts/lib/config.js

@@ -1,127 +0,0 @@
-'use strict'
-
-/**
- * Config loader for the release-artifact generators.
- *
- * Reads `skitterspec.config.json` from the repo root and normalises it over
- * documented defaults. Shipped alongside the generators (copied into the
- * consumer's `scripts/lib/`) so the consumer's scripts never depend back into
- * the skitterspec package. Zero-dependency.
- *
- * Shape:
- *   {
- *     "version": 1,
- *     "changelog": { "enabled": true, "file": "CHANGELOG.md" },
- *     "releases":  { "enabled": true, "file": "RELEASES.md",
- *                    "productName": "<repo name>", "scopeAreas": {} },
- *     "versionHook": true
- *   }
- */
-
-const { readFileSync } = require('node:fs')
-const { basename, join } = require('node:path')
-
-const SCHEMA_VERSION = 1
-const CONFIG_FILE = 'skitterspec.config.json'
-
-// Static template (productName is derived from the repo dir when blank).
-const DEFAULT_CONFIG = Object.freeze({
-  version: SCHEMA_VERSION,
-  changelog: Object.freeze({ enabled: true, file: 'CHANGELOG.md' }),
-  releases: Object.freeze({
-    enabled: true,
-    file: 'RELEASES.md',
-    productName: '',
-    scopeAreas: Object.freeze({}),
-  }),
-  versionHook: true,
-})
-
-function isObject(value) {
-  return value !== null && typeof value === 'object' && !Array.isArray(value)
-}
-
-function defaultsFor(dir) {
-  return {
-    version: SCHEMA_VERSION,
-    changelog: { enabled: true, file: 'CHANGELOG.md' },
-    releases: {
-      enabled: true,
-      file: 'RELEASES.md',
-      productName: basename(dir),
-      scopeAreas: {},
-    },
-    versionHook: true,
-  }
-}
-
-/**
- * Merge a parsed config over the defaults. Only known keys are copied (unknown
- * keys are ignored for forward-compat); `scopeAreas` is replaced wholesale, not
- * deep-merged, since it's a complete map.
- */
-function mergeConfig(base, parsed) {
-  if (!isObject(parsed)) return base
-
-  if (typeof parsed.version === 'number') base.version = parsed.version
-  if (typeof parsed.versionHook === 'boolean') base.versionHook = parsed.versionHook
-
-  if (isObject(parsed.changelog)) {
-    if (typeof parsed.changelog.enabled === 'boolean') {
-      base.changelog.enabled = parsed.changelog.enabled
-    }
-    if (typeof parsed.changelog.file === 'string' && parsed.changelog.file.trim()) {
-      base.changelog.file = parsed.changelog.file.trim()
-    }
-  }
-
-  if (isObject(parsed.releases)) {
-    if (typeof parsed.releases.enabled === 'boolean') {
-      base.releases.enabled = parsed.releases.enabled
-    }
-    if (typeof parsed.releases.file === 'string' && parsed.releases.file.trim()) {
-      base.releases.file = parsed.releases.file.trim()
-    }
-    if (typeof parsed.releases.productName === 'string' && parsed.releases.productName.trim()) {
-      base.releases.productName = parsed.releases.productName.trim()
-    }
-    if (isObject(parsed.releases.scopeAreas)) {
-      base.releases.scopeAreas = { ...parsed.releases.scopeAreas }
-    }
-  }
-
-  return base
-}
-
-/**
- * Load and normalise config from `dir` (default cwd). Missing file → all
- * defaults. Malformed JSON → throws a clear Error (callers exit non-zero).
- */
-function loadConfig(dir = process.cwd()) {
-  const base = defaultsFor(dir)
-  const file = join(dir, CONFIG_FILE)
-
-  let raw
-  try {
-    raw = readFileSync(file, 'utf-8')
-  } catch (error) {
-    if (error.code === 'ENOENT') return base
-    throw error
-  }
-
-  let parsed
-  try {
-    parsed = JSON.parse(raw)
-  } catch (error) {
-    throw new Error(`Invalid ${CONFIG_FILE}: ${error.message}`)
-  }
-
-  return mergeConfig(base, parsed)
-}
-
-module.exports = {
-  loadConfig,
-  DEFAULT_CONFIG,
-  SCHEMA_VERSION,
-  CONFIG_FILE,
-}

package/assets/scripts/lib/git-commits.js

@@ -1,265 +0,0 @@
-'use strict'
-
-/**
- * Shared git-history plumbing for the release artifact generators.
- *
- * Both `generate-changelog.js` (dev-facing CHANGELOG, from commit subjects) and
- * `generate-releases.js` (user-facing RELEASES, from `Release-Note:` footers)
- * walk the same tag ranges and parse the same conventional-commit format. This
- * module is the single source of that logic so the two generators cannot drift.
- *
- * Commit serialisation: git log emits `hash\0subject\0body\0` per commit (NUL
- * delimiters so multi-line bodies survive). `reconstructCommits` regroups the
- * flat NUL-split array back into per-commit `hash\0subject\0body` strings.
- *
- * A parsed commit is a plain object:
- *   { type, scope?, message, body?, hash, breaking }
- */
-
-const { execSync } = require('node:child_process')
-
-function getCommitsSinceLastTag(currentVersion) {
-  try {
-    // Fetch tags to ensure they're available (important in CI)
-    try {
-      execSync('git fetch --tags --force', { encoding: 'utf-8', stdio: 'pipe' })
-    } catch {
-      // If fetch fails, continue - tags might already be available
-    }
-
-    // Get all tags sorted by version (newest first)
-    const allTags = execSync('git tag --sort=-version:refname', {
-      encoding: 'utf-8',
-      stdio: 'pipe',
-    })
-      .trim()
-      .split('\n')
-      .filter((tag) => tag.trim().length > 0)
-
-    // Determine the previous tag to compare against
-    let previousTag = null
-    let currentTag = null
-
-    if (allTags.length === 0) {
-      // No tags exist, get all commits
-      const output = execSync('git log --pretty=format:"%h%x00%s%x00%b%x00" --no-merges', {
-        encoding: 'utf-8',
-        stdio: 'pipe',
-      }).trim()
-
-      return reconstructCommits(output)
-    }
-
-    // Check if HEAD is at a tag
-    try {
-      currentTag = execSync('git describe --tags --exact-match HEAD', {
-        encoding: 'utf-8',
-        stdio: 'pipe',
-      }).trim()
-    } catch {
-      // HEAD is not at a tag - try to get current branch/tag from environment
-      // In CI, Build.SourceBranchName might be available
-      const sourceBranch = process.env.BUILD_SOURCEBRANCHNAME || process.env.BUILD_SOURCEBRANCH
-      if (sourceBranch && sourceBranch.startsWith('v')) {
-        currentTag = sourceBranch
-      } else if (currentVersion) {
-        // Use the version parameter as fallback (e.g., "8.0.0" -> "v8.0.0")
-        const versionTag = `v${currentVersion}`
-        if (allTags.includes(versionTag)) {
-          currentTag = versionTag
-        }
-      }
-    }
-
-    if (currentTag && allTags.includes(currentTag)) {
-      // HEAD is at a tag - find the previous tag
-      const currentIndex = allTags.indexOf(currentTag)
-      if (currentIndex > 0) {
-        // There is a previous tag
-        previousTag = allTags[currentIndex - 1]
-      } else {
-        // This is the first tag, get all commits
-        const output = execSync('git log --pretty=format:"%h%x00%s%x00%b%x00" --no-merges', {
-          encoding: 'utf-8',
-          stdio: 'pipe',
-        }).trim()
-
-        return reconstructCommits(output)
-      }
-    } else {
-      // HEAD is not at a tag, use the most recent tag
-      previousTag = allTags[0]
-    }
-
-    if (!previousTag) {
-      // No previous tag found, get all commits
-      const output = execSync('git log --pretty=format:"%h%x00%s%x00%b%x00" --no-merges', {
-        encoding: 'utf-8',
-        stdio: 'pipe',
-      }).trim()
-
-      return reconstructCommits(output)
-    }
-
-    // When HEAD is at a tag, use the tag explicitly instead of HEAD
-    // This ensures we get commits up to and including the tag commit
-    const rangeEnd = currentTag || 'HEAD'
-
-    // Get commits since previous tag (inclusive of rangeEnd)
-    // Use null character as delimiter to handle multi-line bodies
-    // Format: hash\0subject\0body\0hash2\0subject2\0body2\0...
-    // NOTE: do NOT pass --all here — it traverses every ref (branches,
-    // remotes, tags) and leaks commits from unmerged branches into the
-    // range. Shallow-clone fallback below uses git fetch --unshallow.
-    const output = execSync(
-      `git log ${previousTag}..${rangeEnd} --pretty=format:"%h%x00%s%x00%b%x00" --no-merges`,
-      { encoding: 'utf-8', stdio: 'pipe' },
-    ).trim()
-
-    const commits = reconstructCommits(output)
-
-    // If no commits found and we're in CI, try unshallow the repo
-    if (commits.length === 0) {
-      try {
-        execSync('git fetch --unshallow', { encoding: 'utf-8', stdio: 'pipe' })
-        // Try again after unshallow
-        const retryOutput = execSync(
-          `git log ${previousTag}..${rangeEnd} --pretty=format:"%h%x00%s%x00%b%x00" --no-merges`,
-          { encoding: 'utf-8', stdio: 'pipe' },
-        ).trim()
-        return reconstructCommits(retryOutput)
-      } catch {
-        // Unshallow failed or not a shallow clone, return empty
-      }
-    }
-
-    return commits
-  } catch (error) {
-    // If git commands fail, try to get all commits as fallback
-    try {
-      const output = execSync('git log --pretty=format:"%h%x00%s%x00%b%x00" --no-merges', {
-        encoding: 'utf-8',
-        stdio: 'pipe',
-      }).trim()
-
-      return reconstructCommits(output)
-    } catch {
-      console.error('Failed to get git commits:', error)
-      return []
-    }
-  }
-}
-
-function reconstructCommits(output) {
-  if (!output.trim()) {
-    return []
-  }
-
-  // Split by null character - DO NOT filter empty parts yet
-  // Empty bodies are valid and needed to maintain correct grouping
-  const parts = output.split('\0')
-
-  const commits = []
-
-  // Group parts into commits: each commit has hash, subject, body
-  // Parts array: [hash1, subject1, body1, hash2, subject2, body2, ...]
-  // Trailing empty string from final \0 is expected and ignored
-  for (let i = 0; i < parts.length - 1; i += 3) {
-    const hash = parts[i] || ''
-    const subject = parts[i + 1] || ''
-    const body = parts[i + 2] || ''
-
-    // Only add commit if we have hash and subject (body can be empty)
-    if (hash.trim() && subject.trim()) {
-      // Reconstruct commit string with null delimiters
-      commits.push(`${hash}\0${subject}\0${body}`)
-    }
-  }
-
-  return commits
-}
-
-function parseCommit(commitLine) {
-  // Split by null character (used as delimiter in git log format)
-  const parts = commitLine.split('\0')
-
-  // Need at least hash and subject (body is optional)
-  if (parts.length < 2) {
-    return null // Invalid format, skip
-  }
-
-  const hash = parts[0].trim()
-  const subject = parts[1].trim()
-  const body = (parts[2] && parts[2].trim()) || undefined
-
-  // Parse conventional commit format: type(scope)!: description
-  // The optional `!` marks a breaking change per the Conventional Commits spec.
-  const conventionalCommitRegex = /^(\w+)(?:\(([^)]+)\))?(!)?:\s*(.+)$/
-  const match = subject.match(conventionalCommitRegex)
-
-  if (!match) {
-    return null // Skip non-conventional commits
-  }
-
-  const [, type, scope, bang, message] = match
-
-  // Breaking change markers:
-  //   1. `!` suffix on type/scope (e.g. `feat!:` or `feat(api)!:`)
-  //   2. A `BREAKING CHANGE:` or `BREAKING-CHANGE:` footer in the body
-  const breakingFooterRegex = /(^|\n)BREAKING[- ]CHANGE:/i
-  const breaking = Boolean(bang) || (body ? breakingFooterRegex.test(body) : false)
-
-  return {
-    type: type.toLowerCase(),
-    scope: scope || undefined,
-    message: message.trim(),
-    body: body,
-    hash: hash.trim(),
-    breaking,
-  }
-}
-
-function getAllVersionTags() {
-  try {
-    execSync('git fetch --tags --force', { encoding: 'utf-8', stdio: 'pipe' })
-  } catch {
-    // fetch is best-effort
-  }
-
-  return execSync('git tag --sort=-version:refname', { encoding: 'utf-8', stdio: 'pipe' })
-    .trim()
-    .split('\n')
-    .map((t) => t.trim())
-    .filter((t) => /^v?\d+\.\d+\.\d+/.test(t))
-}
-
-function getCommitsBetween(fromTag, toTag) {
-  const range = fromTag ? `${fromTag}..${toTag}` : toTag
-  const output = execSync(`git log ${range} --pretty=format:"%h%x00%s%x00%b%x00" --no-merges`, {
-    encoding: 'utf-8',
-    stdio: 'pipe',
-  }).trim()
-  return reconstructCommits(output)
-}
-
-function getTagDate(tag) {
-  try {
-    return execSync(`git log -1 --format=%cs ${tag}`, { encoding: 'utf-8', stdio: 'pipe' }).trim()
-  } catch {
-    return new Date().toISOString().split('T')[0]
-  }
-}
-
-function escapeRegex(value) {
-  return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&')
-}
-
-module.exports = {
-  getCommitsSinceLastTag,
-  reconstructCommits,
-  parseCommit,
-  getAllVersionTags,
-  getCommitsBetween,
-  getTagDate,
-  escapeRegex,
-}

package/assets/skills/commit/SKILL.md

@@ -1,28 +0,0 @@
----
-name: commit
-description: Stage and commit the current change with a concise conventional-commit message. Stages only files related to the task, runs typecheck and the relevant tests first, and appends a Release-Note: footer when the change is user-visible (grammar in .claude/rules/commit-messages.md). Use when the user says "/commit", "commit this", or wants their working changes committed.
----
-
-# /commit — stage and commit the current change
-
-A disciplined commit: stage only what belongs to the task, prove it's green,
-then write a conventional-commit message — with a `Release-Note:` footer when an
-end user would notice the change. Message grammar and length limits live in
-`.claude/rules/commit-messages.md`.
-
-1. Run `git status` and `git diff --staged`.
-2. Stage ONLY files related to the current task (ignore unrelated UI/config
-   drift).
-3. Run typecheck and the relevant tests.
-4. Write a concise conventional commit message scoped to the change.
-5. **Decide if the change is user-visible.** If an end user would notice it
-   (feature, fix, improvement), append a `Release-Note:` footer in plain user
-   language — what they can now do, not the implementation. Use `Release-Note!:`
-   for a release headline, and `Release-Area:` to override the area when the
-   scope isn't a user area. Omit the footer for internal/dev-only changes
-   (`chore`, `test`, `docs`, refactors with no user effect). Put a blank line
-   before the footer. See `.claude/rules/commit-messages.md` → "Release notes
-   footer" for the grammar. When the release tooling is installed, these footers
-   are what the generated release notes are built from at `npm version` — so the
-   note is the user-facing record of the change, not just metadata.
-6. Do NOT ask about unrelated uncommitted files.

package/assets/skills/spec-pull/SKILL.md

@@ -1,46 +0,0 @@
----
-name: spec-pull
-description: Pull a spec's linked Linear project into the local spec (Linear → repo), three-way aware. Applies remote-only fields; refuses to clobber local edits on a conflict unless --force (which backs up the local side first). Fetches Linear over MCP and runs `skitterspec spec-sync pull`. Opt-in — needs specs/.core/linear.config.json. Use when the user says "/spec-pull", "pull from Linear", "sync Linear changes down", or "update this spec from Linear".
----
-
-# /spec-pull — bring Linear changes into the spec
-
-Linear → repo. Applies fields Linear changed since the last sync (status,
-priority, labels, and co-authored fields), rewrites the committed base, and
-stamps `last_synced_at`. It **refuses** to overwrite a local edit that conflicts
-with a Linear edit unless you pass `--force`.
-
-**Opt-in**: only runs when `specs/.core/linear.config.json` exists. If absent,
-tell the user how to enable Linear sync and stop.
-
-## 1. Identify the target spec
-
-Use the argument, else the spec in context; ask if unclear.
-
-## 2. Fetch the Linear project
-
-- Read `linear_project_id` from `00-overview.md` frontmatter; if missing, the
-  spec isn't linked — stop and point at `/spec`.
-- Discover the Linear MCP project-read tool at runtime. If Linear isn't
-  connected, relay the fix and stop — **do nothing destructive**.
-- Call it and write the project JSON to a temp file.
-
-## 3. Run the engine
-
-```
-skitterspec spec-sync pull <spec> --remote <tempfile> [--force]
-```
-
-- **No conflict** — the engine applies remote-only fields to the local snapshot,
-  rewrites the base, and stamps the sync. Body fields with no local home yet are
-  reported as `deferred` (apply them by hand from Linear if needed).
-- **Conflict** (a co-authored field changed on both sides) — the engine
-  **refuses** and lists the fields. Relay that; do not force on the user's behalf.
-- **`--force`** — only when the user explicitly asks. Remote wins after the engine
-  backs up the local side under `sync.backupDir` (the reflog). Relay the backup
-  path.
-
-## 4. Report
-
-Relay the git-like summary (applied / deferred / conflicts / backup / base). If
-fields were applied, remind the user to review and commit the refreshed snapshot.

package/assets/skills/spec-push/SKILL.md

@@ -1,53 +0,0 @@
----
-name: spec-push
-description: Push a spec's local content up to its linked Linear project (repo → Linear), three-way aware and ownership-respecting. Never pushes pull-owned fields or local-only sections; aborts if Linear moved since the last sync unless --force (which backs up the remote side first). Runs `skitterspec spec-sync push` then applies the blessed writes over MCP. Opt-in — needs specs/.core/linear.config.json. Use when the user says "/spec-push", "push to Linear", "sync my spec up to Linear", or "update the Linear project from this spec".
----
-
-# /spec-push — send spec content up to Linear
-
-Repo → Linear. Sends the fields the repo owns/co-authors (description, phases,
-tasks per config) up to the linked project. It **never** writes `pull`-owned
-fields (status/priority/labels) or `localOnlySections`, and it **aborts** if
-Linear moved since the last sync (pull first) unless you `--force`.
-
-**Opt-in**: only runs when `specs/.core/linear.config.json` exists. If absent,
-tell the user how to enable Linear sync and stop.
-
-## 1. Identify the target spec
-
-Use the argument, else the spec in context; ask if unclear.
-
-## 2. Fetch the Linear project
-
-- Read `linear_project_id` from `00-overview.md` frontmatter; if missing, stop
-  (link via `/spec` first).
-- Discover the Linear MCP tools at runtime (project read **and** update). If
-  Linear isn't connected — or the update tool is missing — relay the fix and stop,
-  **writing nothing**.
-- Call the read tool and write the project JSON to a temp file.
-
-## 3. Run the engine (the guard)
-
-```
-skitterspec spec-sync push <spec> --remote <tempfile> --out <mergedfile> [--force]
-```
-
-- **Refused** (`remote-moved` / `concurrent-write` / conflict) — relay the message
-  and **stop**. Do not write to Linear. Suggest `/spec-pull` first.
-- **OK** — the engine has confirmed it's safe, rewritten the base, and stamped
-  `last_synced_at`. Its summary lists the `written` fields (and any `skipped`
-  because they're not pushable).
-- **`--force`** — only when the user explicitly asks. Local wins after the engine
-  backs up the remote side under `sync.backupDir`. Relay the backup path.
-
-## 4. Apply the blessed writes to Linear
-
-Only when step 3 returned OK: for each `written` field, call the Linear update
-tool with that field's local value (e.g. `description` → the project description).
-The engine has already vetted the change and moved the base — so if a Linear
-write fails, re-run `/spec-pull` to reconcile rather than retrying blindly.
-
-## 5. Report
-
-Relay the git-like summary (written / skipped / backup / base) plus which Linear
-fields you updated.

package/assets/skills/spec-status/SKILL.md

@@ -1,46 +0,0 @@
----
-name: spec-status
-description: Show a spec's sync status against its linked Linear project — a read-only, git-status-style per-field divergence (local-only / remote-only / conflict / in-sync). Fetches the Linear project over MCP and runs `skitterspec spec-sync status`. Changes nothing. Opt-in — needs specs/.core/linear.config.json. Use when the user says "/spec-status", "is this spec in sync with Linear", "what's diverged from Linear", or "show spec sync status".
----
-
-# /spec-status — show a spec's divergence from Linear
-
-Read-only. Prints, per field, whether the spec and its linked Linear project have
-diverged since the last sync — the `git status` of the hybrid sync. Writes
-nothing to either side.
-
-This skill is **opt-in**: it only runs when `specs/.core/linear.config.json`
-exists. If it's absent, tell the user to copy `linear.config.json.example` →
-`linear.config.json` to enable Linear sync, and stop.
-
-## 1. Identify the target spec
-
-Use the spec named as an argument, else the spec **currently in context**. If
-neither is clear, ask which spec.
-
-## 2. Fetch the Linear project (read-only)
-
-- Read the spec's `linear_project_id` from `00-overview.md` frontmatter. If it's
-  missing, the spec isn't linked yet — say so and stop (link it via `/spec`).
-- Discover the connected Linear MCP tools at runtime (the project-read tool). If
-  Linear isn't connected, relay "connect the `linear` MCP server" and stop — do
-  nothing else.
-- Call the project-read tool for that id and write the returned JSON to a temp
-  file (e.g. under the OS temp dir).
-
-## 3. Run the engine
-
-```
-skitterspec spec-sync status <spec> --remote <tempfile>
-```
-
-The engine does the three-way compare (local vs Linear vs the committed base) and
-prints each diverged field with its classification and sync direction. Without
-`--remote` it falls back to a local-vs-base comparison (still read-only).
-
-## 4. Report
-
-Relay the engine's summary verbatim, then offer the natural next step:
-`/spec-pull` for remote-only changes, `/spec-push` for local-only, and — for a
-`conflict` — resolve locally or use `--force` (which backs up the losing side).
-Never write anything from this skill.

package/src/config.js

@@ -1,13 +0,0 @@
-'use strict'
-
-/**
- * Config helpers for the skitterspec CLI.
- *
- * The implementation lives in `assets/scripts/lib/config.js` — the same file
- * that ships into a consumer's `scripts/lib/`, so the loader has one source of
- * truth and the consumer's copied scripts never depend back into this package.
- * This module just re-exports it for use by the CLI (`init`, the install
- * prompts in Phase 3).
- */
-
-module.exports = require('../assets/scripts/lib/config.js')

package/src/sync/apply.js

@@ -1,66 +0,0 @@
-'use strict'
-
-/**
- * Translate normalized field values into a local frontmatter patch (pull side).
- *
- * Only the `pull`-owned, frontmatter-backed fields have a local home in Phase 2:
- *   workflowState → spec_status (Linear state name mapped back to the bucket),
- *   priority      → priority,
- *   labels        → labels.
- * Any other field handed in (a body field like `description`/`milestones`) has no
- * frontmatter mapping yet, so it's returned in `deferred` — the caller must NOT
- * advance its base, keeping the remote edit pending instead of falsely synced.
- */
-
-// field name → frontmatter key.
-const FRONTMATTER_FIELD = {
-  workflowState: 'spec_status',
-  priority: 'priority',
-  labels: 'labels',
-}
-
-// Invert config.states ({ bucket: "Linear Name" }) → { "linear name": bucket }.
-function invertStates(config) {
-  const out = {}
-  const states = (config && config.states) || {}
-  for (const [bucket, name] of Object.entries(states)) {
-    if (typeof name === 'string') out[name.toLowerCase()] = bucket
-  }
-  return out
-}
-
-// Map a remote workflowState (a Linear state name) back to a local bucket. Falls
-// back to the raw value when it isn't one of the configured states.
-function localWorkflowState(value, config) {
-  if (value == null) return null
-  const bucket = invertStates(config)[String(value).toLowerCase()]
-  return bucket || String(value)
-}
-
-/**
- * Build the frontmatter patch for a set of applied field values.
- * @param {object} fieldValues  { fieldName: value } to write locally
- * @returns {{ patch:object, applied:string[], deferred:string[] }}
- */
-function frontmatterPatchFor(fieldValues, config) {
-  const patch = {}
-  const applied = []
-  const deferred = []
-  for (const [field, value] of Object.entries(fieldValues)) {
-    const key = FRONTMATTER_FIELD[field]
-    if (!key) {
-      deferred.push(field)
-      continue
-    }
-    patch[key] = field === 'workflowState' ? localWorkflowState(value, config) : value
-    applied.push(field)
-  }
-  return { patch, applied, deferred }
-}
-
-module.exports = {
-  frontmatterPatchFor,
-  localWorkflowState,
-  invertStates,
-  FRONTMATTER_FIELD,
-}