ARCHITECTURE.md Feature Codes table: Scope Boundary extraction only uses first line and doesn't handle multiple FEAT files per code

[six5536]

Bug Report

The Feature Codes table in ARCHITECTURE.md is auto-generated from the Scope Boundary section in FEAT-{CODE}-*.md files. There are two issues with the current extraction logic:

Issue 1: Only the first line of Scope Boundary is used

When the Scope Boundary section contains a multi-line description like:

This feature covers:

- Item 1
- Item 2

The generated Feature Codes table only shows This feature covers: — the introductory line — instead of the actual bullet points that describe the scope.

Expected: The table should include the meaningful content from the Scope Boundary (e.g. the bullet list items), or at minimum more than just the first line.

Issue 2: Ambiguous FEAT file selection when multiple files share a code

There may be multiple FEAT-{CODE}-*.md files for the same feature code (e.g. FEAT-CLI-version.md, FEAT-CLI-man-page.md, etc.). The Scope Boundary can only be taken from one file, but it is unclear which file is selected, and there is no documented or deterministic selection rule.

Expected: Either:

• Document which file takes precedence, or
• Aggregate scope boundaries from all matching files, or
• Use a deterministic rule (e.g. alphabetical first, or a designated primary file)

Reproduction

1. Create a FEAT-{CODE}-*.md with a multi-line Scope Boundary section
2. Run architecture generation
3. Observe the Feature Codes table only shows the first line of the Scope Boundary