feat(realtime): adapt semantic endpointing controls - #107

…, first issues

Three outside contributors showed up in one day (kvnloo, TheAngryPit,
webdevtodayjason) and found a CONTRIBUTING that covered setup and lint but
not what we want, where a change starts, or what a PR has to carry. This
makes the next thirty obvious. Markdown and YAML only; no Python changes.

CONTRIBUTING.md, rewritten around the existing facts (every one kept —
setup, the ruff pin, the TheSmokeDev#93 baseline, the module table now including
talk_check and talk_diagnostics, the adversarial-review paragraph, the
SHA-pinned-actions and BLE001/RUF100 rules):
- ranked priorities for THIS repo: live-lane bug fixes > provider/host
  compatibility > security hardening (auth store, token routing, redaction)
  > cross-platform > new providers behind the contract > new surfaces > docs
- a common-paths table — provider, surface, talk tool, fix, docs — naming
  the files each touches and ships with (talk_realtime.py contract,
  talk_core_provider.py lane, talk_config/talk_cli/talk_doctor wiring,
  pyproject py-modules; the DuplexAudio method set a surface implements;
  the _HANDLERS + READ_ONLY/MUTATING classification a tool needs)
- why `uv run --extra dev`, node for the two dashboard JS tests, and how to
  run a branch live (`hermes plugins install --force --ref <sha>`)
- branch names and Conventional-Commit scopes derived from the last 200
  commits, the PR description contract, the merge bar, a
  first-response-within-24h review promise, and how credit works

.github/PULL_REQUEST_TEMPLATE.md carries the same contract: what/why, how
to test, platforms, a `check --json` receipt when a lane is touched,
`Fixes #N`, a checklist that repeats the merge bar.

Issue forms: feature_request.yml (problem first, proposal second, which
surfaces and providers), provider_compatibility_report.yml (PASS/PARTIAL/
FAIL, provider, model, credential lane, versions, which events were
observed — SessionReady / SpeechStarted / FunctionCall round-trip /
barge-in — the `check --json` report, the wire error verbatim; no audio,
transcripts, or secrets), bug_report.yml gains the core-contract lane and
the check/doctor/diagnostics commands as surfaces plus a pointer to the
provider form, config.yml links private security reporting and
Discussions first.

docs/PROVIDER-RECEIPT.md: the two-minute procedure (`check --json`, then
one short call with a five-row tick list), the table the form mirrors,
and how maintainers act on each verdict — the unticked event names the
adapter function; the wire error becomes the regression fixture. Ported
idea from bielcarpi/hermes-live-voice's compatibility receipt (MIT) —
idea only, no text.

README: Contributing shortened to the pointer plus the promise, a
Contributors line crediting @kvnloo (TheSmokeDev#81 merged, TheSmokeDev#107 in review),
@TheAngryPit (TheSmokeDev#80 in review), @webdevtodayjason (second-consumer feedback
on upstream hermes-agent#81404, the contract our lanes register on).
CHANGELOG [Unreleased] → Added.

Repo settings alongside (not in this diff): labels provider, surface,
security, docs created; good first issue + help wanted on TheSmokeDev#93, help wanted
on TheSmokeDev#90 and TheSmokeDev#51; Discussions were already enabled.

— SmokeDev