fix(protocol): use Classic command permissions for access

[zoeyrose]

Summary

Align Classic access-code administration with its existing per-player/character command permissions. /access uses /cmd_permission, and [OP] grants it automatically like other operator commands.

Implementation / behavior

• Check the active character's effective command permission on each operation.
• Remove the separate root-managed account allowlist and access-specific authority requirement.
• Preserve existing account passwords, stored character permissions and the checked serialized token store.
• Retain root-only Unix-socket administration for a locked private server's initial code, and keep access policy/store-path configuration startup-only.

Only spec/access-tokens.md changes. Wire identities, schemas, generated bindings, crate sources, fixtures and publication policy are unchanged. The separate registry-publication proposal in #46 is untouched.

Validation

At 868a5cddaaaec9be264c414783182c51393b08e9, independent review approved the complete specification change. Full tools/validate.sh passed in pinned Linux build image sha256:7904a1802054662b0ede5b55de72e4c92b0112a3c211125f994ed6c62e9ec9d8; regeneration left the tree clean and full-base whitespace checks passed. Required GitHub checks Protocol validation and Conventional PR title passed on this exact head and accepted base.

Limitations / follow-up

Classic owns the command dispatcher and per-character permission implementation, which are being updated separately. This source change performs no deployment, crate preparation, registry operation or merge.

[github-actions]

🎉 This PR is included in version 2.9.0 🎉

The release is available on:

• v2.9.0
• GitHub release

Your semantic-release bot 📦🚀