sb-adoptlisted

# Establish Specs from a fixed existing implementation ## Apply project language style Before authoring any artifact or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT` means no additional project preference; any `ERROR` line stops the workflow. Read this procedure completely only when the maintainer explicitly asks to establish Specs from existing code and tests or to resume an active reverse establishment. This is reverse establishment, not ordinary change Discovery and not a product release. Existing code and tests are **evidence**, never automatic authority for what the product ought to promise. Reverse establishment creates no Tasks and never changes implementation, tests, dependencies, configuration, or Steering. ## Fix the evidence and version Run the read-only route preflight first: ```sh specbind adoption preflight ``` It reports exactly one ready result: - `ADOPTION_PREFLIGHT_READY` starts a new reverse establishment. Record its exact `source_revision` and continue with this section. - `ADOPTION_RESUME_READY` proves a clean, internally consistent active reverse milestone, matching temporary record, and unchanged implementation source. Go directly to [Resume an active reverse milestone](#resume-an-active-reverse-milestone). If it stops on missing Steering, report that `sb-steering` is a separate maintainer-gated workflow and stop this reve