chore(modules/claude-code): update readme

[hugodutka]

The README points to an old version of claude code that doesn't support the --continue flag, making it incompatible with the latest version of the module. It's easy to copy and paste the example and run into an error. This PR updates the example version and adds troubleshooting notes.

[matifali]

@bcpeinhardt do we still support updating the README without pushing a new version tag?

[matifali]

@hugodutka, can you bump the patch version to ensure we include the latest changes? The registry only deploys from this repo on new tag pushes. Thanks

[github-actions]

❌ Version Bump Validation Failed

Bump Type: patch

Module versions need to be updated but haven't been bumped yet.

Required Actions:

1. Run the version bump script locally: ./.github/scripts/version-bump.sh patch
2. Commit the changes: git add . && git commit -m "chore: bump module versions (patch)"
3. Push the changes: git push

Script Output:

🔍 Detecting modified modules...
Found modules:
registry/coder/modules/claude-code

📦 Processing: coder/claude-code
Found git tag: release/coder/claude-code/v2.0.0 (v2.0.0)
Current version: 2.0.0
New version: 2.0.1
Updating version references for coder/claude-code in registry/coder/modules/claude-code/README.md

🔧 Running formatter to ensure consistent formatting...

📋 Summary:
Bump Type: patch

Modules Updated:

- coder/claude-code: v2.0.0 → v2.0.1

READMEs Updated:

- coder/claude-code

✅ Version bump completed successfully!
📝 README files have been updated with new versions.

Next steps:
1. Review the changes: git diff
2. Commit the changes: git add . && git commit -m 'chore: bump module versions (patch)'
3. Push the changes: git push

Please update the module versions and push the changes to continue.

[matifali]

LGTM.

[bcpeinhardt]

@bcpeinhardt do we still support updating the README without pushing a new version tag?

No we build the front end content entirely from the latest release now, that was the trade off we made to avoid the front end content being more up to date than the back end.

There's one exception: Module's that don't have a release in coder/registry (meaning they were last released when we were still using coder/modules) get their content built from the main branch of coder/registry, as it was copied over when we archived coder/modules so the source is exactly the same.