Remove tracked AI context files from base-cli after the replacement release #509

Problem

base-cli still tracks .ai-context/ as a repository-owned source even though the accepted plan replaces it with a generated export outside the repository. Cleanup must wait until the replacement ships and is proven. This repo-local issue is tracked by Base governance tracker #2665.

Expected behavior

After the generated export command is released and proven, remove tracked .ai-context/ files and stale references/scheduled exports in base-cli. Keep all canonical documentation in its documented homes; do not treat exported artifacts as checked-in source.

Scope and non-goals

Scope: One repository-specific cleanup PR for tracked context, instructions, manifest checklists and scheduled exports.

Non-goals: Do not remove files before package 13b proof; do not change the export command contract; do not remove unrelated validation rules or canonical docs.

Affected areas

• base-cli .ai-context/, AGENTS/CONTRIBUTING instructions, manifest checklist, automation and docs.
• Accepted source: governance plan #2664; context export implementation #2687.

Impact and evidence

1. Product intent: No product requirements change.
2. Architecture and contracts: Moves context from tracked duplicate files to a derived external artifact as accepted.
3. User guidance: Update repository setup/use instructions that point to .ai-context/.
4. CLI/API and reference: Document basectl export-context output/use or justify no local command reference.
5. Operations and safety: Verify privacy, output path and scheduled-task behavior before deletion.
6. Validation and testing: Search tracked files/workflows and test that exports remain outside the repo.
7. Examples and downstream use: Update examples that read .ai-context/; otherwise cite a repository-wide search.
8. Governance and contributor process: Update agent/contributor instructions to canonical documents.
9. Decision records: No new decision; cite the accepted design and export contract.
10. Release notes: Reasoned none if cleanup only removes internal derived files; otherwise explain user impact in the PR.

Open questions

• Confirm package 13b release version and evidence before moving this issue to Ready.

Plan

• S1: One focused cleanup PR in base-cli after the export gate.
• Dependencies: Export command #2687 and the repo's updated PR contract.
• Acceptance criteria:
  • Export command is released and proof covers output location, source attribution, privacy and failure behavior.
  • All tracked .ai-context/ files and stale references/scheduled exports are removed or migrated.
  • Repository instructions point to canonical docs and generated output remains outside the repo.
  • No unrelated validator or workflow contract is removed.
• Validation: Search tracked files for .ai-context/; run relevant repo checks and git diff --check; verify export output leaves repo status clean.
• Risks and rollback: Early cleanup creates a context gap; defer until proof and restore files/schedules through a reviewed PR if the replacement regresses.
• Decision impact: No new decision is accepted.