Bootstrap OpenBitdo clean-room SDK and reliability milestone

process/branch_policy.md

@@ -0,0 +1,16 @@
+# Branch and Merge Policy
+
+Because this workspace currently has no active Git repository metadata, this policy is documented for use when repository control is re-enabled.
+
+## Branches
+- `codex/dirtyroom-spec`: sanitize findings into `cleanroom/spec` and `cleanroom/process`
+- `codex/cleanroom-sdk`: implement SDK and CLI from sanitized artifacts only
+
+## Merge Strategy
+- Cherry-pick sanitized spec commits from dirtyroom branch into cleanroom branch.
+- Never merge dirty-room evidence paths into cleanroom implementation branch.
+
+## Review Checklist
+- Guard script passes.
+- No forbidden path references in code/tests.
+- Requirement IDs are traceable from implementation and tests.

process/cleanroom_rules.md

@@ -0,0 +1,23 @@
+# Clean-Room Rules
+
+## Allowed Inputs During Clean Implementation
+- `cleanroom/spec/**`
+- `cleanroom/process/cleanroom_rules.md`
+- `cleanroom/harness/golden/**`
+
+## Forbidden Inputs During Clean Implementation
+- `decompiled/**`
+- `decompiled_*/*`
+- `bundle_extract/**`
+- `extracted/**`
+- `extracted_net/**`
+- `session-ses_35e4.md`
+
+## Enforcement
+- `cleanroom/sdk/scripts/cleanroom_guard.sh` checks for forbidden path and token references.
+- CI runs the guard before test jobs.
+
+## Commit Hygiene
+- No copied decompiled code snippets.
+- No direct references to dirty-room files in SDK implementation/tests.
+- Any new protocol fact must be added to sanitized spec artifacts first.