You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: OCX registry compatibility and profile support (#67)
* fix: OCX registry compatibility and profile support
- Fix CI workflow to copy registry output to docs site root (index.json
at /systematic/index.json, not /systematic/registry/index.json)
- Fix build script: include author field, strip v prefix from git tags,
add files:[] for bundle/plugin packuments, remove version from
component entries and packument version data
- Normalize target paths in build output (agents/ → agent/, commands/ →
command/) to match OCX's required singular directory names while
keeping plural in source
- Add profile components (standalone, omo) to registry with validation
- Fix .well-known/ocx.json registry path
- Update README and OCX guide with verified commands and profile docs
- Remove structural integrity tests (registry.test.ts)
* fix: harden registry build validation
- Refactor validateRegistry() to reduce cognitive complexity
- Resolve author from package.json when missing in registry source
- Harden git tag parsing to require semver or v-prefixed semver
- Add functional build-registry tests (validation, version errors,
target path normalization)
4. If the profile already exists, remove it first: `ocx profile rm <name>`
170
180
171
181
### Missing skills after OCX install
172
182
Individual skills installed via OCX do not automatically get "bootstrap injection" (the automatic loading of `using-systematic`). To get this feature, you must have the `@fro.bot/systematic` plugin installed in your project or globally.
@@ -176,6 +186,5 @@ If `ocx diff` shows differences but `ocx update` says you are up to date, the re
0 commit comments