fix: harden location extraction and docs automation safety

[Copilot]

Summary

• Fixed greedy location capture while preserving case-insensitive keyword matching by updating extractLocations to use Unicode-aware capture rules with scoped case sensitivity.
• Added regression coverage in tests for uppercase keyword inputs (for example LOCATION / NEAR) to ensure location extraction behavior remains correct.
• Corrected docs generation section replacement logic to find each end marker only after its matching start marker.
• Hardened the docs workflow by adding explicit minimal GITHUB_TOKEN permissions (contents: read) to satisfy security checks.

Checklist

• I reviewed whether this change affects README, architecture docs, or legacy docs.
• If commands, supported file types, or layout metadata changed, I ran npm run docs:generate.
• I ran npm run docs:check.
• If historical Python prototype guidance changed, I updated docs/legacy-prototype.md.

[Copilot]

Pull request overview

This PR tightens location extraction to avoid case-insensitive regex behavior causing greedy captures, and introduces a small docs automation workflow (generated README sections + validation) to keep documentation aligned with the current Node CLI implementation.

Changes:

• Adjusted extractLocations regexes to prevent greedy capture of trailing lowercase words.
• Added documentation generation + validation scripts, wired into package.json and a GitHub Actions workflow.
• Refreshed README + architecture/diagram docs and moved Python prototype guidance into docs/legacy-prototype.md.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/ingestion/file-ingestion.js	Updates location-extraction regex flags/keywords to prevent greedy captures.
scripts/validate-docs.js	Adds a docs consistency validator for scripts/docs/README cross-references.
scripts/generate-docs.js	Adds README section generator for commands/file-types/layout sections.
README.md	Refocuses README on current Node CLI and adds generated sections + docs workflow guidance.
package.json	Adds docs:generate and docs:check scripts.
docs/legacy-prototype.md	Introduces a dedicated legacy doc for the Python prototype.
docs/docs-source.json	Adds metadata source for generated README sections and required-doc links.
docs/diagrams/sequenceDiagram.mermaid	Updates sequence diagram labels to clarify current vs planned behavior.
docs/diagrams/architectureDiagram.mermaid	Updates architecture diagram to distinguish current components vs planned expansion.
docs/architecture.md	Rewrites architecture doc into “current vs planned” structure and references diagrams.
.github/workflows/docs.yml	Adds CI job to run docs validation on PRs and releases.
.github/pull_request_template.md	Adds a checklist prompting docs checks.
.github/prompts/update-readme.prompt.md	Updates prompt to cover the full “active documentation set” and generation workflow.

[Copilot]

Pull request overview

Copilot reviewed 13 out of 13 changed files in this pull request and generated 2 comments.

[aj1126]

Summary

• The i flag on both regex patterns in extractLocations caused [A-Z] in the capture group to match lowercase letters, making (?:[ -][A-Z][a-zA-Z]+)* greedily consume entire phrases (e.g. "Roswell and hovered over the desert") instead of stopping at the location name.
• Removed i flag from metadataPattern and sentencePattern; added explicit title-case variants to the keyword groups to preserve case-insensitive keyword matching without affecting the capture group.

// Before — i flag bleeds into capture group
/\b(?:location|city|site)\s*:\s*([A-Z][a-zA-Z]+(?:[ -][A-Z][a-zA-Z]+)*)/gi

// After — keywords handle their own case; [A-Z] strictly means uppercase
/\b(?:location|city|site|Location|City|Site)\s*:\s*([A-Z][a-zA-Z]+(?:[ -][A-Z][a-zA-Z]+)*)/g

Checklist

• I reviewed whether this change affects README, architecture docs, or legacy docs.
• If commands, supported file types, or layout metadata changed, I ran npm run docs:generate.
• I ran npm run docs:check.
• If historical Python prototype guidance changed, I updated docs/legacy-prototype.md.

@copilot what must be done to finish the checklist?