tests: record AFP trustee access privileges smoke success

tests/linux/README.md

@@ -459,6 +459,46 @@ The server replies with the read-only AFP file information record currently
 implemented by mars_nwe: Entry ID, Parent ID, attributes, data/resource fork
 lengths, offspring count, fixed long/short names, and access rights.
 
+
+### AFP Get/Scan AccessPrivileges smoke
+
+AFP Get File Information and AFP Scan File Information now derive the
+`AccessPrivileges` word from mars_nwe trustee/effective-rights state instead
+of returning the old static compatibility masks.  The WebSDK AccessPrivileges
+bits exposed by the smoke helpers are:
+
+```text
+0x0100 Read
+0x0200 Write
+0x0400 Open
+0x0800 Create
+0x1000 Delete
+0x2000 Parental
+0x4000 Search
+0x8000 Modify File Status Flags
+```
+
+The AFP smoke suite exercises this with the same readonly trustee setup used by
+the metadata negative tests.  With `--readonly-user NOPASSUSER`,
+`--readonly-no-password`, and `--prepare-readonly-rights`, the suite grants
+`[RF]` on `SYS:PUBLIC/pmdflts.ini` and verifies that Get File Information
+reports readable/openable rights while write and modify-status rights are not
+set:
+
+```sh
+./afp_file_info_smoke \
+  --expect-rights-set 0x0100 \
+  --expect-rights-clear 0x9200 \
+  -S MARS -U NOPASSUSER -n \
+  SYS:PUBLIC/pmdflts.ini
+```
+
+Runtime status: the trustee-derived AccessPrivileges smoke run is verified
+with `failures=0`.  The report showed the Supervisor Get/Scan replies returning
+`rights=0x9f00`, while the readonly `NOPASSUSER` probe returned `rights=0x0500`
+under the temporary `[RF]` trustee assignment and satisfied the set/clear mask
+checks.
+
 Useful smoke cases for a standard MARS-NWE `SYS` volume are:
 
 ```sh