Present body source and route boundaries

foundry body-source-scope --source /absolute/path/to/notes.md --json reads the exact complete new Markdown body and returns foundry.body-source-scope.v1. It uses Core’s existing source-scope rules with an empty before-body and no qualified renderer. No Hugo, site scripts, provider or Git command is executed, and no file is changed. Input must be bounded UTF-8 without NUL, at most 1 MiB.

The closed JSON object has exactly three required fields:

{
  "schema": "foundry.body-source-scope.v1",
  "source_sha256": "sha256:<64 lowercase hexadecimal characters>",
  "source_edit_required": false
}

The hash includes every input byte: whitespace, line endings and any final newline. No source text or input path appears in the report. Plain Markdown retains Markdown scope. Introducing opaque HTML, fenced code or unqualified shortcodes requires source-edit scope under the current protected-source rules. Even a standard pullquote is conservative here because this command does not bind a site’s renderer. There is no flag to claim renderer qualification.

This command describes complete new body source. It does not compare an existing body or classify front matter, catalogue data or any other publication artifact. For edits to an existing canonical recipe page, use content-document, which compares actual before/after bytes and preserves unowned metadata. Existing Journal and content-operation reports retain their historical schemas and meanings.

Foundry Control opportunity: Foundry Control can use these portable facts for media review and publishing. The caller must bind the exact Core executable and body hash, check current actor/site permissions and approval at every effect, and validate the complete publication separately. The boolean is a source fact, never an approval or permission grant.