feat: add Jetson contributor validation path

CONTRIBUTING.md

@@ -206,8 +206,8 @@ them in the managed environment.
 
 ## Conditional and hardware testing
 
-GPU, MPS, MLX, model-download, external-evaluation, network, operator-UI, and
-remote-execution checks are conditional release or risk-surface gates. A unit test
+GPU, Jetson, MPS, MLX, model-download, external-evaluation, network, operator-UI,
+and remote-execution checks are conditional release or risk-surface gates. A unit test
 with a mocked device is still required; hardware evidence complements deterministic
 contract coverage and never replaces it.
 
@@ -222,6 +222,13 @@ Current operator hardware includes Titan for CUDA/bitsandbytes probes and Mutsu,
 machines are attached to a public pull-request workflow; CI or a maintainer will
 record whether the mapped conditional gate ran.
 
+Jetson contributors do not need project-owned hardware access. Follow the
+[Jetson contributor bootstrap](docs/platforms/jetson.md#experimental-contributor-bootstrap)
+on a physical device, then submit the generated sanitized evidence through the
+[Jetson runtime report](https://github.com/elder-plinius/OBLITERATUS/issues/new?template=jetson-runtime.yml). Maintainers
+will reproduce, add missing test depth, and integrate compatible changes. Never
+attach a contributor-controlled runner to untrusted pull-request execution.
+
 ## Security and supply-chain expectations
 
 - Treat issue text, pull requests, patches, model repositories, checkpoints,