[chaksaray]

Closes #9

What and why

ECO-5. Three claims in the org profile README were wrong or stale:

1. "The scanner never executes what it scans." The optional Docker sandbox stage runs skill content. It now reads: "The scanner never starts an MCP server and executes nothing by default. An optional Docker sandbox stage runs skill content in isolation." (the wording in the runbook)
2. Table row "Policy | capability-manifest/v1 | Live" now says "Schema published, enforced by the pre-release gate".
3. PiranhaDB is Offline, in the component table (piranha-api row) and in the "Threat intelligence" row, as the task note asks. The piranha-api README says the hosted API is offline, and ecosystem-status.yaml in PR feat: generate the ecosystem status diagram from a status file #8 sets PiranhaDB to offline.

Four lines changed in profile/README.md.

Item 3 of the issue is in PR #8, not here

The issue's third item, replacing the hand-drawn interoperability block with the generated status diagram, is done by PR #8 (ECO-1, issue #7), which has to exist first because it creates the generator. Merge #8 before or together with this PR. If this merges alone, issue #9 closes with item 3 still undone.

Verify (run this session)

python3 scripts/verify_claims.py --output <scratch>   -> 7 FAIL, 1 UNVERIFIED, 12 PASS
  C-11: 2 violations before, 1 now. profile/README.md:64 no longer flagged.
        Remaining: scanner:SECURITY.md:52 "Never execute scanned content." (scanner repository)
git diff added lines, em dashes                          -> 0

Table against ecosystem-status.yaml (from PR #8), row by row: AVE live, PiranhaDB offline, scanner live, gate pre-release, audit log pre-release, identity/reputation/delegation not built. All seven rows agree. The Policy row has no entry in the status file; it is the one sentence from the runbook.

Acceptance

• C-11 passes in claims/STATUS.md. Not met by this PR. The profile README is clean for C-11. One violation remains in scanner/SECURITY.md:52, in the scanner repository, so C-11 stays FAIL until that line is qualified there. Scanner README.md:7 was in the earlier list but is not flagged in this run.
• Table states match ecosystem-status.yaml

Other rows in this README that I think are stale (not changed)

These are outside the issue, so I left them. Each needs a decision or a separate task.

• gate row: "v1.0 feature-complete, pre-release. Install from source". pip install bawbel-gate works (claim C-10 PASS) and the version is 0.1.x.
• bawbel-mcp row: "Read-only, no private-data tools, no egress tools". Gate PR #78 argues this is not so; read it before the row is kept.
• integrations and bawbel-mcp rows say "Live". The verifier has no claim for either.

Not verified

• That the README renders as intended on the organization page.
• No CI workflow runs on this PR (the status-diagram workflow is in feat: generate the ecosystem status diagram from a status file #8).