Repository navigation
Generate repeated metadata and complete upstream tool checks #87
Description
Problem
Package versions and model data appear in multiple files. Manual updates can leave these files inconsistent.
The repository already has upstream comparison and three-way merge tools. This issue does not require replacement tools.
Required work
- List repeated metadata and identify one source for each fact.
- Generate required copies from those sources.
- Add a CI check that detects stale generated files.
- Compare the existing upstream tools with the requirements below.
- Add only missing controls or tests. Keep metadata and upstream tool changes in separate focused PRs.
Completion conditions
- Repeated generation produces the same output.
- Dry-run commands leave files and Git references unchanged.
- Tests cover upstream additions, removals, local changes, conflicts, and unsafe paths.
- Tools report conflicts without overwriting local changes.
- Tools preserve the decision ledger and required adoption approvals.
- Tools do not advance the incorporated baseline or merge unreviewed content.
- Generated metadata preserves supported behavior.
Any intentional behavior change needs a separate scope and verification.
Activity
[-]Reduce metadata drift and automate mechanical upstream adaptations[/-][+]Generate repeated metadata and complete upstream tool checks[/+]arjitj2 commentedon Oct 18, 2026
Related assessment PR #160 is merged. It records Cursor's documentation checker as excluded.
The checker assumes Cursor's directory layout, exhaustive README inventories, built-in commands and model names. The distribution retains its existing documentation checks.
This assessment adds no metadata generator or upstream merge controls. This issue remains open for its broader completion conditions.
Next, inventory repeated metadata and compare existing upstream tools against those conditions. Implement missing controls in separate focused PRs.
arjitj2 commentedon Oct 27, 2026
Release 1.17.7 metadata status
PR176 updated release metadata for1.17.7. Metadata generation and the remaining upstream-tool controls are still outstanding.
This issue remains open. Identify each metadata owner, generate required copies and test idempotence in separate focused PRs. Preserve the ledger and adoption approvals.