docs: fix Muse table of contents indentation

[arittr]

Who is submitting this PR? (required)

Field	Value
Your model + version	GPT-6 (exact version/ID is not exposed to this session); review by gpt-5.6-sol with low reasoning
Harness + version	Codex CLI 0.153.4
All plugins installed	superpowers@superpowers-dev 6.3.0; stream-deck-agents-codex@drew-local 1.0.0+codex.20260909062849; openai-templates@openai-curated-remote 0.1.1; plugin-management@openai-curated-remote 0.1.0
Human partner who reviewed this diff	The requesting human partner in this session: reported the indentation problem, received the complete one-line diff, then explicitly requested the fix and a PR into dev (quoted below).

What problem are you trying to solve?

The human partner noticed that Muse appeared at the wrong level in the README on dev. Its table-of-contents entry has no leading spaces, so GitHub renders it as a top-level item alongside Getting Started, while the other harnesses are children of Getting Started. The existing ### Muse section heading already has the correct level.

What does this PR change?

Adds two leading spaces to the Muse table-of-contents entry so it nests alongside the other harnesses under Getting Started.

Is this change appropriate for the core library?

Yes. This corrects the hierarchy of an existing entry in the core README. It adds no harness integration, dependencies, or project-specific configuration.

What alternatives did you consider?

Changing the Muse section heading would incorrectly promote one harness above its peers. Leaving the entry unchanged preserves the navigation mismatch. Matching the existing two-space indentation is the smallest correction.

Does this PR contain multiple unrelated changes?

No. The complete change is two leading spaces on one README line.

Existing PRs

• I have reviewed all open AND closed PRs for duplicates or prior art
• Searched all PR states for Muse, README indent, and table of contents; no duplicate fix found.
• Related PRs: feat: add native Muse support (multiprovider) #2317 introduced the Muse entry without indentation; docs: add README table of contents and move Community section higher #2090 added the README table of contents; docs: streamline README getting-started navigation #2109 updated its navigation. This PR corrects the entry introduced by feat: add native Muse support (multiprovider) #2317.
• The open release PR Release v6.4.1: diagnosing-superpowers, Native plan execution, OpenCode 2.0 and Muse support #2338 still carries the unindented entry. The closed release PR Release v6.4.0: diagnosing-superpowers and movie skills, Native execution, OpenCode 2.0, Muse, and Qwen Code support #2331 was a release aggregation, not an attempted indentation fix. This PR targets the source README on dev with only the indentation correction.
• Also inspected the README changes in docs: add MiniMax Code marketplace installation #2272 (MiniMax installation documentation); they do not address Muse indentation.

Environment tested

Harness (e.g. Claude Code, Cursor)	Harness version	Model	Model version/ID
Codex CLI on macOS; verification through GitHub's GFM rendering API	0.153.4	GPT-6	Exact version/ID not exposed to this session

Rendered the before and after table of contents through GitHub's Markdown API and inspected the HTML list hierarchy:

Entry	Before list depth	After list depth
Getting Started	1	1
Hermes Agent	2	2
Muse	1	2
The Basic Workflow	1	1

git diff --check passed. The diff contains one changed line in README.md. A separate read-only review found no issues and confirmed the #muse target matches the existing section heading.

New harness support (required if this PR adds a new harness)

Not applicable: Muse support already exists. This PR changes only the README table-of-contents indentation, so no new-harness acceptance transcript was run.

Evaluation

• Initial human prompt: “i think we have a README issue on dev, is Muse harness at the right indent level”
• Skill-behavior eval sessions after the change: 0. No skill content or runtime behavior changed.
• Before/after outcome: GitHub's rendered HTML places Muse at list depth 1 before the fix and depth 2 afterward, matching Hermes. Getting Started and The Basic Workflow remain at depth 1.

Rigor

• If this is a skills change: I used superpowers:writing-skills and completed adversarial pressure testing — not applicable; no skills changed.
• This change was tested adversarially, not just on the happy path — no adversarial agent sessions were run for this whitespace-only documentation correction. Verification used GitHub's actual Markdown renderer on both versions, including the neighboring list entries.
• I did not modify carefully-tuned content (Red Flags table, rationalizations, “human partner” language) without extensive evals showing the change is an improvement.

Human review

• A human has reviewed the COMPLETE proposed diff before submission.

The human partner was shown the complete proposed change:

-- [Muse](#muse)
+  - [Muse](#muse)

They then explicitly approved implementation and submission: “fix it and open a PR into dev pls”. The submitted diff is exactly that change.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-18T22:39:58.076631Z	a38575f	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.