docs: update README devnet support for pq-devnet-5

[MegaRedHand]

Motivation

The devnet5 branch now runs the pq-devnet-5 spec, but the README still lists pq-devnet-4 as the current devnet.

Description

• Move pq-devnet-5 to current, with the devnet5 Docker tag listed as available.
• Move pq-devnet-4 to the older devnets list (devnet4 tag remains available).
• Add a pq-devnet-6 section noting it is in a planning phase with no features specified yet.
• Drop the completed "Add support for pq-devnet-5" item from incoming features.

[github-actions]

🤖 Kimi Code Review

This PR contains only documentation updates to README.md. No consensus-critical code, cryptographic logic, or state transition functions are modified.

Documentation Review:

1. Consistency check (Line 122): The text states "A Docker tag devnet5 will be published for this version." If pq-devnet-5 support is now complete (as implied by removing it from the roadmap on Line 139), consider updating this to "is available" rather than "will be published" to match the tense used for devnet4 in Line 131.

2. Dead link verification: Confirm that Issue 285 (removed from roadmap Line 139) is actually closed/resolved, since the text now implies pq-devnet-5 support is complete.

3. Nit (Line 125): The pq-devnet-6 section header might benefit from a brief note about expected changes (e.g., "Planning phase for XMSS parameter updates" or similar), though this is optional if specifications are genuinely undetermined.

Verdict: Changes are logically consistent. The progression from "in development" → "current" → "planning" for devnets 4/5/6 is clear. No blockers, though consider Point 1 regarding tense consistency if the Docker image is already built.

No security or consensus risks identified—proceed with merge after confirming the Docker tag availability status.

---

Automated review by Kimi (Moonshot AI) · kimi-k2.5 · custom prompt

[github-actions]

🤖 Codex Code Review

1. README.md, RELEASE.md: this PR advances the advertised current devnet to pq-devnet-5, but the linked release guide still says latest is for devnet3 and its pull example is still devnet3 at RELEASE.md. That leaves conflicting operator-facing instructions around which image/tag is current. I’d update RELEASE.md in the same PR, or soften the README wording until the release docs are brought in sync.

No code paths changed here, so I don’t see consensus, security, performance, Rust, or memory-safety findings in the diff itself. I did not run tests; this is a docs-only change.

---

Automated review by OpenAI Codex · gpt-5.4 · custom prompt

[greptile-apps]

Greptile Summary

This PR updates the README to reflect that the devnet5 branch now runs the pq-devnet-5 spec instead of pq-devnet-4.

• Promotes pq-devnet-5 to the current devnet section (keeping "will be published" for the devnet5 Docker tag), adds a pq-devnet-6 planning note, and moves devnet4 into the older devnets list.
• Removes the now-completed "Add support for pq-devnet-5" item from the incoming features list.

Confidence Score: 5/5

Documentation-only change; no code paths affected.

The change touches only README.md, updating devnet version labels and a features list to match the current state of the branch. All edits accurately reflect what the PR description states and the wording is consistent.

No files require special attention.

Important Files Changed

Filename	Overview
README.md	Documentation update: promotes pq-devnet-5 to current, adds pq-devnet-6 planning note, moves devnet4 to older list, and removes completed incoming feature item.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[pq-devnet-1/2/3] -->|discontinued| B[Older Devnets\ndevnet1, devnet2, devnet3, devnet4]
    C[pq-devnet-4] -->|discontinued| B
    D[pq-devnet-5\n⬅ current\ndevnet5 tag pending] --> E[pq-devnet-6\nplanning phase]

Loading

_{Reviews (1): Last reviewed commit: "docs: update README devnet support for p..." | Re-trigger Greptile}