chore(schemas): rename schemas.opendecree.io → schemas.opendecree.dev (#259)

Mechanical rename across docs, design brief, README, code, tests, and meta-schema YAML/JSON sources. Refs #125.

Author: zeevdr

.agents/context/schema-spec.md

@@ -54,10 +54,10 @@ All changes are **breaking**. Per project policy (no backward compat pre-product
 ### Final top-level shape (v0.1.0)
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree.json
 
 spec_version: v1                          # required, const "v1" (the decree format version)
-$schema: https://schemas.opendecree.io/schema/v0.1.0/decree.json  # optional
+$schema: https://schemas.opendecree.dev/schema/v0.1.0/decree.json  # optional
 $id: urn:decree:schema:payments:v3        # optional
 name: payments                            # required, slug ^[a-z0-9]([a-z0-9-]*[a-z0-9])?$
 description: Payments service config      # optional
@@ -140,12 +140,12 @@ Meta-schema encodes this via `allOf` with 4 `if/then` branches keyed on `type`.
 
 - **Canonical filenames:** `decree.schema.yaml`, `decree.config.yaml`
 - **Generic globs:** `*.decree.schema.yaml`, `*.decree.config.yaml` (for repos with multiple schemas)
-- **Modeline:** `# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree.json` on line 1 of every example
+- **Modeline:** `# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree.json` on line 1 of every example
 - **CLI stays filename-agnostic** — `decree apply some-other-name.yaml` must keep working. The convention drives editor discovery only.
 
 ## Publishing
 
-- **URL pattern:** `https://schemas.opendecree.io/schema/v{MAJOR}.{MINOR}.{PATCH}/decree.json`
+- **URL pattern:** `https://schemas.opendecree.dev/schema/v{MAJOR}.{MINOR}.{PATCH}/decree.json`
 - **Pre-stable:** full SemVer in path (`/v0.1.0/`)
 - **Post-1.0.0:** switch to major-only paths (`/v1/`) with permanent redirects from historical full-SemVer URLs
 - **Hosting:** TBD (GitHub Pages on a dedicated repo, or static-hosted redirect to raw GitHub content). Must be HTTPS, stable, `Content-Type: application/schema+json`.
@@ -155,7 +155,7 @@ Meta-schema encodes this via `allOf` with 4 `if/then` branches keyed on `type`.
     "name": "OpenDecree Schema",
     "description": "OpenDecree configuration schema",
     "fileMatch": ["decree.schema.yaml", "decree.schema.yml", "*.decree.schema.yaml", "*.decree.schema.yml"],
-    "url": "https://schemas.opendecree.io/schema/v0.1.0/decree.json"
+    "url": "https://schemas.opendecree.dev/schema/v0.1.0/decree.json"
   }
   ```
 
@@ -191,7 +191,7 @@ Meta-schema encodes this via `allOf` with 4 `if/then` branches keyed on `type`.
 
 ### Phase C — Publishing
 
-- #125 — Host meta-schema at `https://schemas.opendecree.io/schema/v0.1.0/decree.json`
+- #125 — Host meta-schema at `https://schemas.opendecree.dev/schema/v0.1.0/decree.json`
 - #126 — Submit schemastore.org PR
 
 ### Phase D — Docs
@@ -205,7 +205,7 @@ Meta-schema encodes this via `allOf` with 4 `if/then` branches keyed on `type`.
 
 ## Open questions
 
-- **Hosting target for `schemas.opendecree.io`** — dedicated GitHub Pages repo? Cloudflare redirect to raw GitHub content? Needs DNS + CORS setup.
+- **Hosting target for `schemas.opendecree.dev`** — dedicated GitHub Pages repo? Cloudflare redirect to raw GitHub content? Needs DNS + CORS setup.
 - **Bundling tool** — hand-rolled Python script vs off-the-shelf (e.g. `json-dereference-cli`). Go with off-the-shelf if one exists and is maintained.
 - **Does the CLI emit `$schema`/`$id` on export?** — `decree schema export` should probably inject `$schema` by default, make `$id` opt-in.
 - **Post-v1.0.0 URL migration** — when the spec promotes to 1.0.0, keep `/v0.1.0/` live forever or redirect? Preserve forever matches OpenAPI's dated-URL practice.

README.md

@@ -336,8 +336,8 @@ Values use a `TypedValue` oneof — integer, number, string, bool, timestamp, du
 
 The schema YAML format authors write to define their config shape is documented in [Schema Format](docs/concepts/schema-format.md). The corresponding [JSON Schema 2020-12 meta-schemas](docs/concepts/meta-schema.md) for editor IntelliSense and CI validation are published at:
 
-- `https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json` — validates `*.decree.schema.yaml`
-- `https://schemas.opendecree.io/schema/v0.1.0/decree-config.json` — validates `*.decree.config.yaml`
+- `https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json` — validates `*.decree.schema.yaml`
+- `https://schemas.opendecree.dev/schema/v0.1.0/decree-config.json` — validates `*.decree.config.yaml`
 
 All endpoints that accept a tenant or schema ID also accept the **name slug** — the server resolves automatically. Use UUIDs or human-readable names interchangeably:
 

docs/concepts/meta-schema.md

@@ -45,7 +45,7 @@ YAML is the human-edited source of truth. JSON copies are generated by [`scripts
 Add the modeline on line 1 of your schema or config file. VS Code, Neovim, IntelliJ, Helix, and Zed via [yaml-language-server](https://github.com/redhat-developer/yaml-language-server) auto-apply the schema for autocompletion and inline error highlighting:
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json
 spec_version: v1
 name: payments
 fields:
@@ -56,7 +56,7 @@ fields:
 For config files:
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-config.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-config.json
 spec_version: v1
 values:
   payments.fee:
@@ -70,11 +70,11 @@ Run [`check-jsonschema`](https://github.com/python-jsonschema/check-jsonschema)
 ```bash
 pip install check-jsonschema
 check-jsonschema \
-  --schemafile https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json \
+  --schemafile https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json \
   '**/*.decree.schema.yaml'
 
 check-jsonschema \
-  --schemafile https://schemas.opendecree.io/schema/v0.1.0/decree-config.json \
+  --schemafile https://schemas.opendecree.dev/schema/v0.1.0/decree-config.json \
   '**/*.decree.config.yaml'
 ```
 
@@ -92,10 +92,10 @@ Any [JSON Schema 2020-12 validator](https://json-schema.org/implementations) can
 ## URL scheme + versioning
 
 ```
-https://schemas.opendecree.io/schema/v{MAJOR}.{MINOR}.{PATCH}/decree-{schema|config}.json
+https://schemas.opendecree.dev/schema/v{MAJOR}.{MINOR}.{PATCH}/decree-{schema|config}.json
 ```
 
-**Pre-stable (current):** full SemVer in the path — `https://schemas.opendecree.io/schema/v0.1.0/...`. Each release of the meta-schema is published at its exact version path forever; older versions stay reachable for tools that pin a specific version.
+**Pre-stable (current):** full SemVer in the path — `https://schemas.opendecree.dev/schema/v0.1.0/...`. Each release of the meta-schema is published at its exact version path forever; older versions stay reachable for tools that pin a specific version.
 
 **Post-1.0.0 (future):** switch to major-only paths (`/v1/`) with permanent redirects from historical full-SemVer URLs. Matches the OpenAPI 3.x dated-URL practice.
 

docs/concepts/schema-format.md

@@ -14,18 +14,18 @@ The canonical reference for the **decree.schema.yaml** format — every top-leve
 Place the modeline on line 1 of every file so editors with [yaml-language-server](https://github.com/redhat-developer/yaml-language-server) auto-apply schema validation and IntelliSense:
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json
 ```
 
 The CLI is filename-agnostic — `decree apply some-other-name.yaml` keeps working. The convention drives editor discovery only.
 
 ## Top-level shape
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json
 
 spec_version: v1                                # required, const "v1"
-$schema: https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json  # optional
+$schema: https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json  # optional
 $id: urn:decree:schema:payments:v3              # optional URN
 
 name: payments                                  # required slug

docs/concepts/schemas-and-fields.md

@@ -30,7 +30,7 @@ Published versions are immutable — you cannot change their fields. To evolve a
 A small schema in YAML:
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json
 spec_version: v1
 name: payments
 description: Payment processing configuration

docs/getting-started.md

@@ -36,7 +36,7 @@ export DECREE_SUBJECT=admin@example.com
 A schema defines the structure of your configuration — what fields exist, their types, and constraints. Create a file called `decree.schema.yaml` (or `<name>.decree.schema.yaml` if your repo holds multiple schemas):
 
 ```yaml
-# yaml-language-server: $schema=https://schemas.opendecree.io/schema/v0.1.0/decree-schema.json
+# yaml-language-server: $schema=https://schemas.opendecree.dev/schema/v0.1.0/decree-schema.json
 spec_version: "v1"
 name: payments
 description: Payment processing configuration

internal/schema/yaml.go

@@ -14,7 +14,7 @@ const (
 	yamlSpecVersionV1 = "v1"
 	// metaSchemaURL is the canonical URL of the meta-schema that validates
 	// decree.schema.yaml documents at this spec version. Emitted on export.
-	metaSchemaURL = "https://schemas.opendecree.io/schema/v0.1.0/decree.json"
+	metaSchemaURL = "https://schemas.opendecree.dev/schema/v0.1.0/decree.json"
 )
 
 // schemaURNPattern matches decree schema URNs: urn:decree:schema:<segment>(:<segment>)*

internal/schema/yaml_test.go

@@ -307,9 +307,9 @@ func TestYAMLValidation_SchemaAndID(t *testing.T) {
 	})
 
 	t.Run("both accepted when well-formed", func(t *testing.T) {
-		doc, err := unmarshalSchemaYAML([]byte("spec_version: \"v1\"\n$schema: https://schemas.opendecree.io/schema/v0.1.0/decree.json\n$id: urn:decree:schema:test:v1" + validBody))
+		doc, err := unmarshalSchemaYAML([]byte("spec_version: \"v1\"\n$schema: https://schemas.opendecree.dev/schema/v0.1.0/decree.json\n$id: urn:decree:schema:test:v1" + validBody))
 		require.NoError(t, err)
-		assert.Equal(t, "https://schemas.opendecree.io/schema/v0.1.0/decree.json", doc.Schema)
+		assert.Equal(t, "https://schemas.opendecree.dev/schema/v0.1.0/decree.json", doc.Schema)
 		assert.Equal(t, "urn:decree:schema:test:v1", doc.ID)
 	})
 

schemas/v0.1.0/decree-config.json

@@ -1,6 +1,6 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "https://schemas.opendecree.io/schema/v0.1.0/decree-config.json",
+  "$id": "https://schemas.opendecree.dev/schema/v0.1.0/decree-config.json",
   "title": "OpenDecree Config Format (v0.1.0)",
   "description": "Tenant-side import format for OpenDecree config values. A decree.config.yaml file declares the values to apply against a previously imported schema; the server enforces type compatibility and cross-field rules at write time.",
   "type": "object",

schemas/v0.1.0/decree-config.yaml

@@ -13,7 +13,7 @@
 # may consume either.
 
 $schema: "https://json-schema.org/draft/2020-12/schema"
-$id: "https://schemas.opendecree.io/schema/v0.1.0/decree-config.json"
+$id: "https://schemas.opendecree.dev/schema/v0.1.0/decree-config.json"
 title: OpenDecree Config Format (v0.1.0)
 description: >-
   Tenant-side import format for OpenDecree config values. A