opensdd 0.1.2 → 0.1.3

package/opensdd/cli.md

@@ -30,9 +30,9 @@ Initializes the OpenSDD protocol in the current project.
 
 1. Verify the current directory is a project root (contains `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `.git`, `opensdd.json`, or similar project markers). If no project marker is found, warn the user and ask for confirmation to proceed.
 2. Install both skills (sdd-manager and sdd-generate) into all supported agent configuration directories. If already present, overwrite — skills are always spec-owned. The full installation mapping is defined in the **Skill Installation Mapping** section below.
-3. If `opensdd.json` does not exist at the project root, create it with default contents: `{ "opensdd": "0.1.0", "specs_dir": "opensdd", "deps_dir": ".opensdd.deps" }`. The `registry`, `publish`, and `dependencies` fields are intentionally omitted from the default — they are optional. When `registry` is absent, the CLI defaults to `https://github.com/deepagents-ai/opensdd` per the registry source resolution logic. If `opensdd.json` already exists, leave it untouched.
-4. Create the `opensdd/` directory (or the directory specified by `specs_dir` in an existing `opensdd.json`) if it does not exist.
-5. If `<specs_dir>/spec.md` does not exist, create a skeleton `spec.md` with placeholder sections:
+3. If `opensdd.json` does not exist at the project root, create it with default contents: `{ "opensdd": "0.1.0", "specsDir": "opensdd", "depsDir": ".opensdd.deps" }`. The `registry`, `publish`, and `dependencies` fields are intentionally omitted from the default — they are optional. When `registry` is absent, the CLI defaults to `https://github.com/deepagents-ai/opensdd` per the registry source resolution logic. If `opensdd.json` already exists, leave it untouched.
+4. Create the `opensdd/` directory (or the directory specified by `specsDir` in an existing `opensdd.json`) if it does not exist.
+5. If `<specsDir>/spec.md` does not exist, create a skeleton `spec.md` with placeholder sections:
    ```markdown
    # {project-name}
 
@@ -51,7 +51,7 @@ Initializes the OpenSDD protocol in the current project.
    <!-- List properties that must hold true across all inputs and states. -->
    ```
    The `{project-name}` placeholder SHOULD be inferred from the nearest project manifest (e.g., `name` in `package.json`) or default to the directory name. If `spec.md` already exists, leave it untouched.
-6. Create the `.opensdd.deps/` directory (or the directory specified by `deps_dir` in an existing `opensdd.json`) if it does not exist.
+6. Create the `.opensdd.deps/` directory (or the directory specified by `depsDir` in an existing `opensdd.json`) if it does not exist.
 7. Print a success message.
 
 - `opensdd init` in a fresh project MUST produce the output below
@@ -270,12 +270,12 @@ Fetches a spec from the registry and installs it as a dependency.
 #### Behavior
 
 1. Verify `opensdd.json` exists at the project root. If not, print a message suggesting `opensdd init` first and exit with code 1.
-2. Check if the spec `<name>` already exists as a key in `opensdd.json`'s `dependencies` object. If it does AND the spec directory exists in `<deps_dir>`, print a message indicating the spec is already installed and suggest `opensdd update` instead. Exit with code 1. If the entry exists BUT the spec directory is missing, treat as a re-install: log a message noting the stale entry, then continue to step 4 using the version from the existing entry (unless `[version]` is explicitly provided, in which case use that).
+2. Check if the spec `<name>` already exists as a key in `opensdd.json`'s `dependencies` object. If it does AND the spec directory exists in `<depsDir>`, print a message indicating the spec is already installed and suggest `opensdd update` instead. Exit with code 1. If the entry exists BUT the spec directory is missing, treat as a re-install: log a message noting the stale entry, then continue to step 4 using the version from the existing entry (unless `[version]` is explicitly provided, in which case use that).
 3. Validate the spec name (lowercase alphanumeric and hyphens only).
 4. Fetch `index.json` from `registry/<name>/` in the configured registry source. If `[version]` is provided, use that version; otherwise use `latest` from `index.json`.
-5. Read `manifest.json` from `registry/<name>/<version>/` to get spec_format and dependencies.
-6. Copy all files from `registry/<name>/<version>/` into `<deps_dir>/<name>/` (including `manifest.json`, `spec.md`, and any supplementary files).
-7. Add an entry to `opensdd.json` under `dependencies.<name>` with fields from `manifest.json` (`version`, `spec_format`), the resolved registry URL as `source`, and consumer-managed fields initialized to defaults: `implementation: null`, `tests: null`, `has_deviations: false`.
+5. Read `manifest.json` from `registry/<name>/<version>/` to get specFormat and dependencies.
+6. Copy all files from `registry/<name>/<version>/` into `<depsDir>/<name>/` (including `manifest.json`, `spec.md`, and any supplementary files).
+7. Add an entry to `opensdd.json` under `dependencies.<name>` with fields from `manifest.json` (`version`, `specFormat`), the resolved registry URL as `source`, and consumer-managed fields initialized to defaults: `implementation: null`, `tests: null`, `hasDeviations: false`.
 8. If the spec has `dependencies`, check whether each dependency name exists as a key in `opensdd.json`'s `dependencies` object. If any are missing, print a warning listing the missing dependencies and suggesting `opensdd install` for each.
 9. Print a success message.
 
@@ -310,15 +310,15 @@ Fetches the latest version of installed dependency specs from the registry, upda
 
 1. If `<name>` is provided, update that single spec. If no name is provided, update all installed dependencies.
 2. For each spec being updated:
-   a. Read the spec's entry in `opensdd.json` `dependencies` to get the installed version and `spec_format` version.
+   a. Read the spec's entry in `opensdd.json` `dependencies` to get the installed version and `specFormat` version.
    b. Fetch `index.json` from the registry to get the latest version. Read `manifest.json` from the latest version directory.
    c. If the registry version matches the installed version, skip with a message "already up to date".
    d. Before overwriting, compute unified diffs of all spec-owned files that will change.
-   e. Overwrite all spec-owned files in `<deps_dir>/<name>/` with the new version from the registry (`manifest.json`, `spec.md`, and any supplementary files).
+   e. Overwrite all spec-owned files in `<depsDir>/<name>/` with the new version from the registry (`manifest.json`, `spec.md`, and any supplementary files).
    f. MUST NOT overwrite or delete `deviations.md`. The CLI MUST NOT create, modify, or delete `deviations.md` under any circumstances.
    g. Create the staging directory `.opensdd.deps/.updates/<name>/` and write two files. If a pending update already exists for this spec, overwrite it and note the replacement in the output.
-      - `changeset.md` — contains previous and new version, `spec_format` version change (if any), and unified diffs from step (d).
-      - `manifest.json` — contains the metadata needed to finalize the update in `opensdd.json`: `name`, `previous_version`, `version`, `source`, `spec_format`.
+      - `changeset.md` — contains previous and new version, `specFormat` version change (if any), and unified diffs from step (d).
+      - `manifest.json` — contains the metadata needed to finalize the update in `opensdd.json`: `name`, `previousVersion`, `version`, `source`, `specFormat`.
 3. Print a summary of what was updated.
 
 #### Input
@@ -376,7 +376,7 @@ Applies a staged update to `opensdd.json`, confirming that the migration is comp
 3. Prompt the user for confirmation (y/n). If declined, exit with code 0.
 4. For each pending update:
    a. Read `.opensdd.deps/.updates/<name>/manifest.json` to get the update metadata.
-   b. Update the `opensdd.json` `dependencies.<name>` entry: set `version`, `source`, and `spec_format` from the manifest. Preserve all consumer-managed fields (`implementation`, `tests`, `has_deviations`).
+   b. Update the `opensdd.json` `dependencies.<name>` entry: set `version`, `source`, and `specFormat` from the manifest. Preserve all consumer-managed fields (`implementation`, `tests`, `hasDeviations`).
    c. Delete the `.opensdd.deps/.updates/<name>/` directory.
 5. If `.opensdd.deps/.updates/` is now empty, delete it.
 6. Print a summary.
@@ -431,14 +431,14 @@ Publishes an authored spec to the registry.
 
 1. Verify `opensdd.json` exists at the project root. If not, print a message suggesting `opensdd init` first and exit with code 1.
 2. Verify `opensdd.json` has a `publish` object. If not, print an error suggesting the user add a `publish` section and exit with code 1.
-3. Read the `publish` object to get `name`, `version`, `description`, `spec_format`, `dependencies`.
-4. Verify `<specs_dir>/spec.md` exists. If not, print error and exit with code 1.
-5. Run validation on the `<specs_dir>/` directory (same logic as `opensdd validate`). If validation fails with errors, print them and exit with code 1.
+3. Read the `publish` object to get `name`, `version`, `description`, `specFormat`, `dependencies`.
+4. Verify `<specsDir>/spec.md` exists. If not, print error and exit with code 1.
+5. Run validation on the `<specsDir>/` directory (same logic as `opensdd validate`). If validation fails with errors, print them and exit with code 1.
 6. Resolve the registry source. The registry MUST be a GitHub repository URL for publishing.
 7. Fetch `index.json` from `registry/<name>/` if it exists. If the version being published already exists in `index.json`, print error suggesting a version bump and exit with code 1.
 8. Construct the registry entry:
-   a. Build `manifest.json` from the `opensdd.json` `publish` fields (`name`, `version`, `description`, `spec_format`, `dependencies`).
-   b. Collect all files from `<specs_dir>/`.
+   a. Build `manifest.json` from the `opensdd.json` `publish` fields (`name`, `version`, `description`, `specFormat`, `dependencies`).
+   b. Collect all files from `<specsDir>/`.
 9. If `--branch <name>` was provided, use that as the branch name. Otherwise, prompt the user for a branch name.
 10. Clone the registry repo (shallow), create a new branch with the chosen name, and:
     a. Create `registry/<name>/<version>/` with `manifest.json` and all spec files.
@@ -472,7 +472,7 @@ Published. Spec will be available after PR is merged.
 
 - OpenSDD not initialized: print message suggesting `opensdd init` and exit with code 1.
 - No `publish` section in `opensdd.json`: print error and exit with code 1.
-- `<specs_dir>/spec.md` missing: print error and exit with code 1.
+- `<specsDir>/spec.md` missing: print error and exit with code 1.
 - Spec validation fails: print validation errors and exit with code 1.
 - Version already exists in registry: print error suggesting version bump and exit with code 1.
 - Registry is not a GitHub URL: print error (publishing requires a GitHub registry) and exit with code 1.
@@ -487,8 +487,8 @@ Shows the status of the authored spec and all installed dependency specs in the
 
 1. Read `opensdd.json`.
 2. If `publish` exists, print authored spec section showing the spec's name, version, and directory.
-3. If `dependencies` exists and has entries, iterate the `dependencies` object. For each entry, read its consumer-managed fields and check for the presence of `deviations.md` in `<deps_dir>/<name>/`. Print a dependency status table.
-4. Check for untracked directories: spec directories in `<deps_dir>` that have no corresponding `opensdd.json` dependency entry. Warn about any found.
+3. If `dependencies` exists and has entries, iterate the `dependencies` object. For each entry, read its consumer-managed fields and check for the presence of `deviations.md` in `<depsDir>/<name>/`. Print a dependency status table.
+4. Check for untracked directories: spec directories in `<depsDir>` that have no corresponding `opensdd.json` dependency entry. Warn about any found.
 
 #### Output
 
@@ -520,7 +520,7 @@ Validates that a spec directory conforms to the OpenSDD spec-format.
 3. Check for required files: `spec.md` MUST exist.
 4. If `manifest.json` exists, validate it:
    a. `name` MUST be present.
-   b. `spec_format` MUST be present and be a recognized version.
+   b. `specFormat` MUST be present and be a recognized version.
    c. `version` MUST be present and be valid semver.
 5. Validate `spec.md`:
    a. MUST start with an H1 header followed by a blockquote summary.
@@ -607,7 +607,7 @@ For local paths, the CLI MUST read directly from the filesystem. This supports d
 During `opensdd update apply`, the CLI MUST preserve these `opensdd.json` fields for each affected dependency entry:
 - `implementation`
 - `tests`
-- `has_deviations`
+- `hasDeviations`
 
 The CLI reads the existing `opensdd.json` dependency entry, applies updated metadata from the staged manifest, then re-applies the consumer-managed field values. Note that `opensdd update` does NOT touch `opensdd.json` at all — it only stages the update. The `opensdd.json` entry continues to reflect the old version until `opensdd update apply` is called.
 
@@ -651,7 +651,7 @@ The CLI reads the existing `opensdd.json` dependency entry, applies updated meta
 - The Claude Code skill installation (`.claude/skills/`) MUST always be present since Gemini CLI and Amp reference it
 - `opensdd.json` MUST be created by `opensdd init` if it does not exist, and MUST NOT be overwritten if it already exists
 - Consumer-managed `opensdd.json` fields MUST survive all update operations
-- Every installed dependency MUST have both a directory in `deps_dir` and an entry in `opensdd.json` `dependencies`
+- Every installed dependency MUST have both a directory in `depsDir` and an entry in `opensdd.json` `dependencies`
 - All commands MUST exit with code 0 on success and code 1 on error
 - The CLI MUST NOT invoke an AI model or coding agent
 - `opensdd publish` MUST NOT allow overwriting an existing version in the registry

package/opensdd/skills/sdd-generate.md

@@ -17,7 +17,7 @@ Before starting, you need:
 1. A **target repository** — a GitHub URL or local path provided by the user.
 2. A **scope** — which capability, module, or function to spec. If the user provides a whole-repo URL without scoping, ask them to narrow it before proceeding. A spec for "the entire lodash library" is not useful. A spec for "lodash's string slugification" is.
 3. The **spec-format reference** — read [spec-format.md](../spec-format.md) to understand the required output structure.
-4. A **working directory** — confirm with the user where the generated spec should be written. If the project has `opensdd.json`, use the directory specified by `specs_dir` (default: `opensdd/`). If the project is not yet initialized, ask the user where to output the spec — a common default is `opensdd/` in the current project root. The agent does not need `opensdd.json` to exist before generating a spec.
+4. A **working directory** — confirm with the user where the generated spec should be written. If the project has `opensdd.json`, use the directory specified by `specsDir` (default: `opensdd/`). If the project is not yet initialized, ask the user where to output the spec — a common default is `opensdd/` in the current project root. The agent does not need `opensdd.json` to exist before generating a spec.
 
 ## Output
 
@@ -38,7 +38,7 @@ If `opensdd.json` exists, add or update the `publish` object:
     "name": "{name}",
     "version": "{semver}",
     "description": "{one-line description}",
-    "spec_format": "0.1.0",
+    "specFormat": "0.1.0",
     "dependencies": []
   }
 }
