Update release-readiness audit: set current rating to 8.3/10 and add local validation details

[GsCommand]

Motivation

• Correct the release-readiness assessment after PR fix(agent-sdk): align receipt proof shape to metadata.proof #51 to reflect verified local validation and to shift focus from runtime protocol work to packaging/versioning before publish.
• Record authoritative local validation evidence so the audit distinguishes environment-specific registry issues from actual product readiness.

Description

• Update AUDIT-agent-sdk-runtime-core-alignment.md to set Branch to codex/create-audit-for-agent-sdk-release-readiness and change the current rating to 8.3/10 while keeping the target at 9/10.
• Add a clear commands/validation split that notes the Codex/container registry/network constraints and records verified local Windows validation with npm install, npm run build, and npm test passing.
• Keep only the real remaining release blockers: package version still 1.1.0, missing exports map in package.json, re-run npm pack after build, confirm schemas are present in dist/src and the npm tarball, and decide 1.2.0 vs 2.0.0 for the release.
• Update release guidance to: not ready to publish yet but close, and recommend 1.2.0 unless the metadata.proof migration is treated as a public breaking change (use 2.0.0), and explicitly note canonical proof shape alignment as receipt.metadata.proof.*.

Testing

• Verified local validation by running npm install, npm run build, and npm test, all of which passed on the authoritative Windows validation environment.
• Local test results recorded: 17 passed, 0 failed for the repository test suite.
• Notes that registry/network constraints in the Codex/container environment may prevent reproducible npm install there, and those environment-specific issues are not treated as product/runtime failures.

---

Codex Task

[GsCommand]

Agreed on 1.2.0 for the upcoming agent-sdk release, assuming there are no known external consumers depending on the prior top-level proof shape.

This audit now reflects the authoritative local validation state:

• npm install passed
• npm run build passed
• npm test passed
• 17 tests passed, 0 failed

Remaining release work should stay limited to packaging/version/export cleanup, including:

• bump package version to 1.2.0
• add/confirm exports map
• run npm pack --dry-run after build
• confirm schema JSON assets are included in the tarball

No further protocol/signature architecture changes are needed before the packaging PR unless the pack audit exposes a concrete issue.