docs: replace stale hard-coded test counts

[karagozemin]

Summary

Remove stale hard-coded test counts from contributor-facing documentation and point readers to reproducible commands instead.

Why this matters

README.md and docs/SCF_PLAN.md still claim counts such as 14 contract tests, 13 tlock tests, and 7 SDK tests. The suites have grown substantially, so these numbers now understate the project and become incorrect whenever tests are added.

Scope

• Update stale test-count claims in README.md and docs/SCF_PLAN.md.
• Prefer stable wording plus the command that produces the current result.
• Keep historically frozen evidence clearly labeled if an exact old count must remain.
• Do not manually replace old numbers with new numbers that will become stale again.

Acceptance criteria

• Current capability/status sections no longer advertise stale exact counts.
• Contract, SDK, tlock, keeper, and web verification commands are easy to find.
• Historical claims, if retained, are explicitly dated or marked as snapshots.
• pnpm docs:check-links passes.

[CleanDev-Fix]

I can take this as a focused documentation-stability pass. I’ll replace the stale contract, tlock, and SDK counts with the repository’s reproducible suite commands, and make the contract, SDK, tlock, keeper, and web verification commands easy to find in both current-status sections. I won’t change test code or replace old counts with new counts; verification will be the repository link checker plus command-to-package.json and diff checks. Does that boundary match your intent for #177?

[fadeelah2007]

Hello Maintainer, I'd love to work on this issue. I can update README.md and docs/SCF_PLAN.md to remove the hardcoded test counts and replace them with clear, reproducible test commands as outlined in the description.

[onyemaechiezekiel9]

@onyemaechiezekiel9 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I have gone through the issue and I would love to work on this swiftly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @onyemaechiezekiel9 to this issue.

[raymondidahor-bot]

@raymondidahor-bot has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would love to work on this project. I can deliver within a short time. Please consider me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @raymondidahor-bot to this issue.

[CHASE3020]

@CHASE3020 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i would love to work on this issue sir

ℹ️ Repo Maintainers: To accept this application, review their application or assign @CHASE3020 to this issue.

[ogundeleoluwaferanmi35]

@ogundeleoluwaferanmi35 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign this issue to me, I can get it done in 30 mins

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ogundeleoluwaferanmi35 to this issue.

[Olasunkanmi975]

@Olasunkanmi975 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Olasunkanmi975 to this issue.

[baedboibidex-cmyk]

@baedboibidex-cmyk has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

PLS ASSIGN

ℹ️ Repo Maintainers: To accept this application, review their application or assign @baedboibidex-cmyk to this issue.