Initial Commit

openspec/package-cap-map.yml

@@ -0,0 +1,48 @@
+# Package → OpenSpec capability mapping.
+#
+# Most packages own a single capability whose folder name in `openspec/specs/`
+# matches the package's bare name (the part after `@suaveplan/`). For those
+# packages, no entry is needed here — the conformance script defaults to
+# `<bare> -> [<bare>]`.
+#
+# Add an entry below ONLY when:
+#   - The cap folder name differs from the package name (legacy rename, e.g. logger → logging).
+#   - One package owns multiple caps (e.g. random covers 4 specs).
+#   - One cap is shared by multiple packages (rare; document with a comment).
+#
+# Format:
+#   <bare-package-name>:
+#     - <cap-folder-name>
+#     - <another-cap>
+#
+# Convention: keys sorted alphabetically. One YAML doc; no nesting beyond array.
+
+# --- legacy cap rename ---
+db:
+  - database
+
+logger:
+  - logging
+
+serialize:
+  - serialization
+
+# --- crypto subpackages with engine-suffixed cap folders (from 2026-04-18-enterprise-crypto-family fold) ---
+crypto-browser:
+  - crypto-browser-engine
+
+crypto-sodium:
+  - crypto-sodium-engine
+
+# crypto-keys and crypto-vault use folder names equal to package name — no override needed.
+
+# --- multi-cap packages ---
+random:
+  - random-utilities
+  - seeded-prng
+  - noise-functions
+  - statistical-distributions
+
+# --- package contributes to a sibling's cap ---
+readline:
+  - cli  # readline primitives are specified inside the cli cap; the package ships them as a focused export.