docs: accepted contribution scope + runnable sample Home Assistant

[ai-hpc]

Highlights the accepted contribution scope in the README and ships a runnable sample Home Assistant — the GenieClaw Jetson deployment's actual mock-home config — so the "real HA" bar is reproducible.

What this adds

• README → Accepted contribution scope: a PR is accepted only if it's (1) a measurable performance improvement, or (2) a tool-dispatch / real-Home-Assistant error fix reproduced against a real HA — with reproducible on-device proof. Anything else is closed.
• deploy/homeassistant/: the Jetson's verbatim mock-home configuration.yaml (Demo integration + input-helper mocks + template sensors) + a docker-compose that bind-mounts it, so the simulated house loads with no UI step — the exact home GenieClaw is tested against.

Exactly how BFCL accuracy is improved (no bigger model)

Grounding the predict prompt in the home device catalog (#399) — Qwen3-4B @ 4096, 208 HA-Intents cases, on the Jetson:

metric	before	after
raw strict accuracy	20.19%	50.96%
grounded strict	72.12%	82.69%
tool-name	98.08%	97.12%

Raw tool-call accuracy went 2.5× — same model, same 4096-token context, purely from deterministic device-state grounding (not scale). With the prefix cache live (genie-ai-runtime#85) the same run reproduces 51.44% / 83.65% in ~20 min (vs ~62).

A real Home Assistant error, before → after (#400)

Connected to the live mock-home HA and drove the agent to control a light.

Before — genie-ctl chat "turn off the kitchen lights":

[home_control] The tool result indicates that the action 'turn off' is invalid for the
kitchen light; valid actions include turn_on, turn_off, toggle, set_brightness, ...

→ light.kitchen_lights stayed on. The model emitted "turn off" (space); the runtime required exact "turn_off", so a correct intent silently failed to actuate.

After — the runtime canonicalizes the action verb ("turn off" → "turn_off"):

BEFORE  light.kitchen_lights: off
$ genie-ctl chat "turn on the kitchen lights"
[home_control] The kitchen lights have been turned on with a brightness of 70%.
AFTER   light.kitchen_lights: on

→ off → on, confirmed via the HA /api/states. The device actually actuates.

Real Behavior Proof

Docs + deploy-config only — no source/build surfaces touched; the sample mirrors the live HA these examples were produced on.

• Docs/deploy-config change verified by review; no code paths affected.