fix: bound catalog acquisition before pilot staging

docs/architecture/package-activation.md

@@ -40,3 +40,10 @@ filesystem catalog adapter returns a descriptor for acquisition only; local
 immutable staging remains the only active package root. These adapters and the
 controlled local catalog scenarios are verified by tests; a corporate DFS pilot
 and Autodesk launch with a real roster are not runtime verified.
+
+Catalog acquisition is bounded before staging: the configured catalog root and
+package root must not be reparse points, the descriptor must remain below the
+configured root, manifests may contain at most 256 files and 512 MiB declared
+payload, and absolute or traversal payload paths are rejected. A corporate pilot
+requires explicit configured roster and catalog roles; absent roles block before
+any corporate payload is read.

docs/evidence/corporate-catalog-pilot-status.json

@@ -0,0 +1,13 @@
+{
+  "schemaVersion": 1,
+  "pilotTooling": "VERIFIED_BY_TESTS",
+  "realCorporateRosterParsing": "BLOCKED",
+  "realCorporatePackageAcquisition": "BLOCKED",
+  "blockReason": "CORPORATE_CATALOG_AND_ROSTER_PATHS_NOT_CONFIGURED",
+  "localImmutableStaging": "VERIFIED_BY_TESTS",
+  "controlledOutageRecovery": "VERIFIED_BY_TESTS",
+  "productionActivation": "NOT_RUN",
+  "autodeskRuntime": "NOT_RUN",
+  "productionReadiness": "NOT_ACHIEVED",
+  "redaction": "No corporate paths, roster contents, package payload, session identity, or machine data were recorded."
+}