Understanding Expectations

[jklaus-work]

Hello,
I am looking for a level-set on what our expectations should be in terms of behavior.
We currently have a copilot plugin marketplace that we are considering changing over to APM. This is a mono-repo where the plugins live within the same repo as the marketplace. My understanding is that we are to apm init --marketplace in the root of the repo then down inside each of our ./plugins/{plugin-directory} we should apm init --plugin.
This gives us the following structure:

my-marketplace/
├── apm.yml
└── plugins/
    └── plugin-one/
        ├── apm.yml
        ├── plugin.json
        └── [plugin-content-files-here]

The marketplace level apm.yml would have:

...
marketplace:
  ...
  packages:
    - name: plugin-one
      source: ./plugins/plugin-one
      ...

The plugin level apm.yml & plugin.json files only contain the content that is populated during the init process, or should we be adding content to apm.dependencies.apm[] (specifically asking for locally referenced plugins)?

When running apm pack on the marketplace I see that a ./.claude-plugin/marketplace.json is generated and it matches the format for the copilot plugin marketplace json however when I add the apm marketplace and install the package/plugin the plugin does not show via copilot plugin list. I assume we should operate under the assumption that APM Packages are not Copilot Plugins and thus will not show up in the Copilot CLI - please confirm.

If any of this is in flux due to the rapid changing nature of the project please provide current state and future intentions.
Note: in regard to what I saw during pack and install, everything is targeting copilot.

Thanks,
jKlaus