@@ -164,7 +164,7 @@ Always update `_notes/gaps.md` at the end of each pass with what still needs to
   - `## NOT Specified (Implementation Freedom)` — list implementation choices observed in the source that the spec intentionally leaves open (data structures, algorithms, caching, internal architecture)
   - `## Invariants` — universal properties extracted from property tests, type constraints, or behavioral patterns (e.g., idempotency, commutativity, output format guarantees)
   - `## Implementation Hints` (optional) — guidance on performance, concurrency, or common pitfalls observed in the source, only if genuinely useful. If the spec targets a specific platform, hints MAY be platform-specific; otherwise they SHOULD be language-agnostic.
-- If `opensdd.json` exists, add or update the `publish` object with name, version, description, spec_format, and dependencies from `_notes/scope.md`.
+- If `opensdd.json` exists, add or update the `publish` object with name, version, description, specFormat, and dependencies from `_notes/scope.md`.
 
 **Validate the output:**
 - MUST have H1 header with blockquote summary and `## Behavioral Contract`

package/opensdd/skills/sdd-manager.md

@@ -40,7 +40,7 @@ The dependency spec (`spec.md`) is the authoritative description of what to buil
 
 5. **Verify:** Execute the full verification protocol (see Verification Protocol section below): generate test suite → run tests until all pass (or SHOULD bail after 50 attempts) → dispatch subagent for spec compliance audit → fix any findings → re-run tests.
 
