docs: align P2-P6 planning artifacts with the P1.1 registry contract

docs/superpowers/specs/2026-08-10-p2-p6-workspace-preprocessing-design.md

@@ -44,7 +44,9 @@ Every operation binds these values before doing work:
 
 - workspace ID;
 - exact 40-hex active Git commit;
-- exact canonical descriptor snapshot;
+- catalog entry (`thoth-workspaces.yaml`) and exact canonical descriptor snapshot (the catalog blob
+  and descriptor blob at that same commit; a docs-only or content-only commit is still a distinct
+  revision even when the descriptor blob is unchanged, because the commit is authoritative);
 - installation-local bindings resolved under configured secret roots;
 - runtime roots beneath `/data/sessions/<workspace-id>`;
 - internal Qdrant/Ollama contract;
@@ -169,7 +171,7 @@ rollback of lost vector data.
 The canonical path is fixed, not descriptor-configurable:
 
 ```text
-workspace-content/<workspace-id>/schema/annotations.yaml
+<workspace-id>/schema/annotations.yaml
 ```
 
 The registry validates that the object is a regular Git blob at the same commit as the descriptor.
@@ -206,7 +208,7 @@ accepted blob and compatible reusable DWH binding; otherwise it starts a new run
 ## 8. P6 — commit-addressed Evidence materialization
 
 For filesystem Evidence, the registry materializes exactly
-`workspace-content/<id>/evidence` from the pinned commit into an immutable revision content root.
+`<id>/evidence` from the pinned commit into an immutable revision content root.
 It does not consume the mobile registry checkout and does not resolve against author files.
 
 Materialization uses fixed Git plumbing to enumerate object type, mode, path, object ID, and bytes.