docs(install): document local clone+link flow and CI install smoke

[Munawarx]

Summary

Makes Leadline installable without the npx github: specifier. package.json is private: true, so an npm package isn't publishable yet; this adds a documented local install path plus a CI job that proves it.

Changes

• README "Get started": add a git clone && npm install && npm link flow so the leadline command is available from a current checkout, and a note that the npm package is still on the roadmap. Document the Node ≥ 18 requirement and the Linux-only exam harness caveat.
• .github/workflows/ci.yml: add an install-smoke job (ubuntu-latest, Node 20) that runs npm ci → npm link → invokes the leadline CLI, proving the documented install path works on a clean runner.

Why

Contributors on non-Linux hosts (and anyone who wants a pinned local copy) had only the GitHub-specifier install. A reproducible local install lowers the contribution barrier and is the interim step before a published npm package.

Verification

• README change is docs-only; CI adds a job that exercises npm link + the CLI.
• No engine / contract-engine / schema / security-boundary changes — docs/infra per CONTRIBUTING.

Trade-offs

• Keeps private: true (no published package yet) — the clone+link path is the supported interim. When the maintainer is ready to publish, flipping private: false + adding prepare/version tagging is the follow-up.

Files

• README.md
• .github/workflows/ci.yml

Co-Authored-By: Hermes Agent noreply@hermes.ai

[Munawarx]

Tracking our current contribution set for Leadline (Munawarx). All are independent, each on its own branch:

• fix(router): add deterministic current-state runtime tells (issue #10) #12 fix(router): deterministic current-state runtime tells — closes issue Router: natural phrasings of the core question class are missed (1 of 5 on real prompts) #10 direction docs: contribution rules + security policy #2 (4/5 → 5/5 natural phrasings route). RED test + bench before/after included.
• refactor(receipts): remove dead createClaimSupportReceipt helper #13 refactor(receipts): remove dead createClaimSupportReceipt helper — dead-code cleanup, 44/44 suite green.
• docs(install): document local clone+link flow and CI install smoke #14 docs(install): document local clone+link flow + CI install-smoke — interim install path until npm publish.
• fix(exam): cross-platform fallback for the labelling/replay harness #15 fix(exam): cross-platform fallback for the labelling/replay harness — extends docs: document the Linux-only requirement for the exam/replay harness #6; best-effort (not race-safe) off-Linux, Linux path unchanged.
• feat(router): project-registerable component nouns (issue #10 dir #3) #17 feat(router): project-registerable component nouns — issue Router: natural phrasings of the core question class are missed (1 of 5 on real prompts) #10 direction docs: link CONTRIBUTING and SECURITY from README #3; design pre-posted as feat(router): project-registerable component nouns (issue #10 direction #3) #16 (core-surface, per CONTRIBUTING).
• docs: document the Linux-only requirement for the exam/replay harness #6 docs: Linux-only exam requirement (still open from earlier).

Each PR is self-contained and ready to review independently. Happy to split, adjust, or rebase any of them. Co-Authored-By: Hermes Agent noreply@hermes.ai

[Nazim22]

Verified: two blockers. (1) The documented "dry-run" flow actually writes 7 files (settings.json hooks, .leadline/config.yaml + packs) — that's upstream bug #18, being fixed; these docs should land AFTER so they document the corrected behavior. (2) The CI smoke leadline --help || leadline init --claude-code --dry-run short-circuits — --help exits 0 so the init path is never exercised. Deferring until #18 ships; a rebase then would be welcome.