Staging->dev backport

[jeffmaki]

• Updated .claude/settings.json to allow a few additional Bash(...) commands, including vue-tsc, git add, and the @sentry/nuxt version check.
• Removed the README’s TODO note about eliminating any typing.
• Adjusted services/rapid.ts to add logging around Rapid loading, editor change handling, and uploader success events, while also changing the stable change flow to calculate a combined change count before notifying state updates.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates Rapid manager logging and event handling in services/rapid.ts (typed userDetails callback, stablechange changesLength calculation, added console logs), expands Claude settings' allowed Bash commands, and removes a TODOs note from README.

Changes

Rapid Service and Tooling Updates

Layer / File(s)	Summary
Rapid OSM/editor/uploader logging services/rapid.ts	userDetails callback expanded to typed multi-line form; stablechange handler now logs details and computes changesLength before calling #notifyStateChange; resultSuccess and #onLoaded gain added console logging; minor whitespace adjustments.
Dev tooling and docs cleanup .claude/settings.json, README.md	Allowlist expanded with vue-tsc and git add commands; README TODOs note removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

Logs now hop through Rapid's core,
Console whispers, "more, more, more!"
Settings widened, TODOs gone,
A tidy burrow, work well done.
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects that this is a staging-to-develop backport, though it doesn't describe the specific code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

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 `@services/rapid.ts`:
- Line 121: The `changesLength` calculation in `services/rapid.ts` is using
`||`, so it only returns the first non-zero bucket instead of the total pending
edits. Update the `changesLength` assignment in the `rapid` flow to sum
`changes.modified`, `changes.created`, and `changes.deleted` so
`normalizePendingEditCount` receives the full count. Keep the fix localized to
the `changesLength` variable used right before the pending edit normalization.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b6e6c1dc-ca49-4a0c-85ef-ffc6e962af97

📥 Commits

Reviewing files that changed from the base of the PR and between ee0fdd0 and f7d355e.

📒 Files selected for processing (3)

• .claude/settings.json
• README.md
• services/rapid.ts

💤 Files with no reviewable changes (1)

• README.md

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

changesLength uses || instead of +, underreporting pending edits.

When multiple change categories are non-empty (e.g., 2 modified + 3 created), || returns only the first non-zero count (2), not the total (5). The downstream consumer normalizePendingEditCount treats this as the pending edit count shown to users, so the count will be wrong whenever edits span more than one category.

🐛 Proposed fix

-      const changesLength = changes.modified.length || changes.created.length || changes.deleted.length;
+      const changesLength = changes.modified.length + changes.created.length + changes.deleted.length;

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	const changesLength = changes.modified.length || changes.created.length || changes.deleted.length;
	const changesLength = changes.modified.length + changes.created.length + changes.deleted.length;

🤖 Prompt for AI Agents

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

In `@services/rapid.ts` at line 121, The `changesLength` calculation in
`services/rapid.ts` is using `||`, so it only returns the first non-zero bucket
instead of the total pending edits. Update the `changesLength` assignment in the
`rapid` flow to sum `changes.modified`, `changes.created`, and `changes.deleted`
so `normalizePendingEditCount` receives the full count. Keep the fix localized
to the `changesLength` variable used right before the pending edit
normalization.