Align contributor documentation with the repository, and check that it stays aligned

[Crypto2099]

Summary

Brings the contributor-facing documentation in line with the repository as it actually is, and adds a check so the next divergence fails a build instead of misleading a reader.

Every correction below was verified against the tree rather than assumed.

Tracking: se7en-labs-inc#14, whose first two tasks ship in #3387. The two forms here cover the report categories that a general bug form serves worst.

The pull request template

The checklist required a thread on a Slack workspace this project cannot reach, two GitHub teams that do not exist, a named individual reviewer, and a Jira ticket. It asked for yarn manage:translations, which is now yarn i18n:manage, and a CHANGELOG entry that 20 of the last 25 merged pull requests did not add.

The replacement names the exact local command for every CI check, so a reviewer reproduces what the build will do rather than asserting it from memory. The code quality items carry over unchanged.

Issue forms for sync and hardware wallet problems

Sync failures are explained by where the blockchain is stored and on what kind of volume, not by the steps the user took. Hardware wallet failures depend on four components that version independently: Daedalus, the device firmware, the Cardano app, and the operating system. A general bug form asks for none of that, so those reports arrive needing a round trip before triage can begin.

Both forms open with the diagnostic information from Help > Daedalus Diagnostics. That instruction assumes the copy control in #3384; until it lands there is nothing for a reporter to click, so the two want to land together or close to it.

The device list is the set Daedalus supports, from source/common/types/hardware-wallets.types.ts.

Corrections to the guidance set

Claim	Reality
AGENTS.md and .agent/readme.md: Electron 24.2.0	package.json resolves 41.3.0
Both tables: tests are *.test.tsx	73 *.spec.ts, zero *.test.tsx
Two skills linked under skills/frontend/	They live directly under skills/
theme-management/SKILL.md: four links	All resolve above the repository root
frontend.md: useContext(IntlContext)	Absent from the tree; the API postdates react-intl 2.9.0
frontend.md: composes: in SCSS	Zero occurrences in source/
test.md: pre-commit and pre-push hooks	No git hooks; no husky, no lefthook
state-management.md: setupStores(api, actions)	setUpStores, four parameters
tests/README.md: yarn test:e2e:byron, yarn nix:dev	Neither script exists; no @byron scenarios
installers/README.md: default.nix, cardano-sl-src.json	Neither file is present

The skills table also omitted thermo-nuclear-code-quality-review.

The check

Documentation drifts here because nothing can fail. Each correction above was mechanically decidable and none of it was decided, because no check looked.

nix build .#checks.x86_64-linux.docs makes four assertions over tracked markdown:

1. Every relative link resolves.
2. Every yarn command named inside backticks is a script in package.json, a yarn subcommand, or a listed exception carrying its reason.
3. References to systems this project no longer uses do not reappear.
4. Versions restated in prose match what package.json resolves.

.agent/plans/ and CHANGELOG.md are excluded. Both are records of what was true when written, correct as history and wrong as present-tense instruction. Asserting over them would either fail permanently or require editing the record to keep a build green.

BESTPRACTICES.md is exempt from the third assertion, with the reason recorded in the check. Its Git chapter prescribes a develop branch and YouTrack identifiers; retiring that document is a decision in its own right, and half-editing a file that may be going away is worse than naming the exemption.

Verification

nix build .#checks.x86_64-linux.docs passes over 51 files. Reintroducing each historical failure was confirmed to fail it:

.agent/readme.md:92   link does not resolve: ./skills/frontend/i18n-messaging/SKILL.md
.agent/readme.md:274  documents 'yarn manage:translations', which is not a script in package.json
.agent/readme.md:274  refers to 'daedalus-qa': a GitHub team that does not exist
AGENTS.md:49          states Electron 24.2.0; package.json resolves electron to 41.3.0

nix fmt reports no changes. Both issue forms parse as GitHub issue form schemas.