docs: publish v1.2.0 Go archive pins (#159)

Author: tonyredondo

README.md

@@ -168,6 +168,26 @@ prints `RTO_COMMIT`, `RTO_ARCHIVE_URL`, `RTO_ARCHIVE_SHA256`,
 and the default Orchestrion version. Published GitHub pins use `tar.gz`; other
 archive types must be mirrored and documented outside this helper.
 
+Current `v1.2.0` GitHub pins:
+
+```bash
+RTO_COMMIT="69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_REMOTE="https://github.com/DataDog/rules_test_optimization.git"
+RTO_ARCHIVE_URL="https://codeload.github.com/DataDog/rules_test_optimization/tar.gz/69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_ARCHIVE_SHA256="fd54d1871fc01ff0bb3db190dfaadaa8256edd68a4f3bb85ecc08b315fbf5bd4"
+RTO_ARCHIVE_PREFIX="rules_test_optimization-69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_ARCHIVE_TYPE="tar.gz"
+RULES_GO_VARIANT="complete"
+RULES_GO_STRIP_PREFIX="third_party/rules_go_orchestrion_complete"
+DD_TRACE_GO_VERSION="v2.9.0-rc.2"
+ORCHESTRION_VERSION="v1.9.0"
+```
+
+The archive URL, SHA256, and prefix are tied to the repository commit. Use the
+same values with `RULES_GO_VARIANT="base"` and
+`RULES_GO_STRIP_PREFIX="third_party/rules_go_orchestrion_base"` when a
+consumer should use the base variant instead of the complete variant.
+
 Consumers using the Go bootstrap can print the same tuple or write a
 repository-local summary:
 

docs/Installation_Reference.md

@@ -89,6 +89,9 @@ For mirrored/archive installs, also pin and verify archive `sha256` values (see
 "Archive mirror installation" below) so the fetched source is integrity-checked
 in CI and local builds.
 
+For `v1.2.0`, use commit
+`69953536d4ef1252c8181c267d16c61263f0aa4c`.
+
 ### Generate published Go pins
 
 Before copying Go/Orchestrion pins into a consumer repository, generate them
@@ -110,6 +113,26 @@ The command prints the full tuple used by WORKSPACE archive mode:
 `ORCHESTRION_VERSION`. Published GitHub codeload pins are `tar.gz`; use a
 separate repository-owned mirror process for any other archive format.
 
+#### Current `v1.2.0` published tuple
+
+```bash
+RTO_COMMIT="69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_REMOTE="https://github.com/DataDog/rules_test_optimization.git"
+RTO_ARCHIVE_URL="https://codeload.github.com/DataDog/rules_test_optimization/tar.gz/69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_ARCHIVE_SHA256="fd54d1871fc01ff0bb3db190dfaadaa8256edd68a4f3bb85ecc08b315fbf5bd4"
+RTO_ARCHIVE_PREFIX="rules_test_optimization-69953536d4ef1252c8181c267d16c61263f0aa4c"
+RTO_ARCHIVE_TYPE="tar.gz"
+RULES_GO_VARIANT="complete"
+RULES_GO_STRIP_PREFIX="third_party/rules_go_orchestrion_complete"
+DD_TRACE_GO_VERSION="v2.9.0-rc.2"
+ORCHESTRION_VERSION="v1.9.0"
+```
+
+The archive URL, SHA256, and prefix are tied to the repository commit. Use the
+same values with `RULES_GO_VARIANT="base"` and
+`RULES_GO_STRIP_PREFIX="third_party/rules_go_orchestrion_base"` when a
+consumer should use the base variant instead of the complete variant.
+
 From a consumer that already has the Go companion available, the bootstrap can
 print the same tuple or write a checked-in Markdown summary:
 

docs/Language_Onboarding.md

@@ -233,7 +233,10 @@ Start by identifying the existing Go shape:
 Wire the public WORKSPACE helper instead of copying patch directories or
 declaring `patches = [...]`. Use `rules_go_variant = "base"` for normal
 repositories. Use `rules_go_variant = "complete"` only when the repository
-needs the declared extended monorepo compatibility variant.
+needs the declared extended monorepo compatibility variant. Use the current
+published tuple from
+[`docs/Installation_Reference.md`](Installation_Reference.md#current-v120-published-tuple)
+for the commit, archive URL, archive SHA256, and archive prefix values.
 
 ```bzl
 load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository")

docs/Troubleshooting.md

@@ -116,7 +116,9 @@ or a tuple that was not generated from the real GitHub codeload archive.
 
 3. **Keep the generated tuple together**. If `RTO_COMMIT`,
    `RTO_ARCHIVE_URL`, `RTO_ARCHIVE_SHA256`, and `RTO_ARCHIVE_PREFIX` come from
-   different commits, archive mode will fail or fetch the wrong source.
+   different commits, archive mode will fail or fetch the wrong source. The
+   current published tuple is tracked in
+   [`docs/Installation_Reference.md`](Installation_Reference.md#current-v120-published-tuple).
 
 4. **Authenticate private archive downloads**. The helper uses `GITHUB_TOKEN`,
    `GH_TOKEN`, or `gh auth token` when available. If codeload returns `404` for

tools/agent-skills/go-test-optimization-onboarding/references/workspace-onboarding.md

@@ -50,7 +50,9 @@ From this repository, generate published pins with:
 ```
 
 Use `--variant base` for normal repositories and `--variant complete` for large
-monorepos that need the compatibility layer.
+monorepos that need the compatibility layer. The current published release
+tuple is tracked in
+[`docs/Installation_Reference.md`](../../../../docs/Installation_Reference.md#current-v120-published-tuple).
 
 ```bzl
 load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository")