Verify CAP-004's docs against the implementation; provenance: verified

Human review (Flemming N. Larsen) re-read CAP-004/README.md,
criteria.md, design.md, and C-005 against the shipped RobotData/
RobocodeFileOutputStream code. Found and fixed one carried-over
inaccuracy from before the FIO-001 wording narrowed: README.md and
RobotData's own Javadoc still said "absolute path" is re-rooted --
only a root-relative name is; a true drive-letter-absolute name fails
the write on both engines instead, as design.md and C-005 already
correctly stated. Corrected both, then promoted all four documents'
provenance from inferred to verified, clearing clue validate's
ADR-035 activation gate (now OK: CAP-004 covered/partial as declared,
no remaining high-cost inferred blockers).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011GShGLuFwRpnWNY2WL5Vz5

Author: flemming-n-larsen

docs/capabilities/CAP-004-robot-file-io-sandboxing/README.md

@@ -5,21 +5,21 @@ status: active
 links: [G-001, C-005, IDR-007]
 goal: G-001
 title: Robot file I/O sandboxing
-provenance: inferred
+provenance: verified
 reversal-cost: high
 ---
 
 # CAP-004 — Robot file I/O sandboxing
 
-Classic Robocode confines everything a robot writes, through its own data-file API, to that robot's own data directory. A robot that opens an absolute path gets a file inside its data directory instead, and never learns the difference. This capability is that redirection, implemented at the one point the bridge controls: `RobotData.getDataFile`/`getDataDirectory`.
+Classic Robocode confines everything a robot writes, through its own data-file API, to that robot's own data directory. A robot that opens a root-relative path gets a file inside its data directory instead, and never learns the difference. This capability is that redirection, implemented at the one point the bridge controls: `RobotData.getDataFile`/`getDataDirectory`.
 
 ## Why it exists as its own capability
 
 Robots depend on the redirection, and the dependency is invisible in their source. A robot that saves its learned targeting data to a root path is not misbehaving — it is a robot whose author relied on the engine to place the file, correctly, because under classic the engine always did. One such bot in the collection produced access-denied errors in the thousands over a single battle before this capability existed, and its behaviour under the bridge was not a degraded version of its classic behaviour but a different robot: one whose learning never persisted.
 
 ## What it covers
 
-Path confinement inside `getDataFile`/`getDataDirectory` — asterisks stripped and a `java.io.File` merge used so an absolute or root-relative name is re-rooted inside the directory rather than overriding it, `..` rejected exactly as classic rejects it — plus the 200000-byte quota classic enforces on a robot's data directory.
+Path confinement inside `getDataFile`/`getDataDirectory` — asterisks stripped, `..` rejected in the stripped name (stricter than classic's own check order, for safety — see `design.md`), and a `java.io.File` merge used so a root-relative name is re-rooted inside the directory rather than overriding it (a true drive-letter-absolute name fails the write on both engines instead) — plus the 200000-byte quota classic enforces on a robot's data directory.
 
 ## What it does not cover
 

docs/capabilities/CAP-004-robot-file-io-sandboxing/criteria.md

@@ -5,7 +5,7 @@ status: active
 links: [CAP-004]
 title: Robot file I/O sandboxing — acceptance criteria
 ac-prefix: FIO
-provenance: inferred
+provenance: verified
 reversal-cost: high
 ---
 

docs/capabilities/CAP-004-robot-file-io-sandboxing/design.md

@@ -4,7 +4,7 @@ type: design
 status: active
 links: [CAP-004, IDR-002, IDR-007, ARCH-002, C-005]
 title: Robot file I/O sandboxing — design
-provenance: inferred
+provenance: verified
 reversal-cost: high
 ---
 

docs/constraints/C-005-robot-file-io-confined-to-data-directory.md

@@ -6,7 +6,7 @@ links: [CAP-004]
 title: A robot reads and writes only inside its own data directory
 source: Classic Robocode's robot sandbox, which every rumble robot was written against
 enforcement: partial
-provenance: inferred
+provenance: verified
 reversal-cost: high
 ---
 

robocode-api/src/main/java/dev/robocode/tankroyale/bridge/RobotData.java

@@ -45,10 +45,12 @@ public static File getDataDirectory() {
     /**
      * Resolves a robot-supplied filename against the data directory, matching classic's
      * {@code RobotFileSystemManager.getDataFile}: asterisks are stripped, and a {@code java.io.File}
-     * merge is used rather than {@code java.nio.file.Path#resolve} so an absolute or root-relative
-     * name is re-rooted inside the directory instead of overriding it outright.
+     * merge is used rather than {@code java.nio.file.Path#resolve} so a root-relative name is
+     * re-rooted inside the directory instead of overriding it outright. A true drive-letter-absolute
+     * name (e.g. {@code C:\...} on Windows) is not re-rooted by this merge, matching classic; the
+     * write then fails rather than escaping the directory.
      *
-     * @throws AccessControlException if filename contains "..", matching classic's
+     * @throws AccessControlException if the name contains "..", matching classic's
      *                                 {@code AdvancedRobotProxy.getDataFile}.
      */
     public static File getDataFile(String filename) {