coygeek
## Summary The JavaScript reference instructions in `apps/docs/CONTRIBUTING.md` still tell contributors to edit `spec/supabase_js_v2.yml` and describe `$ref` extraction and transformation. JavaScript v2 now uses the separate TypeDoc pipeline, which skips that YAML input. The contributor entry point therefore sends JavaScript reference edits to the wrong authoring workflow. ## Steps to reproduce 1. Inspect `supabase/supabase` at current `master` revision `4ab54b935919ba3f4bb92f436ae4e757108e4f8a`. 2. Read `apps/docs/CONTRIBUTING.md`, lines 100-128. The "Specific spec file" section links to `apps/docs/spec/supabase_js_v2.yml` as its JavaScript example and describes source parameters pulled through `$ref` and transformed by the Makefile. 3. Read `apps/docs/features/docs/Reference.constants.ts`, lines 13-24, and `apps/docs/features/docs/Reference.generated.script.ts`, lines 165-175. `javascript-v2` opts into the new pipeline, and the legacy generator excludes libraries in that set before reading their YAML specs. 4. Compare `apps/docs/spec/reference/README.md`, lines 1-35 and 70-94, with `apps/docs/spec/Makefile`, lines 46-52 and 66-70. These document and implement TypeDoc inputs for the six core JavaScript packages, hand-authored `config.json` and partials, and generation through `scripts/build-reference-content.ts`. ## Expected behavior The contributor guide identifies the active JavaScript v2 authoring workflow or routes to its reference-pipeline README. It distinguishes hand-authored SDK source comments and docs-app configuration/partials from downloaded TypeDoc JSON and generated output. Any legacy YAML instructions identify the SDKs that still use them. ## Actual behavior The guide presents JavaScript v2 YAML as the library-specific authoring example, although JavaScript v2 is excluded from the generator that consumes that file. The guide does not identify the new reference directory or link to its pipeline README. ## Affected area `apps/docs/CONTRIBUTING.md`, specifically the "Reference structure" and "Specific spec file" instructions for JavaScript v2. ## Runtime or environment This is a source-only documentation reproduction at `supabase/supabase` revision `4ab54b935919ba3f4bb92f436ae4e757108e4f8a`. It requires no package installation, database, or running docs server. No build or rendered-page result is claimed. ## Evidence - [Contributor instructions](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/CONTRIBUTING.md#L100-L128) use JavaScript YAML as the example. - [New-pipeline registration](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/features/docs/Reference.constants.ts#L13-L24) and [legacy generator exclusion](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/features/docs/Reference.generated.script.ts#L165-L175) establish which workflow JavaScript v2 uses. - [Reference-pipeline README](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/spec/reference/README.md#L1-L35) distinguishes the new pipeline from SDKs still on the legacy one. Its [source section](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/spec/reference/README.md#L70-L94) distinguishes downloaded artifacts from tracked authoring inputs. - [Makefile](https://github.com/supabase/supabase/blob/4ab54b935919ba3f4bb92f436ae4e757108e4f8a/apps/docs/spec/Makefile#L46-L70) downloads specs for `supabase-js`, `auth-js`, `postgrest-js`, `realtime-js`, `storage-js`, and `functions-js`, and states that the new pipeline needs no separate dereference/combine step. - [Merged PR #46502](https://github.com/supabase/supabase/pull/46502) migrated JavaScript v2 away from the legacy YAML render path. [Merged PR #50743](https://github.com/supabase/supabase/pull/50743) later shortened the contributor guide but retained its reference-structure section. ## Impact A contributor following the primary docs contribution guide can select a legacy file that the active JavaScript v2 reference generator skips. They must discover the separate pipeline instructions to locate the actual authoring inputs. ## Additional context The defect remains present when the contributor entry point names JavaScript YAML as the current authoring example. It is resolved when the JavaScript instructions agree with the active generator and explain or link to the supported authoring inputs and refresh workflow. The recorded baseline and freshly fetched default-branch revision are both `4ab54b935919ba3f4bb92f436ae4e757108e4f8a`, so the baseline-to-current commit range is empty. The complete paginated open issue and PR corpus, relevant closed issues, and merged contributor-guide/reference-pipeline PRs were screened. No matching open report or fix for this contributor instruction mismatch was found.