[codex] prepare protocol release 1.1

[chgaowei]

What changed

• Removed draft-stage wording from Chinese and English protocol documents.
• Standardized protocol metadata blocks with released status and version 1.1.
• Removed version suffixes from document titles and moved version information into metadata blocks.
• Updated related links, SVG captions, and community-operation titles that referenced Draft/草案.

Why

This prepares the ANP protocol documents for publishing version 1.1 without draft wording in titles or release metadata.

Review notes

No protocol fields, algorithms, message flows, interface semantics, or security requirements were intentionally changed. The edits are limited to release metadata, draft/version wording, and non-normative wording needed to remove Draft/草案 references. The remaining draft strings are JSON Schema standard URIs.

Validation

• Ran git diff --check.
• Searched changed files for residual Draft/草案/草稿 wording; only JSON Schema URI occurrences remain.

[gsimcard]

1. Marking status as "released" and version 1.1 ensures consistency and clarity.
2. No protocol fields, flows, or security requirements were changed — this guarantees backwards compatibility.
3. Keeping draft in JSON Schema URIs (e.g., draft-07) is appropriate because they reference external standards, not this document's status.

Recommendation: Approve and merge. This is a clean, editorial update ready for publishing version 1.1.

[whyseu]

Draft Version 1.1 is a milestone for the community. Thank you all for your contributions.

[okwinds]

One thing worth clarifying: this PR updates the document metadata to Version: 1.1, but the examples still use "protocolVersion": 1.0.0. Since the PR says it does not change protocol fields or semantics, that means “protocolVersion “ is intentionally unchanged in this PR. It would help to add a short note near the release metadata or in the PR description saying that “Version: 1.1” is the spec/document release version, while protocolVersion is not changed by this PR.

I’m glad to see this release coming together. This feels like a milestone version for the project, and I recommend approving and merging it.