docs: map CellFence package ownership - #37
Conversation
|
@Dibya0912 The current table covers the core packages, but please also list the remaining workspace packages explicitly, including:
The general note about |
aoto-tech
left a comment
There was a problem hiding this comment.
Thanks for the PR. I’m requesting changes for now because this does not yet satisfy the Issue #34 acceptance criterion that every current workspace package is represented.
Please add explicit entries for the remaining current workspace packages, including the adapter and plugin packages, rather than only describing plugin-* and adapter-* generally. Once each workspace package is visible in the package map, this should be ready for another look.
aoto-tech
left a comment
There was a problem hiding this comment.
@Dibya0912 Thanks for working on this. I still cannot merge it because #34 asks for every current workspace package to be represented. This table covers the main entry points, but it omits the adapter packages and several @cellfence/plugin-* packages. Please add all current packages and link the map from the README or another discoverable docs page, then rerun git diff --check.
7df9c4f to
39ca07b
Compare
|
@Dibya0912 I updated this PR to address the requested changes. The package ownership map now lists every current workspace package explicitly, including the adapter packages and all |
aoto-tech
left a comment
There was a problem hiding this comment.
Follow-up fixes landed and CI is green.
Related Issue
Closes #34
Description
Document which npm package owns each CellFence entry point, including the CLI, engine, schema, plugin API, GitHub Action, MCP proxy, trace utilities, baseline gate, and reporter. This gives new users and contributors a quick package-selection reference.
Validation
git diff --checkGenerative AI Disclosure