Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@backend/plugins/AGENT.md`:
- Around line 70-75: The docs incorrectly state plugins should export a
startPlugin() function that returns { graphql, expressRouter, trpcAppRouter,
meta }; instead, update the wording to match actual wiring: plugins must call
startPlugin({ graphql, expressRouter, trpcAppRouter, meta }) from their
entrypoint (as used in main.ts) — mention the exact call signature
startPlugin({...}) and the required config fields graphql, expressRouter,
trpcAppRouter and meta so authors implement the correct entrypoint pattern.
- Line 30: Replace the invalid Apollo Federation snippet "(keyfield: \"_id\")"
with the proper `@key` directive syntax: instruct using `@key`(fields: "_id") on the
entity type (for example "type User `@key`(fields: \"_id\") { _id: ID! ... }") and
mention that for Federation 2+ the `@key` must be available via `@link`; update the
line that currently reads `When defining a schema, you must declare (keyfield:
"_id").` to reference the correct `@key`(fields: "_id") usage and the example
entity form.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@backend/plugins/AGENT.md`:
- Around line 810-835: The import rule forbids relative imports in the "Rules"
section but several examples in the same document use relative imports; fix by
making the document consistent: either relax the rule text ("Prefer absolute
imports; relative imports allowed in examples") or change all example import
statements to use absolute aliases (`~/`, `@/`) so they comply; update the
“Rules: - Always use absolute paths” line and the conflicting example import
blocks so the prohibition and examples (the example import lines earlier in the
doc) match exactly.
- Line 27: The fenced directory-tree block starting with "```" that contains
"plugin_name_api/" should include a language tag to satisfy markdownlint MD040
and improve rendering; update the opening fence from ``` to ```text (i.e.,
change the code fence that precedes the directory tree to ```text) so the block
becomes a text-fenced block and keep the closing fence as ``` unchanged.
- Around line 769-771: The migration example uses an empty string for
generateModels(''), which will fail in SaaS because generateModels requires a
valid non-empty subdomain; update the migrateTasks function to supply a real
subdomain (or accept one as a parameter) and document it: change migrateTasks to
call generateModels with a proper subdomain value (or add a function parameter
like subdomain and pass it through to generateModels) and ensure any calling
code or README explains the required subdomain format so the example works in
the SaaS flow.
- Around line 134-141: The example defines the onServerInit key twice which
causes the first definition to be overridden; merge the duplicate into a single
async onServerInit function that accepts the app parameter and performs both
initialization tasks (e.g. initialize external services/websockets using the app
arg and then call await initMQWorkers(redis)); update the example to show both
responsibilities in one onServerInit and keep the background worker comment so
plugin authors don’t accidentally drop initialization logic.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@backend/plugins/rules/RULES.md`:
- Line 11: Update the checklist item that currently reads "[ ] Index frequently
queried fields and all `_id` fields" by removing the "_id" portion so it reads
"[ ] Index frequently queried fields"; leave the rest of the checklist untouched
and ensure no other references to indexing `_id` remain in RULES.md to avoid
prompting redundant index creation.