-6. **Record:** Update `opensdd.json` `dependencies` entry with `implementation` path, `tests` path, and `has_deviations` if applicable.
+6. **Record:** Update `opensdd.json` `dependencies` entry with `implementation` path, `tests` path, and `hasDeviations` if applicable.
 
 7. **Report:** Report results with spec coverage summary.
 
@@ -59,7 +59,7 @@ Run existing test suite → report pass/fail. If test suite is missing or stale,
 
 ### Create Deviation
 
-Determine affected spec section → classify type → create/append to `deviations.md` in `.opensdd.deps/<name>/` → update test suite to skip affected tests → update `has_deviations` in `opensdd.json`.
+Determine affected spec section → classify type → create/append to `deviations.md` in `.opensdd.deps/<name>/` → update test suite to skip affected tests → update `hasDeviations` in `opensdd.json`.
 
 ## Universal Implementation Defaults
 

package/opensdd/spec-format.md

@@ -48,7 +48,7 @@ A spec is a directory containing spec files. The directory name is the bare spec
 
 In the registry and in installed dependency specs (`.opensdd.deps/`), every spec directory MUST contain:
 
-- `manifest.json` — Metadata about the spec (name, version, spec_format, description, dependencies).
+- `manifest.json` — Metadata about the spec (name, version, specFormat, description, dependencies).
 - `spec.md` — The behavioral contract and acceptance criteria. The spec IS the acceptance criteria — a well-written spec contains everything needed to both implement and verify the software.
 
 For the authored spec (`opensdd/`), the directory contains `spec.md` and any supplementary files. The metadata that would be in `manifest.json` lives in the `opensdd.json` `publish` entry instead; a separate `manifest.json` file is constructed during publishing.
