docs(qa): flag ow-v103-reval scorecard row as superseded (ran on the dead Dal, #305)

[100yenadmin]

Docs-only data-integrity correction. The ow-v103-reval row in qa/SCORECARD.md records story 4.1 / mech 4.1 as a post-v1.0.3 canon-PC revalidation — but per #305, Dal Lightspark is canonically DEAD, so that run was on a dead, portrait-less PC. Its scores are SUSPECT as a clean canon-PC baseline.

Appends a ⚠ [SUPERSEDED — #305] note to that row's notes cell so no future agent cites 4.1/4.1 as the canon-PC baseline. Clarifies that the engine-plumbing validations still hold (the #162 kind="player"⇒in-party invariant, clock/travel/world-peopled are char-agnostic) and that the clean revalidation duo is OWED on a LIVING canon PC via the #329 living fixture.

No scores rewritten (the run happened; only its interpretation is corrected). No contract/engine/asset changes. Off origin/main via a worktree (shared checkout untouched).

Refs #305, #329, #162.

Summary by CodeRabbit

• Documentation
  • Updated quality assurance scorecard with a clarification indicating that validation scores for a specific test run may require revalidation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0c86e8d3-c77a-4b66-a388-e78d9d000f03

📥 Commits

Reviewing files that changed from the base of the PR and between 5406633 and 699cf88.

📒 Files selected for processing (1)

• qa/SCORECARD.md

---

📝 Walkthrough

Walkthrough

This PR updates the QA scorecard to document that the ow-v103-reval run's reported story/mech scores are superseded due to a canonical character death, while affirming that underlying engine-plumbing validations remain intact and a follow-up revalidation is required.

Changes

QA Scorecard Documentation Update

Layer / File(s)	Summary
Superseded run disclaimer qa/SCORECARD.md	The ow-v103-reval ledger entry is annotated with [SUPERSEDED — #305], indicating the story/mech scores cannot serve as a reliable canon-PC baseline due to canonical character death, while engine-plumbing invariants and checks remain valid.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• electricsheephq/WorldOS#147: Both PRs modify qa/SCORECARD.md to update QA ledger entries; PR #147 establishes the scorecard structure, while this PR adds a superseded-run disclaimer to an existing entry.
• electricsheephq/WorldOS#301: Both PRs update qa/SCORECARD.md to adjust v1.0.3-related release documentation and disclaimers; this PR's supersession note directly relates to that PR's SCORECARD v1.0.3 updates.

Poem

🐰 A scorecard row that's marked unfit,
When canon-fate has changed a bit,
Yet engine-plumbing stands so tall—
The validation conquers all! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete—it lacks the required Licensing/CLA checklist and Validation section entirely, which are mandatory per the repository template.	Add the complete Licensing/CLA checklist with appropriate checkmarks and a Validation section listing checks performed before merging.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: flagging a scorecard row as superseded due to being run on a dead character.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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