docs: document npm as a distribution channel#68
Conversation
Two follow-up edits to address review feedback on #67 (feat: ship as npm package via @netresearch/agent-skill-coordinator): - docs/ARCHITECTURE.md: add npm to the Distribution Channels section so future maintainers see it as a packaging surface that must be considered when changing release or distribution logic. - skills/github-project/references/multi-repo-operations.md: clarify that `package.json.version` parity rules differ by package type — skill packages use `0.0.0-source` (publish-time-rewritten); the coordinator-style packages keep parity with `plugin.json`. Resolves copilot-pull-request-reviewer threads PRRT_kwDOQoDmGs5_GzUj and PRRT_kwDOQoDmGs5_GzUo. Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Code Review
This pull request updates the project's documentation to include the npm distribution channel and clarifies versioning requirements for multi-repo operations, specifically regarding package.json placeholders. Feedback was provided to ensure consistency with the rule that composer.json should not contain a version field, to specify exact license filenames in the documentation, and to clarify confusing terminology where a package name was used as a version example.
There was a problem hiding this comment.
Pull request overview
Updates project documentation to explicitly include npm as a supported distribution channel and to refine version-parity guidance for repos that ship via npm (accounting for the 0.0.0-source placeholder pattern).
Changes:
- Document npm as an additional distribution channel alongside Composer, Claude plugin, npx/skills.sh, and manual installs.
- Clarify the multi-repo pre-flight version validation rules for npm-shipping repos, including the
0.0.0-sourceplaceholder case.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| docs/ARCHITECTURE.md | Adds npm to the Distribution Channels section and notes the npm files allowlist constraint. |
| skills/github-project/references/multi-repo-operations.md | Updates version-parity guidance to reflect npm placeholder vs released-version patterns. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…PR review) multi-repo-operations.md line 106 contradicted line 120: the pre-flight asked for plugin.json/composer.json version parity, but composer.json in Netresearch skill repos must NOT have a version field (Packagist derives versions from git tags). Replace with the correct negative assertion plus a SKILL.md frontmatter parity check. Also tighten line 107 to clarify that matching package.json.version applies to coordinator-style packages, not the example dependency. ARCHITECTURE.md line 34 used 'LICENSE files' as a placeholder inside an inline files array, which would be an invalid literal entry. Replace with the actual allowlist values (LICENSE-MIT, LICENSE-CC-BY-SA-4.0) so the snippet is copy-pasteable. Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
Summary
Two follow-up doc edits addressing review threads on #67 that were not fixed in the merged code:
docs/ARCHITECTURE.md: add npm to the Distribution Channels section. Previously listed only Composer, Claude Code plugin, npx/skills.sh, and manual installs — future maintainers wouldn't see npm as a packaging surface to consider.skills/github-project/references/multi-repo-operations.md: clarify the version-parity rule. The pre-merge guidance saidplugin.json.version/composer.json.version/package.json.versionmust all match — but skill packages intentionally ship0.0.0-sourceinpackage.json(publish-time rewritten), so blanket parity would flag the merged shape as broken.Addresses
package.json:3(PRRT_kwDOQoDmGs5_GzUj)README.md:137(PRRT_kwDOQoDmGs5_GzUo)Test plan