Scope HC-4 to repository content

Signed-off-by: Nate W <natew@cncf.io>
Assisted-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: nate-double-u

specs/ai-assisted-techdocs-assessment-spec.md

@@ -137,11 +137,12 @@ the labor. AI drafts, humans decide, all in the open.
   a technical writer still starts it (section 5).
 - HC-3: Deliverables are files in cncf/techdocs. Including the issue backlog
   (one file per proposed issue). Nothing is filed to an external repo.
-- HC-4: No unattended autonomy. Content the agent produces lands only through a
-  human-reviewed PR, and the agent never self-merges. Deterministic lifecycle
-  bookkeeping fired by a human decision, such as the merge-triggered workflow
-  that opens the next phase's tracking issue (section 12), is not autonomy: no
-  model runs, and the human act that fires it is an approval already given.
+- HC-4: No unattended autonomy. Repository content the agent produces lands only
+  through a human-reviewed PR, and the agent never self-merges. Deterministic
+  lifecycle bookkeeping fired by a human decision, such as the merge-triggered
+  workflow that opens the next phase's tracking issue (section 12), is not
+  autonomy: no model runs, and the human act that fires it is an approval
+  already given.
 - HC-5: Provenance required. Quantitative claims (counts, link status,
   inventories) must be generated by a committed, re-runnable step and cite their
   source; no unverifiable figures in a deliverable.