@@ -255,23 +255,23 @@ The `opensdd.json` file is the project-level manifest. It lives at the project r
 {
   "opensdd": "0.1.0",
   "registry": "https://github.com/deepagents-ai/opensdd",
-  "specs_dir": "opensdd",
-  "deps_dir": ".opensdd.deps",
+  "specsDir": "opensdd",
+  "depsDir": ".opensdd.deps",
   "publish": {
     "name": "auth",
     "version": "1.0.0",
     "description": "Authentication with multiple provider support",
-    "spec_format": "0.1.0",
+    "specFormat": "0.1.0",
     "dependencies": []
   },
   "dependencies": {
     "slugify": {
       "version": "2.1.0",
       "source": "https://github.com/deepagents-ai/opensdd",
-      "spec_format": "0.1.0",
+      "specFormat": "0.1.0",
       "implementation": null,
       "tests": null,
-      "has_deviations": false
+      "hasDeviations": false
     }
   }
 }
@@ -281,8 +281,8 @@ The `opensdd.json` file is the project-level manifest. It lives at the project r
 
 - `opensdd` (required): Protocol version string. Agents and the CLI MUST use this to determine how to interpret the manifest.
 - `registry` (optional): URL of the default registry. Overridden by the CLI's `--registry` flag. Default: `"https://github.com/deepagents-ai/opensdd"`.
