Add initial design files for music-history

[FarPointer]

What this changes

Checklist

• Scoped to this change — no unrelated files swept in
• Directory README.md updated (or none needed)
• AGENTS.md updated if a working rule or convention changed

Playlist data

• Sources touched:
• make check passes — cache rebuilt, verify.py green, zero-line cache diff
• Overrides changed:
  Every override edit records a human decision, not an inference
• publication-links.json entries come from real REST responses, not guessed IDs

Tooling

• make lint and make test pass
• A regression test covers any bug fixed in an override path, parser heuristic, or gate

Safety

• No secrets: no .env*, ~/.czarchive.toml, API keys, OAuth tokens, or cookies
• Superseded work moved to discarded/ with a README.md explaining why

[FarPointer]

@copilot I want these files to go into a "music-history-db" subdirectory under specs, not in the root. Update the PR to fix that

[Copilot]

🟡 Changes recommended

The new spec includes a materially incorrect licensing statement (Discogs CC0) and some repo-inaccurate workflow guidance that should be corrected to avoid misleading implementation.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds an initial technical implementation strategy document for a KSER-focused “music history” database, outlining a Python/JSONL→SQLite pipeline, source connector contracts, and planned CI/refresh/publish workflows.

Changes:

• Introduces a new spec doc covering the proposed architecture, data model, and connector responsibilities.
• Documents network-access/rate-limit policy, testing strategy, and delivery phases for the project.
• Describes intended GitHub Actions and Copilot Cloud setup for repeatable refresh/publish automation.

File summaries

File	Description
tools/specs/KSER_Music_History_Technical_Implementation_Strategy.md	New technical strategy/specification for the planned KSER music-history database and workflows.

Review details

• Files reviewed: 1/3 changed files
• Comments generated: 4
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

@copilot I want these files to go into a "music-history-db" subdirectory under specs, not in the root. Update the PR to fix that

Moved the three files into tools/specs/music-history-db/ in b6525eb (repushed as part of latest commit after rebasing onto the autofix commits).

[FarPointer]

@copilot move this file from tools/specs/ to tools/specs/music-history-db/