Extend AgentKeys with direct regular authority and scoped proposal operations

[web3blind]

Optional functionality

Feature-only follow-up to the correctness fixes already in master. No dependency on the closed combined implementation.

• Permit explicitly granted direct regular authority and scope grants by operation/principal, preserving the prohibition on mixed regular and active/master transactions.
• Permit proposal_create and proposal_delete with unchanged evaluator restrictions. No persistent proposal approvals; proposal_update, account_update and redelegation remain forbidden.
• Recheck agent-dependent proofs before application; preserve ordinary entry-time proofs and recursive authority isolation.
• Align RPC discovery including partial independent agent contributions. Missing signatures still prevent transaction acceptance.
• Preserve unique agent keys, wire format and storage layout. EN/RU docs describe policy changes.

Verification and review

Final head 2997256, based on f2857b3:

• Sequential upstream/DREAM incremental builds -j1 succeeded.
• Fresh protocol: 12 cases / 57 assertions; focused chain: 33 cases / 185 assertions.
• Final RPC partial-contribution regression: 15 cases; existing discovery: 13 probes. Parent review finding reproduced RED then GREEN with actual RPC; incomplete transactions remain rejected.
• Prior feature matrix: 54 unique transactions (29 irreversible positives, 25 rejected negatives); snapshot/restart evidence retained. Final narrow authority regression also included 2 irreversible positives and 1 rejected transaction before the RPC-only correction.
• Full simulator 140 cases / 1845 assertions is earlier feature-stage evidence, NOT a new full-suite run on final head. The full live matrix was not rerun for the final RPC-only correction.
• All 13 feature files match tested DREAM sources byte-for-byte. Parent independently reviewed implementation and final correction; live execution performed by worker.
• Latest master 0e655d4 changes release version/schema temp reuse/snapshot warning/docs outside this feature delta; read-only merge-tree found no conflicts. No claim of a fresh merged-head build.

Activation

This is an OPTIONAL consensus policy change, not required to deploy the accepted correctness fixes. Maintainer must coordinate activation/release timing before merging or deploying; HF15 date is not changed here. No production deployment or mainnet verification.