Summary

Documentation corrections and additions based on a thorough accuracy review of all repository-root Markdown files against the current source implementation.

Changes

SECURITY_MODEL.md — New section 5.1: Compact Permission-Check Call-Flow Diagram

Adds a five-part call-flow reference showing:

• All guard entry points (SerialObjectPermission, NativeInvocationPermission, NativeMemoryPermission, LoadClassPermission, thread-creation and module-mutation permissions) and how they funnel into checkPermission
• CombinerSecurityManager.checkPermission internal flow (self-bypass → checked cache → contextCache → parallel domain evaluation)
• AccessControlContext native stack walk
• ConcurrentPolicyFile.implies (volatile array read, privileged-grant fast-path, URI comparison, permission implication)
• System.setSecurityManager conditional validation flow (trusted 3-class whitelist vs custom 4-layer stack hardening)

CONTRIBUTING.md — Two omissions corrected

1. Guards directory listing (src/.../guards/): NativeMemoryPermission.java was missing from the project-structure tree. It exists in the implementation and is referenced throughout SECURITY_ANALYSIS.md and PROCESS_ISOLATION.md.
2. Key Files table: Added NativeMemoryPermission.java row (security level HIGH) alongside the existing guard entries.

README.md — Security Hardening Roadmap: two missing ✔ Done entries

NativeInvocationPermission and NativeMemoryPermission are implemented and wired into JNI/FFM paths, but were absent from the roadmap. Added:

• NativeInvocationPermission for ClassLoader.findNative / SymbolLookup / SystemLookup
• NativeMemoryPermission for Arena.global() and MemorySegment.reinterpret*()

STACK_VALIDATION_ANALYSIS.md — Annotate two outdated pseudocode blocks

The document is correctly marked RESOLVED (Issue #85) and the Resolution Summary table at the top records the correct 3-class whitelist. However, two pseudocode blocks lower in the document (isTrustedSecurityManagerClass helper and Phase 1 code fragment) still showed a single-class check for CombinerSecurityManager only — the pre-implementation analysis sketch. Added inline notes to both blocks making clear they are historical analysis pseudocode, and directing readers to the Resolution Summary and System.java for the authoritative 3-class implementation.

Policy Compliance: All contributions in this PR are human-written and comply with the OpenJDK Interim Policy on Generative AI adopted by DirtyChai.

These files fall under the Repository Documentation Exception defined in CONTRIBUTING.md (repository-root developer Markdown files not shipped as part of the DirtyChai/JDK build artefacts).