Explain myscripts as an origin and learning archive

[GLyttek]

Context

myscripts is the public starting point of my practical AI work. The existing README described the current folders but did not explain that the repository spans several periods or that some files are historical learning artifacts.

Changes

• explain the repository as a historical workshop rather than one maintained application;
• link the 2024, 2025, and 2026 phases to their public commits;
• distinguish the original scripts, later prototypes, and the llm-experiments collection;
• add a status map and safer reading/running guidance;
• link the broader development record in lyttek-ai-journey.

Verification

• git diff --check
• python3 -m compileall -q .
• all local README targets resolved
• every external link in the new README returned HTTP 200 without GitHub authentication
• public-safety and style scans over the changed README

Current CI finding

The PR changes only README.md. The build-linux job reaches Flake8 and fails on three pre-existing F821 undefined-helper errors in llm-experiments/youtube-rag/yt-rag.py. That file is byte-identical between main and this branch. The README now records this current check state instead of implying repository-wide compatibility.

Limits

This is a documentation-only change. It does not convert historical code into maintained reference implementations, repair the YouTube-RAG experiment or workflow, or modify the existing open feature PRs.