-- `specs_dir` (optional): Relative path from the project root to the directory containing the authored spec. Default: `"opensdd"`.
-- `deps_dir` (optional): Relative path from the project root to the directory containing installed dependency specs. Default: `".opensdd.deps"`.
+- `specsDir` (optional): Relative path from the project root to the directory containing the authored spec. Default: `"opensdd"`.
+- `depsDir` (optional): Relative path from the project root to the directory containing installed dependency specs. Default: `".opensdd.deps"`.
 - `publish` (optional): Object defining the spec this project publishes. Omit if the project only consumes specs.
 - `dependencies` (optional): Object keyed by spec name. Each entry tracks an installed dependency spec. Omit if the project only publishes specs.
 
@@ -291,17 +291,17 @@ The `opensdd.json` file is the project-level manifest. It lives at the project r
 - `name` (required): Bare spec name — lowercase alphanumeric and hyphens only.
 - `version` (required): Semver version of the spec being developed.
 - `description` (required): One-line description for registry display.
-- `spec_format` (required): Which version of the OpenSDD protocol this spec targets.
+- `specFormat` (required): Which version of the OpenSDD protocol this spec targets.
 - `dependencies` (optional): Array of bare spec names that this spec references for shared types or behavioral contracts.
 
 #### Dependency entry fields
 
 - `version` (required): Semver version of the installed spec.
 - `source` (required): URL of the registry this spec was installed from.
