docs: propose resource v1 direct-resolution format

[shadstoneofficial]

Summary

This drafts a resource version 1 direct-resolution proposal as a successor discussion to the narrow HIP018 / Rerecord A and AAAA prototype in #955.

The proposal follows the path suggested in the #955 discussion: avoid stretching version 0 ordering behavior further, and instead define a clean direct-resolution format with labels, TTL handling, and a vetted initial record set.

Scope

This is intentionally a docs/spec PR, not an implementation PR.

It sketches:

• keeping version 0 behavior unchanged;
• using version 1 for direct-resolution records;
• separating delegation records from direct-resolution records;
• adding owner labels for names like _443._tcp.example.;
• defining TTL handling as an explicit design choice;
• considering A, AAAA, TLSA, HTTPS, SVCB, and MX as possible v1 records;
• compatibility and rollout steps.

Relationship to #955

#955 remains useful as a prototype and test reference for direct A/AAAA resolution. If maintainers prefer the v1 path, this proposal can supersede that narrow v0-compatible implementation path before any larger code changes are made.

Non-goals

This does not propose supply, locked-fund, foundation, tokenomics, tree interval, or arbitrary zone-file changes.