chore: update all module READMEs to use main agent id #567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR standardizes all module documentation examples to use
coder_agent.maininstead ofcoder_agent.example, aligning with the most common template convention.Problem
Currently, there's an inconsistency between template definitions and module documentation:
"main"as the agent name"example"as a placeholder, which doesn't exist in any templates, except some modules who already use "main"This creates friction when users copy examples from module docs into their templates that use
mainas the agent name.Solution
Update all module documentation to use
coder_agent.mainsince:Changes
Module Documentation (52 files)
coder_agent.example→coder_agent.mainREADME.mdCONTRIBUTING.mdexamples/templates/main.tfWhat's NOT in this PR
❌ Template changes - Templates are left as-is to avoid breaking existing workspaces
❌ Linting rules - Will be addressed separately if desired
Impact
✅ Zero breaking changes: Only documentation is updated
✅ Better DX: Copy-paste examples work with 78% of existing templates
✅ Consistency: Documentation now matches the de facto standard
Testing
git diffRelated
This addresses the documentation inconsistency identified in the registry audit. Template standardization can be addressed in a future PR if desired.
PR by @phorcys420
Non-blink follow-up to #566