Drop atime from the format spec and pin the file entry fields (closes #158)

atime left mf.proto earlier and nothing reads or writes it, but docs/FORMAT.md still narrated its removal and listed it among the determinism rules. The spec now describes the file entry by its fields only. A new test compares the MFFilePath message descriptor, by name and number, with a list copied from the spec's field table. It does not read the spec, so changing a field means changing the proto, the spec and that list together. Model: opus-5-5
2026-10-06 03:26:16 +02:00
parent 99b3e0e202
commit 343431dd30
2 changed files with 25 additions and 4 deletions
@@ -78,9 +78,6 @@ Each file entry contains:
 | `mtime`    | 302    | Timestamp (optional)      | Modification time                   |
 | `ctime`    | 303    | Timestamp (optional)      | Change time (inode metadata change) |

-Field 304 (`atime`) has been removed from the specification. Access time is
-volatile and non-deterministic; it is not useful for integrity verification.
-
 ## Path Rules

 All `path` values must satisfy these invariants:
@@ -130,7 +127,6 @@ By default, manifests are generated deterministically:

 - File entries are sorted by `path` in **lexicographic byte order**
 - `createdAt` is omitted unless explicitly requested
- `atime` is never included (field removed from schema)

 This ensures that two independent runs over the same directory tree produce
 byte-identical `.mf` files (assuming file contents and metadata have not