docs(profile): normalize scope hierarchy to canonical (tenant/workspace/app/workflow/agent/toolset)

[amavashev]

What

Replaces the scope hierarchy list in profile/README.md with the canonical hierarchy used everywhere else in the protocol/spec/site.

Before:

- tenant
- environment
- application
- workflow
- agent
- tool
- run

After:

- tenant
- workspace
- app
- workflow
- agent
- toolset

Plus a one-sentence note: "Run-level budgets can be modeled through workflow or agent scope patterns where needed."

Why

The org README was using a different scope vocabulary (environment, application, tool, run) than the protocol, governance spec, docs, and dashboard, which all standardize on tenant -> workspace -> app -> workflow -> agent -> toolset. Inconsistent scope language weakens the mental model and dilutes the SEO/category signal.

Scope

• 1 file changed: profile/README.md
• 7 lines edited (the bullet list) + 1 sentence appended after it
• No structural changes; no other sections touched