State the proposal scope where proposals are made

The automation fences commits to questions/*.yaml and aggregates.yaml;
the page and README now say so, instead of promising "any file" and
silently failing after approval.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

README.md

@@ -112,7 +112,8 @@ entirely in this repo, in this order:
    and its workflow must be updated in lockstep.
 
 5. **Change the system through itself.** `/develop-proposal` takes a
-   proposed replacement for any file in this repo — from a person, or
+   proposed replacement for any content file (`questions/*.yaml` or
+   `aggregates.yaml` — nothing else is in scope) — from a person, or
    eventually a locally-run model, through the same public form. An
    owner approves it on `/develop`; approval triggers the automation
    that branches, commits, opens a PR, and merges only when the same

questions/develop-proposal.yaml

@@ -9,9 +9,10 @@ description: >
 alternatives:
   - name: The change you propose
     description: >
-      The proposed content replaces (or creates) one file in the
+      The proposed content replaces (or creates) one content file —
-      questions repo, verbatim — so it has to be complete, valid YAML
+      a page under questions/, or aggregates.yaml — verbatim, so it
-      for that file, not a diff.
+      has to be complete, valid YAML for that file, not a diff.
+      Nothing outside those files is in scope.
     action: /proposed
     consequence: [Propose it]
     record_as: development_proposals