-- `spec_format` (required): OpenSDD protocol version of the installed spec.
+- `specFormat` (required): OpenSDD protocol version of the installed spec.
 - `implementation` (consumer-managed): Path to the generated implementation file, `null` until implemented.
 - `tests` (consumer-managed): Path to the generated test file, `null` until implemented.
-- `has_deviations` (consumer-managed): Boolean, `false` until a deviation is created.
+- `hasDeviations` (consumer-managed): Boolean, `false` until a deviation is created.
 
 Consumer-managed fields MUST be present with explicit `null` or `false` values rather than omitted. Fields MUST survive all update operations.
 
@@ -338,8 +338,8 @@ Each spec in the registry MUST have an `index.json` at its root:
   "description": "String to URL-friendly slug",
   "latest": "2.2.0",
   "versions": {
-    "2.1.0": { "spec_format": "0.1.0" },
-    "2.2.0": { "spec_format": "0.1.0" }
+    "2.1.0": { "specFormat": "0.1.0" },
+    "2.2.0": { "specFormat": "0.1.0" }
   }
 }
 ```
@@ -347,7 +347,7 @@ Each spec in the registry MUST have an `index.json` at its root:
 - `name` (required): Bare spec name.
 - `description` (required): One-line description.
 - `latest` (required): The most recent published version.
-- `versions` (required): Object keyed by semver version string. Each entry MAY include summary metadata (e.g., `spec_format`).
+- `versions` (required): Object keyed by semver version string. Each entry MAY include summary metadata (e.g., `specFormat`).
 
 #### manifest.json (per version)
 
@@ -357,7 +357,7 @@ Each version directory MUST contain a `manifest.json`:
 {
   "name": "slugify",
   "version": "2.2.0",
-  "spec_format": "0.1.0",
+  "specFormat": "0.1.0",
   "description": "String to URL-friendly slug",
   "dependencies": []
 }
@@ -365,7 +365,7 @@ Each version directory MUST contain a `manifest.json`:
 
 - `name` (required): Bare spec name.
 - `version` (required): Semver version of this entry.
-- `spec_format` (required): OpenSDD protocol version.
+- `specFormat` (required): OpenSDD protocol version.
 - `description` (required): One-line description.
 - `dependencies` (optional): Array of bare spec names.
 
@@ -429,10 +429,10 @@ Contains the metadata needed to finalize the `opensdd.json` dependency entry whe
 ```json
 {
   "name": "slugify",
-  "previous_version": "2.1.0",
+  "previousVersion": "2.1.0",
   "version": "2.2.0",
   "source": "https://github.com/deepagents-ai/opensdd",
-  "spec_format": "0.1.0"
+  "specFormat": "0.1.0"
 }
 ```
 
@@ -484,7 +484,7 @@ Specs use semantic versioning:
 - Spec-owned files in `.opensdd.deps/` MUST NOT be modified by the consumer or their agent
 - `deviations.md` MUST NOT be created, modified, or deleted by the CLI or any automated tooling
 - Consumer-managed fields in `opensdd.json` MUST survive all update operations
-- Every installed dependency spec MUST have both a directory in `deps_dir` and an entry in `opensdd.json` `dependencies`
+- Every installed dependency spec MUST have both a directory in `depsDir` and an entry in `opensdd.json` `dependencies`
 - All behaviors described in the spec MUST be thoroughly tested by the implementing agent
 - A `spec.md` MUST contain an H1 header with blockquote summary and a `## Behavioral Contract` section
 - `deviations.md` MUST only be created when a deviation actually exists

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opensdd",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "The official OpenSDD (Open Spec-Driven Development) CLI, spec, and spec registry",
   "type": "module",
   "bin": {
@@ -15,7 +15,7 @@
     "node": ">=18.0.0"
   },
   "scripts": {
-    "test": "node --test test/**/*.test.js"
+    "test": "echo '\\n========== TESTS BEGIN ==========\\n' && node --test test/**/*.test.js; EXIT=$?; echo '\\n========== TESTS END ==========\\n'; exit $EXIT"
   },
   "keywords": [
     "opensdd",

package/src/commands/init.js

@@ -118,15 +118,15 @@ export async function initCommand() {
   if (!manifest) {
     manifest = {
       opensdd: '0.1.0',
-      specs_dir: 'opensdd',
-      deps_dir: '.opensdd.deps',
+      specsDir: 'opensdd',
+      depsDir: '.opensdd.deps',
     };
     fs.writeFileSync(manifestPath, JSON.stringify(manifest, null, 2) + '\n');
     manifestCreated = true;
   }
 
-  const specsDir = manifest.specs_dir || 'opensdd';
-  const depsDir = manifest.deps_dir || '.opensdd.deps';
+  const specsDir = manifest.specsDir || 'opensdd';
+  const depsDir = manifest.depsDir || '.opensdd.deps';
   const specsDirPath = path.join(cwd, specsDir);
   const depsDirPath = path.join(cwd, depsDir);
 

package/src/commands/install.js

@@ -132,10 +132,10 @@ export async function installCommand(name, version, options) {
   manifest.dependencies[name] = {
     version: resolvedVersion,
     source: registrySource,
-    spec_format: specManifest.spec_format || '0.1.0',
+    specFormat: specManifest.specFormat || '0.1.0',
     implementation: existingEntry?.implementation ?? null,
     tests: existingEntry?.tests ?? null,
-    has_deviations: existingEntry?.has_deviations ?? false,
+    hasDeviations: existingEntry?.hasDeviations ?? false,
   };
 
   writeManifest(manifestPath, manifest);

package/src/commands/publish.js

@@ -65,16 +65,16 @@ export async function publishCommand(options) {
   if (!manifest.publish) {
     console.error('Error: No `publish` section in opensdd.json.');
     console.error(
-      'Add a `publish` object with name, version, description, and spec_format to publish your spec.'
+      'Add a `publish` object with name, version, description, and specFormat to publish your spec.'
     );
     process.exit(1);
   }
 
-  const { name, version, description, spec_format, dependencies } = manifest.publish;
+  const { name, version, description, specFormat, dependencies } = manifest.publish;
 
-  if (!name || !version || !description || !spec_format) {
+  if (!name || !version || !description || !specFormat) {
     console.error(
-      'Error: `publish` section must include name, version, description, and spec_format.'
+      'Error: `publish` section must include name, version, description, and specFormat.'
     );
     process.exit(1);
   }
@@ -169,7 +169,7 @@ export async function publishCommand(options) {
     const publishManifest = {
       name,
       version,
-      spec_format,
+      specFormat,
       description,
       dependencies: dependencies || [],
     };
@@ -192,7 +192,7 @@ export async function publishCommand(options) {
       indexData = { name, description, latest: version, versions: {} };
     }
     indexData.latest = version;
-    indexData.versions[version] = { spec_format };
+    indexData.versions[version] = { specFormat };
     fs.writeFileSync(indexPath, JSON.stringify(indexData, null, 2) + '\n');
     console.log(`  Updated index.json        latest: ${version}`);
 

package/src/commands/status.js

@@ -53,7 +53,7 @@ export async function statusCommand() {
       // Check for deviations
       let deviationInfo = '';
       const deviationsPath = path.join(projectRoot, depsDir, depName, 'deviations.md');
-      if (entry.has_deviations || fs.existsSync(deviationsPath)) {
+      if (entry.hasDeviations || fs.existsSync(deviationsPath)) {
         if (fs.existsSync(deviationsPath)) {
           const content = fs.readFileSync(deviationsPath, 'utf-8');
           const deviationCount = (content.match(/^## /gm) || []).length;

package/src/commands/update.js

@@ -115,8 +115,8 @@ export async function updateCommand(name, options) {
     fs.mkdirSync(updatesDir, { recursive: true });
 
     // Write changeset.md
-    const specFormatOld = entry.spec_format || '0.1.0';
-    const specFormatNew = newManifest.spec_format || '0.1.0';
+    const specFormatOld = entry.specFormat || '0.1.0';
+    const specFormatNew = newManifest.specFormat || '0.1.0';
     const specFormatChange =
       specFormatOld === specFormatNew
         ? 'unchanged'
@@ -142,10 +142,10 @@ export async function updateCommand(name, options) {
     // Write manifest.json for staging
     const stageManifest = {
       name: specName,
-      previous_version: entry.version,
+      previousVersion: entry.version,
       version: latestVersion,
       source: registrySource,
-      spec_format: newManifest.spec_format || '0.1.0',
+      specFormat: newManifest.specFormat || '0.1.0',
     };
 
     fs.writeFileSync(

package/src/commands/updateApply.js

@@ -64,7 +64,7 @@ export async function updateApplyCommand(name) {
   if (pendingNames.length === 1) {
     const updateManifestPath = path.join(updatesDir, pendingNames[0], 'manifest.json');
     const updateManifest = JSON.parse(fs.readFileSync(updateManifestPath, 'utf-8'));
-    confirmMsg = `Apply update for ${pendingNames[0]} v${updateManifest.previous_version} -> v${updateManifest.version}? (y/n) `;
+    confirmMsg = `Apply update for ${pendingNames[0]} v${updateManifest.previousVersion} -> v${updateManifest.version}? (y/n) `;
   } else {
     confirmMsg = `Apply ${pendingNames.length} pending updates? (y/n) `;
   }
@@ -103,13 +103,13 @@ export async function updateApplyCommand(name) {
       ...existing,
       version: updateManifest.version,
       source: updateManifest.source,
-      spec_format: updateManifest.spec_format,
+      specFormat: updateManifest.specFormat,
       // Preserve consumer-managed fields
       implementation:
         existing.implementation !== undefined ? existing.implementation : null,
       tests: existing.tests !== undefined ? existing.tests : null,
-      has_deviations:
-        existing.has_deviations !== undefined ? existing.has_deviations : false,
+      hasDeviations:
+        existing.hasDeviations !== undefined ? existing.hasDeviations : false,
     };
 
     // Delete staging directory
@@ -117,7 +117,7 @@ export async function updateApplyCommand(name) {
 
     applied.push({
       name: specName,
-      oldVersion: updateManifest.previous_version,
+      oldVersion: updateManifest.previousVersion,
       newVersion: updateManifest.version,
     });
   }

package/src/lib/manifest.js

@@ -30,9 +30,9 @@ export function writeManifest(manifestPath, data) {
 }
 
 export function getSpecsDir(manifest) {
-  return manifest.specs_dir || 'opensdd';
+  return manifest.specsDir || 'opensdd';
 }
 
 export function getDepsDir(manifest) {
-  return manifest.deps_dir || '.opensdd.deps';
+  return manifest.depsDir || '.opensdd.deps';
 }

package/src/lib/validation.js

@@ -105,9 +105,9 @@ function validateManifest(manifest, result) {
     result.errors.push('manifest.json: Missing name');
   }
 
-  if (!manifest.spec_format) {
-    result.manifestErrors.push('Missing required field: spec_format');
-    result.errors.push('manifest.json: Missing spec_format');
+  if (!manifest.specFormat) {
+    result.manifestErrors.push('Missing required field: specFormat');
+    result.errors.push('manifest.json: Missing specFormat');
   }
 
   if (!manifest.version) {