docs: Add prerequisites and beginner resources to README

[Ivan-houzhiwen]

Summary

Added prerequisites note and beginner resources section to README.md.

Changes

• Added prerequisites note at top of README explaining required knowledge
• Added Resources for Beginners section with links to learning materials

Issue Reference

Fixes #2980

[Copilot]

Pull request overview

This PR updates top-level documentation to better onboard new contributors by adding prerequisites guidance and beginner-friendly references.

Changes:

• Added a prerequisites callout and a “Reading Guide” section to README.md.
• Added a “Resources for Beginners” section with external learning links to README.md.
• Expanded CONTRIBUTING.md with guidance on interpreting pytest output and common failure causes; added quick-reference glossaries to .claude/context/PHILOSOPHY.md.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.

File	Description
README.md	Adds onboarding guidance (prerequisites, reading guide, beginner resources) near the top of the project docs.
CONTRIBUTING.md	Adds a new section explaining test output and troubleshooting common test failures.
.claude/context/PHILOSOPHY.md	Adds short glossaries/term explanations to make philosophy docs more accessible to newcomers.

Comments suppressed due to low confidence (1)

README.md:45

• The Table of Contents doesn’t include the newly added “Reading Guide” / “Resources for Beginners” sections, making navigation inconsistent with the rest of the README’s TOC-driven structure. Add TOC entries (or intentionally keep them out, but then consider removing the TOC expectation by moving these sections under an existing TOC item).

## 📖 Reading Guide

**New to amplihack?** Start with [Quick Start](#quick-start), then [Core Concepts](#core-concepts), then [Configuration](#configuration).

**Want to contribute?** Go to [Development](#development) and [CONTRIBUTING.md](CONTRIBUTING.md).

**Already familiar?** Check out [Feature Catalog](#feature-catalog) and [Documentation Navigator](#documentation-navigator).

---

## Table of Contents

- [Why amplihack?](#why-amplihack)
- [Quick Start](#quick-start)
- [Core Concepts](#core-concepts)
- [Feature Catalog](#feature-catalog)
- [Configuration](#configuration)
- [Documentation Navigator](#documentation-navigator)
- [Development](#development)
- [RustyClawd Integration](#rustyclawd-integration)
- [License](#license)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

README.md is now 613 lines, which exceeds the repo’s enforced limit of 600 lines (tests/test_readme_structure.py::test_total_length). To avoid CI failures, consider moving the new beginner resources to a dedicated docs page and linking to it here, or trimming other sections so the README stays within 350–600 lines.

[Copilot]

The example pytest tests/test_example.py doesn’t correspond to an existing file in this repo (there is no tests/test_example.py). Using a non-existent path in the debugging tips will confuse contributors; switch to a real test file path (or keep it generic like pytest tests/test_some_feature.py).

[Copilot]

The “success” example hardcodes a specific test count/time (237 passed in 45.2s), which will go stale as tests are added/removed and as runtime varies by machine/CI. Consider using placeholders (e.g., X passed) and describing the meaning rather than pinning exact numbers.

[Copilot]

This “Key Terms Explained” blockquote duplicates the definitions immediately below in the existing “Key concepts” list (Brick/Stud/Regeneratable/Isolated). Keeping both will create drift; consider removing one of the two or making one a brief pointer to the other.

Suggested change

	> **Key Terms Explained:**
	> - **Brick** = A self-contained module with ONE clear responsibility (like a LEGO brick)
	> - **Stud** = The public interface/contract that other modules connect to
	> - **Regeneratable** = Can be rebuilt from scratch using AI without breaking the system
	> - **Isolated** = All code, tests, and fixtures live inside the module folder
	> **Key Terms Explained:** See the **Key concepts** list below for precise definitions of Brick, Stud, Regeneratable, and Isolated.

[Copilot]

The new “Resources for Beginners” H2 sits immediately after “## Why amplihack?” and before the “The Problem/The Solution” value proposition, which effectively makes the “Why amplihack?” section empty and nests the value proposition under “Resources” instead. This also pushes the “barebones / problem / solution / engineering system” keywords beyond the first 50 lines, likely failing tests/test_readme_structure.py::test_value_proposition_in_first_50_lines. Move Resources later (or make it a subheading under Why after the problem statement) so the value proposition stays near the top.