chore: update plugin

[daveomri]

Summary

• Import the Apify for Qoder plugin codebase (mirrored from personal repo).
• Reset CHANGELOG.md to a clean slate, removing version history and links pointing to the personal repo.

What's included

• Qoder plugin manifest (.qoder-plugin/marketplace.json, apify/.qoder-plugin/plugin.json)
• Apify MCP server configuration
• Bundled skills: apify-ultimate-scraper, apify-actor-development, apify-actorization, apify-generate-output-schema, apify-sdk-integration
• Apify subagent with routing logic
• Role instruction doc, CI release workflow, contributing guide
• Apache-2.0 license

Note

The plugin code was already pushed to main via repo mirror. This PR resets the changelog so version history starts fresh from this organization's repo.

[Jakub-Vacek]

Review of the main content:

1. Are you linking icons somewhere? or it is Qoder convention to always have icon.png/svg so it can be loaded?
2. This might not work: https://github.com/apify/apify-qoder-plugin/blob/main/.github/workflows/release.yml#L48
3. We generally do not have Contributing guide in plugin repos - external users are not able to contribute to internal repos which holds the actual content.
4. I would drop the /skills and /agents a let these propagate from internal repo - so we know this flow works
   5: I don't understand this file: https://github.com/apify/apify-qoder-plugin/blob/main/apify/CONNECTORS.md (especially the last part) - why do we need MD file describing MCP?

[daveomri]

Review of the main content:

1. Are you linking icons somewhere? or it is Qoder convention to always have icon.png/svg so it can be loaded?

2. This might not work: https://github.com/apify/apify-qoder-plugin/blob/main/.github/workflows/release.yml#L48

3. We generally do not have Contributing guide in plugin repos - external users are not able to contribute to internal repos which holds the actual content.

4. I would drop the /skills and /agents a let these propagate from internal repo - so we know this flow works
   5: I don't understand this file: https://github.com/apify/apify-qoder-plugin/blob/main/apify/CONNECTORS.md (especially the last part) - why do we need MD file describing MCP?

@Jakub-Vacek

I followed the Qoder docs [LINK], where they suggest this structure of the plugin:

• it's optional, so we can drop it

oki, will do in the following commit

I add it there for context of devs, that will be responsible for publishing this plugin, as it requires manual move of the zip to Qoder platform, but we can drop it as well

will update, thanks

Nope, Qoder doesn't have any such convention. I added it to assets/ in the repo root so it's on hand when submitting the new/first version of the plugin to Qoder, which requires a raster icon to be uploaded manually (png/jpg/webp, 1:1, ≤500 KB; svg isn't accepted). The svg is just the brand source.