fix: track the Libraries/Simulation section renames in the docs site

[mbegin-robotiq]

Problem

The daily README job has been failing with:

Could not import the "SDKs/languages" software tools section: no
AUTO-GENERATED-SDK-TABLE markers found in robotiq.github.io's docs/intro.mdx.
It may have been restructured — refusing to publish a partial section.

robotiq.github.io#4 ("Doc-update") renamed two sections in docs/intro.mdx:

update-readme.mjs expected	Upstream now has
SDK — "SDKs/languages"	LIBRARIES — "Libraries"
PHYSICS_ENGINE — "Physics engine"	SIMULATION — "Simulation"
ROS2, ROS1, OTHER	unchanged

The generator's guard worked as designed — it refused to publish a partial section rather than silently dropping the missing tables from the org's public landing page. This was invisible until now because the workflow used to die earlier, at the missing-README_BOT_PAT checkout step (fixed in #4).

Fix

Updates SOFTWARE_SECTIONS to the new marker keys, and follows upstream for the displayed headings so the profile page stays consistent with the docs site it mirrors: "SDKs/languages" → "Libraries" and "Physics engine" → "Simulation".

profile/README.md needs no marker changes — it uses a single AUTO-GENERATED-SOFTWARE-TOOLS block, so the per-section markers only ever existed upstream.

The README content itself is deliberately not included here. Regenerating it is the daily job's work, and letting the automation produce that change doubles as an end-to-end test of the GitHub App path merged in #4.

Test plan

• node --test scripts/*.test.mjs passes (16/16), with the fixture and assertions updated to the new keys
• Ran node scripts/update-readme.mjs against live upstream — succeeds, and all five sections render (Libraries, ROS2, ROS1, Simulation, Other community projects)
• After merge, trigger update-readme.yml and confirm the full chain: App opens PR → test passes → github-actions[bot] approves → auto-merge lands the regenerated README

🤖 Generated with Claude Code