aeoess-aps: narrow the 0.9.0 revocation note per #178 (#195)

Author: aeoess

integrations/aeoess-aps/README.md

@@ -66,7 +66,7 @@ as no evidence rather than as not revoked. TRACE's own section 3.2.3 takes the A
 position at the bundle level (a verifier with no bundle reports that it performed no
 revocation check). The behaviour observed at agentrust-trace 0.9.0 is retained here as a tested
 implementation result; agentrust-io/trace-spec#246 records it as inconsistent with
-section 3.2.3. It cannot be re-observed on this exporter's record at 0.10.0, where
+section 3.2.3. It was not re-evaluated at 0.10.0, where
 `verify_record` refuses the record on schema grounds before any revocation check
 runs, so these rows are 0.9.0 results and are not restated for 0.10.0.
 

integrations/aeoess-aps/integration.yaml

@@ -38,7 +38,7 @@ tested_against:
   # These versions are the fixed run in .github/workflows/aeoess-aps-conformance.yml.
   # The floating run installs unpinned releases as drift detection (#169).
   # The revocation observations in README were made against 0.9.0 and stand as
-  # 0.9.0 results. They cannot be re-run on this exporter's record at 0.10.0:
+  # 0.9.0 results. They were not re-run on this exporter's record at 0.10.0:
   # verify_record refuses it on schema grounds before any revocation check runs
   # (observed with an empty store, a callable returning a non-bool, and a
   # callable returning True; all three raise the schema error first).