docs: align legacy positioning with project source

[ProfRandom92]

Motivation

• Remove legacy naming and positioning contradictions between older docs and the canonical governance sources so contributors and reviewers see a single authoritative framing.
• Normalize the human-facing project name to CompText V7 in targeted legacy files to reduce confusion.
• Keep the change minimal and reviewer-oriented while preserving existing agent discipline and fixture-bound caveats.

Description

• Update AGENTS.md title to # CompText V7 Agent Instructions and replace the first project-focus bullet with the canonical replay-integrity phrasing.
• Normalize the heading and the opening paragraph in docs/research_positioning.md to the canonical replay-integrity language while preserving the rest of the document and its prototype-scoped caveats.
• Replace the conflicting runtime/dashboard sentence in docs/API_SURFACE.md with wording that treats API, dashboard, export, and report surfaces as deterministic review and evidence handoff surfaces (explicitly not runtime orchestration, live monitoring, or platform expansion).
• Limit edits to AGENTS.md, docs/research_positioning.md, and docs/API_SURFACE.md only, with no changes to code, fixtures, artifacts, workflows, package files, README, or tests.

Testing

• Ran npm run check, which invoked repository layout, TypeScript typechecks, validate/build steps, and pytest as part of the check pipeline, and completed without error.
• All automated tests passed: pytest reported 283 passed and the overall npm run check succeeded.

---

Codex Task

[gemini-code-assist]

Code Review

This pull request updates the project name to "CompText V7" and refines the research positioning and API surface descriptions across several documentation files to emphasize deterministic replay integrity. Review feedback indicates that the name update is inconsistent, as several instances of the legacy name "Comptextv7" remain in "docs/API_SURFACE.md" and "docs/research_positioning.md", which should be corrected to align with the repository style guide.

[gemini-code-assist]

While this paragraph is updated to use the canonical project name CompText V7, several other occurrences of the legacy name Comptextv7 remain in this file (e.g., on lines 5, 35, 80, and more). To fully align with the PR's goal of reducing confusion and adhere to the project's established naming convention, please consider updating all instances of the project name within this document for consistency.

References

1. The repository style guide establishes 'CompText V7' as the canonical project name (lines 1, 4). For consistency, this name should be used throughout the project documentation. ^(link)

[gemini-code-assist]

The heading and opening paragraph now correctly use CompText V7. However, the rest of the document still contains numerous instances of the legacy name Comptextv7 (e.g., on lines 5, 7, 23). This creates an inconsistent naming convention within the same file, which could be confusing for readers. To ensure consistency with the project's established naming, it would be beneficial to update all occurrences of the project name throughout this document.

References

1. The repository style guide establishes 'CompText V7' as the canonical project name (lines 1, 4). For consistency, this name should be used throughout the project documentation. ^(link)