Skip to content

fix(registry): add dependencies key to 6 components and break self-dependency cycle - #359

Open
FlintsXzzz wants to merge 1 commit into
darrenhinde:mainfrom
FlintsXzzz:fix/registry-hygiene
Open

FlintsXzzz wants to merge 1 commit into
darrenhinde:mainfrom
FlintsXzzz:fix/registry-hygiene

Conversation

@FlintsXzzz

Copy link
Copy Markdown

Two small, provable hygiene fixes to .opencode/registry.json:

  1. Self-cycle removalcontexts/external-libraries-workflow listed itself in
    dependencies. Removed the self-reference; the two real dependencies are kept.

  2. Missing dependencies key — 6 components omitted the key that every other
    component declares (matching the fix-registry.py writer convention):
    commands/analyze-patterns, contexts/visual-development, contexts/learning-readme,
    contexts/product-readme, contexts/data-readme, contexts/context-bundle-template
    (templates/ entry only; blueprints/ entry already has the key).

Validated against CI validator:
./scripts/registry/validate-registry.sh -v → exit 0, 244/244 paths valid, 0 missing deps.

…pendency cycle

- external-libraries-workflow no longer depends on itself
- commands/analyze-patterns gains explicit dependencies: []
- contexts visual-development, learning-readme, product-readme,
  data-readme, and templates/context-bundle-template gain dependencies: []
- (blueprints/context-bundle-template already had the key)

Header footer alignment: registry formatVersion/schemaVersion untouched (schema is v2.0.0 by design).
Copilot AI lite review requested due to automatic review settings September 11, 2026 11:36

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Critical path and profile-schema regressions, plus dependency and duplicate-key issues, must be fixed.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR aims to normalize registry dependency metadata, but also introduces unrelated path, profile, dependency, and metadata changes.

Changes:

  • Adds empty dependencies arrays to six components.
  • Removes a self-dependency cycle.
  • Rewrites component paths and profile schema.
  • Removes existing dependencies and duplicates a location key.
File summaries
File Findings
registry.json Critical invalid paths (3 votes); Moderate removed dependencies (3 votes); Critical incompatible profile schema (3 votes); Moderate duplicate location key (1 vote).
Review details

Suppressed comments (12)

registry.json:2796

  • This entry now points at .opencode/context/core/context-system/guides/context-paths-config.md, which is not present; the existing file is .opencode/context/core/config/paths.json. check-dependencies.ts treats the latter as critical infrastructure, so this change makes the dependency checker report a missing critical file and breaks profile installation.
        "path": ".opencode/context/core/context-system/guides/context-paths-config.md",

registry.json:2806

  • root-navigation now points at .opencode/context/dev-navigation/navigation.md, but that file does not exist; the actual root navigation remains .opencode/context/navigation.md. The path validator will therefore fail and ContextScout/other agents that still reference the old root cannot discover context. Restore the existing path.
        "path": ".opencode/context/dev-navigation/navigation.md",

registry.json:2903

  • The new subagents.documentation object defines location twice. JSON parsers silently keep only the last duplicate key, leaving an ambiguous registry shape; remove the second location property.
      "location": "agent/subagents/core/documentation.md",

registry.json:2818

  • This changes the config entry from the existing root env.example to .opencode/config/env.example, which is not present in the repository. The validator checks config paths too, so this unrelated path rewrite adds a guaranteed missing registry entry; retain the existing path unless the file move is included.
        "path": ".opencode/config/env.example",

registry.json:2166

  • The navigation entries in this block are all redirected under .opencode/context/dev-navigation/, but that directory is absent; the repository's navigation files remain under their original .opencode/context/... locations. These paths cannot pass the registry validator or be installed. Revert these path changes unless the corresponding file moves are included.
        "path": ".opencode/context/dev-navigation/core/navigation.md",

registry.json:2838

  • This entry changes the existing root README.md to .opencode/config/readme.md, but the latter file is absent. That makes the config registry entry invalid under the repository's path validator and causes installers to resolve a file that cannot be fetched; keep the original path unless a matching file move is part of this change.
        "path": ".opencode/config/readme.md",

registry.json:1977

  • These project-intelligence entries are redirected into .opencode/context/core/task-management/standards/, but that target set of files does not exist; the repository still stores the project-intelligence documents under .opencode/context/project-intelligence/ (and the original standards paths). The registry validator and installers will treat these entries as missing. Restore the original paths unless the files are moved in the same change.
        "path": ".opencode/context/core/task-management/standards/project-intelligence.md",

registry.json:1727

  • The subagent-framework-maps, subagent-test-commands, and subagent-testing-modes entries are moved to guides/ paths that do not exist; the files remain under lookup/ and concepts/. Since registry validation checks these paths directly, this unrelated relocation creates missing components. Restore the existing paths unless the files are moved as part of this PR.
        "path": ".opencode/context/openagents-repo/guides/subagent-framework-maps.md",

registry.json:2057

  • Both workflow reference entries are redirected to new delegation-ref.md/review-ref.md files that are not present; the existing files are delegation.md and review.md. This causes missing registry paths and is unrelated to dependency hygiene, so retain the existing paths unless the files are added or moved here.
        "path": ".opencode/context/core/workflows/delegation-ref.md",

registry.json:2486

  • This workflow block redirects when-to-delegate, npm publishing, and GitHub issues to .opencode/context/core/workflows/, but those target files are absent; the existing files remain in development/frontend and openagents-repo/guides. The registry validator will reject these entries, so revert these unrelated path changes unless the files are moved too.
        "path": ".opencode/context/core/workflows/when-to-delegate.md",

registry.json:1667

  • These C# entries now point to .opencode/context/development/frameworks/, but the repository has the existing files under .opencode/context/core/standards/; the new framework paths are absent. The path validator and installers will therefore treat both C# components as missing. Restore the original paths unless the files are moved in this PR.
        "path": ".opencode/context/development/frameworks/csharp.md",

registry.json:1697

  • fullstack-navigation is redirected to .opencode/context/development/fullstack/navigation.md, but that file is absent; the existing file is .opencode/context/development/fullstack-navigation.md. This makes the registry path invalid and is unrelated to the dependency fixes. Restore the existing path.
        "path": ".opencode/context/development/fullstack/navigation.md",
  • Files reviewed: 1/1 changed files
  • Comments generated: 3
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread registry.json
"typescript",
"standards"
],
"path": ".opencode/context/development/frameworks/typescript.md",
Comment thread registry.json
"config:readme",
"context:openagents-repo/*"
]
"default": {
Comment thread registry.json
],
"description": "External context integration workflows",
"tags": [],
"dependencies": [],
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants