docs: preserve RPAP benchmark status sync

[LaloLalo1999]

What changed

• preserve the eight unpublished MemSWE harness commits through the verified chart package
• add commit 60206e7, which introduces a PAP evidence index and a broader, cautious benchmark-status/documentation sync

Critical relationship to PR #20

The first eight commits in this branch are the exact same SHAs already present in PR #20:

• df8295e
• 7b5b533
• e90b820
• d52a930
• 5ec1a32
• 63c9bab
• ce8ec24
• 7dca44e

After that shared tip, the branches diverge:

• this PR adds docs commit 60206e7
• PR feat(memswe): expand benchmark harness and provider conditions #20 adds implementation/test commit c4f3ee6

Do not merge both PRs blindly. Reviewers should sequence or reconcile them—preferably land/rebase PR #20 first, then transplant the unique documentation delta from 60206e7 and resolve the overlapping README/status files.

Why

The 60206e7 documentation is not patch-equivalent to any remote commit. It adds the unique docs/pap-sunday-2026-07-05/README.md evidence index and materially different cautious status text, so preserving it for review is preferable to silently dropping it.

Validation

Passed for the unique docs commit:

• git diff --check HEAD^..HEAD
• 52 local Markdown link targets
• HTML parser check for memswe-benchmark-status.html
• conflict-marker scan
• literal secret-pattern scan

Harness test:

• 19/20 tests passed.
• The task-discovery test fails because this branch hard-codes 12 task IDs while the current sibling MemSWE checkout exposes 40. PR feat(memswe): expand benchmark harness and provider conditions #20's c4f3ee6 replaces that brittle exact-list assertion, reinforcing the need to reconcile the branches before merge.

No model, provider, or external-memory calls were made.

This is a preservation/review draft, not an independently merge-ready alternative to PR #20.

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

[blocksorg]

Mention Blocks like a regular teammate with your question or request:

@blocks review this pull request
@blocks make the following changes ...
@blocks create an issue from what was mentioned in the following comment ...
@blocks explain the following code ...
@blocks are there any security or performance concerns?

Run @blocks /help for more information.

Workspace settings | Disable this message