gitlab-labkit 5.6.0 → 5.6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fb00f476a5fed0be71839727d4fb5d8230f773831c8c8cca40ff8090c76cb2c5
-  data.tar.gz: c382bf0eed9e55b283eb90c3956a00c8dbf73ad5819fb22e8dd6a1be931fd9ff
+  metadata.gz: a1ef319c707c40ea0cca46358bbacdf18d1068b8f2b778ebc1a1486c33cea1ef
+  data.tar.gz: 5cbead469ab098d29afb9dcf2dd97576976a703db93eda7ea337a54bc94fcde9
 SHA512:
-  metadata.gz: 5932210330aa7c8c4413de43f8ae710508658846c89f1b7b74e1d8d36af564b61034988a6248bf9795d6343602d4b1579d6a9aff48795cda1163c545377932b9
-  data.tar.gz: ddc501d350806e384f122f152f6ceb7066487bc4f41078341f1ae13373631adf52a1f5cd427a69e879482cf3dc1dff75bbfe7cd57dd1237094c595e615acc591
+  metadata.gz: 1488c581703cab14db63d485aa2ef3159d8a0cd8449cc34b4aeeb522d97ad2207edb57096f388240cff213ef44aaa925a8219a2464b3ab4054a81b0e8569129a
+  data.tar.gz: 4c65d98b9b29084a3c5bdc7e0d9dc166a4708f203840a08180421172f21c0356005641557e46dc14f48fb277570f4bdae041d61072c454dbdfa252e4e8baf5fd

data/.claude/hooks/precommit-validate.sh

@@ -0,0 +1,47 @@
+#!/usr/bin/env bash
+# PostToolUse hook: validate a just-edited file against this repo's pre-commit rules.
+#
+# Runs `pre-commit run --files <file>` on the file that Edit/Write/MultiEdit
+# touched. On failure it prints the output to stderr and exits 2, which feeds the
+# result back to Claude so it can fix the issue. A clean run exits 0 silently.
+set -euo pipefail
+
+# no-commit-to-branch guards the branch, not file content, and would fire
+# spuriously (e.g. on jj's detached HEAD). It is irrelevant to file validation.
+export SKIP="no-commit-to-branch"
+
+# Run through `mise exec` so mise-managed tools that the hooks rely on
+# (pre-commit, jsonnet-tool, shfmt, ...) are on PATH, matching a normal
+# interactive shell.
+if ! command -v mise >/dev/null 2>&1; then
+  echo "pre-commit validation hook requires mise to run." >&2
+  exit 1
+fi
+
+run() { mise exec -- "$@"; }
+
+repo_root="$(git rev-parse --show-toplevel 2>/dev/null)" || exit 0
+
+input="$(cat)"
+file="$(printf '%s' "$input" | mise exec jq@1.8 -- jq -r '.tool_input.file_path // empty')"
+[[ -z $file ]] && exit 0
+
+# Only validate files that live inside this repository.
+case "$file" in
+"$repo_root"/*) ;;
+*) exit 0 ;;
+esac
+
+if ! output="$(cd "$repo_root" && run pre-commit run --files "$file" 2>&1)"; then
+  {
+    echo "pre-commit reported issues on ${file#"$repo_root"/}:"
+    echo
+    echo "$output"
+    echo
+    echo "Re-read the file (hooks such as trailing-whitespace, shfmt, and"
+    echo "generate may have rewritten it) and fix any remaining problems."
+  } >&2
+  exit 2
+fi
+
+exit 0

data/.claude/settings.json

@@ -0,0 +1,15 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/precommit-validate.sh\""
+          }
+        ]
+      }
+    ]
+  }
+}

data/.copier-answers.yml

@@ -3,7 +3,7 @@
 # See the project for instructions on how to update the project
 #
 # Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
-_commit: v1.60.0
+_commit: v1.85.0
 _src_path: https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git
 ee_licensed: false
 gitlab_namespace: gitlab-org/ruby/gems
@@ -17,5 +17,6 @@ release_platform: false
 ruby: true
 rubygem: true
 rust: false
+scaffold_target: repo
 terraform: false
 truncated_tags: true

data/.gitignore

@@ -2,5 +2,4 @@ Gemfile.lock
 *.gem
 node_modules
 .bundle
-/.env.sh
 .idea/

data/.gitlab/duo/agent-config.yml

@@ -7,22 +7,22 @@
 image: registry.gitlab.com/gitlab-com/gl-infra/common-ci-tasks-images/duo-workflow-sandbox:latest
 
 setup_script:
-  # Keep mise's data + cache inside the project dir so the `cache:` block below
-  # can capture them (caching only reliably covers paths under the project dir).
-  - export MISE_DATA_DIR="${CI_PROJECT_DIR}/.cache/mise/data"
-  - export MISE_CACHE_DIR="${CI_PROJECT_DIR}/.cache/mise/cache"
-  - mise trust --yes
-  - mise install --yes
+  # duo-workflow-setup (baked into the image) exports some variables as
+  # `export KEY=VALUE` lines on stdout, which we `eval` into the flow's shell.
+  - eval "$(/usr/local/bin/duo-workflow-setup)"
 
 cache:
-  # Re-use installed tools as long as the version pins are unchanged.
+  # Re-use installed tools and primed pre-commit hooks as long as the version
+  # pins / hook config are unchanged.
   key:
     files:
       - .tool-versions
       - .mise.toml
+      - .pre-commit-config.yaml
   paths:
     - .cache/mise/data
     - .cache/mise/cache
+    - .cache/pre-commit
 
 network_policy:
   # Allow the Sandbox Runtime's recommended allowlist (GitLab, package

data/.mise.toml

@@ -7,6 +7,9 @@ legacy_version_file = false
 # OpenSSL and sidesteps it. This becomes mise's default in 2026.8.0.
 ruby.compile = false
 
+# Disable sending anonymous download statistics to mise-versions.jdx.dev.
+use_versions_host_track = false
+
 [tools]
 # Please continue to use `.tool-versions` to specify tool versions, rather than adding them directly here.
 

data/.opencode/plugins/precommit-validate.ts

@@ -0,0 +1,101 @@
+import type { Plugin, Hooks } from "@opencode-ai/plugin";
+import { existsSync } from "node:fs";
+import { isAbsolute, join, resolve } from "node:path";
+
+/**
+ * precommit-validate plugin
+ *
+ * OpenCode equivalent of the Claude Code PostToolUse hook defined in
+ * `.claude/hooks/precommit-validate.sh` (wired up by `.claude/settings.json`).
+ *
+ * After the agent edits or writes a file, this runs that *same* shell script to
+ * validate the file against the repo's pre-commit rules. When pre-commit reports
+ * problems, the findings are appended to the tool result so the agent sees them
+ * on its next turn and can fix the file. A clean run is silent.
+ *
+ * The script's exit codes mirror Claude Code's hook contract, so we honour the
+ * same distinction here:
+ *   - 0 = clean or no-op (silent)
+ *   - 2 = pre-commit reported issues; feed the report back to the model
+ *   - any other non-zero = non-blocking error (e.g. mise missing); log it for
+ *     the user but do not nag the model, since it can't fix its environment.
+ *
+ * The script is reused verbatim: it reads Claude Code's PostToolUse payload on
+ * stdin (`{ "tool_input": { "file_path": "..." } }`), so we synthesize that same
+ * shape here from OpenCode's tool arguments.
+ *
+ * Auto-loaded from `.opencode/plugins/`.
+ */
+
+// OpenCode file-mutating tools, analogous to Claude Code's `Edit|Write|MultiEdit`
+// matcher. Current OpenCode may use `apply_patch` for file edits.
+const FILE_TOOLS = new Set(["apply_patch", "edit", "write"]);
+
+const HOOK_SCRIPT = ".claude/hooks/precommit-validate.sh";
+
+export const PrecommitValidatePlugin: Plugin = async ({ $, client, directory, worktree }) => {
+  const root = worktree || directory;
+  const script = join(root, HOOK_SCRIPT);
+
+  const hooks: Hooks = {
+    "tool.execute.after": async (input, output) => {
+      if (!FILE_TOOLS.has(input.tool)) return;
+      // Inert when the shared script is absent (e.g. loaded in another repo).
+      if (!existsSync(script)) return;
+
+      const filePaths = new Set<string>();
+      const filePath: string | undefined = input.args?.filePath;
+      if (filePath) filePaths.add(filePath);
+
+      for (const file of output.metadata?.files ?? []) {
+        if (typeof file.filePath === "string") filePaths.add(file.filePath);
+      }
+
+      if (filePaths.size === 0) return;
+
+      const reports: string[] = [];
+
+      for (const filePath of filePaths) {
+        const absolute = isAbsolute(filePath) ? filePath : resolve(root, filePath);
+
+        // Same JSON shape Claude Code's PostToolUse hook delivers on stdin. The
+        // script itself decides whether the file lives inside the repo.
+        const payload = JSON.stringify({ tool_input: { file_path: absolute } });
+
+        const result = await $`printf '%s' ${payload} | ${script}`
+          .cwd(root)
+          .nothrow()
+          .quiet();
+
+        if (result.exitCode === 0) continue; // clean / no-op
+
+        const report =
+          result.stderr.toString().trim() || result.stdout.toString().trim();
+
+        if (result.exitCode === 2) {
+          // Blocking: pre-commit reported issues. Surface them to the model by
+          // appending to the tool output, the OpenCode equivalent of feeding the
+          // hook's stderr back to Claude Code on exit 2.
+          if (report) reports.push(report);
+          continue;
+        }
+
+        // Non-blocking error (e.g. exit 1 = mise not on PATH). Not something the
+        // model can act on, so log it for the user instead of polluting the turn.
+        await client.app.log({
+          body: {
+            service: "precommit-validate",
+            level: "warn",
+            message: report || `pre-commit validation hook exited ${result.exitCode}`,
+          },
+        });
+      }
+
+      if (reports.length > 0) {
+        output.output += `\n\n<pre-commit-validation>\n${reports.join("\n\n")}\n</pre-commit-validation>`;
+      }
+    },
+  };
+
+  return hooks;
+};

data/.pre-commit-config.yaml

@@ -15,7 +15,7 @@ repos:
       - id: check-json
       - id: detect-private-key
       - id: mixed-line-ending
-        args: ["--fix=lf"]
+        args: [--fix=lf]
       - id: no-commit-to-branch
         args: [--branch, main]
       - id: pretty-format-json
@@ -36,3 +36,4 @@ repos:
       - id: gitleaks  #  Detect hardcoded secrets using Gitleaks
       - id: editorconfig  # Validate text files against .editorconfig
       - id: yamllint  # Validate YAML files using yamllint
+      - id: ensure-claude-md

data/.rubocop_todo.yml

@@ -151,12 +151,6 @@ Lint/SymbolConversion:
     - 'spec/labkit/logging/json_logger_spec.rb'
     - 'spec/support/tracing/shared_examples.rb'
 
-# Offense count: 1
-# Configuration parameters: Methods.
-Lint/UnexpectedBlockArity:
-  Exclude:
-    - 'tools/update-changelog.rb'
-
 # Offense count: 41
 # This cop supports safe autocorrection (--autocorrect).
 # Configuration parameters: AutoCorrect, AllowUnusedKeywordArguments, IgnoreEmptyMethods, IgnoreNotImplementedMethods, NotImplementedExceptions.
@@ -196,13 +190,6 @@ Naming/RescuedExceptionsVariableName:
   Exclude:
     - 'lib/labkit/logging/grpc/server_interceptor.rb'
 
-# Offense count: 1
-# This cop supports safe autocorrection (--autocorrect).
-# Configuration parameters: EnabledForFlattenWithoutParams.
-Performance/FlatMap:
-  Exclude:
-    - 'tools/update-changelog.rb'
-
 # Offense count: 1
 Performance/MethodObjectAsBlock:
   Exclude:
@@ -402,7 +389,7 @@ Style/FileNull:
     - 'spec/labkit/middleware/sidekiq/user_experience_sli/server_spec.rb'
     - 'spec/spec_helper.rb'
 
-# Offense count: 8
+# Offense count: 7
 # This cop supports unsafe autocorrection (--autocorrect-all).
 # Configuration parameters: EnforcedStyle.
 # SupportedStyles: always, always_true, never
@@ -415,7 +402,6 @@ Style/FrozenStringLiteralComment:
     - 'spec/labkit/tracing/rails/active_support/cache_read_instrumenter_spec.rb'
     - 'spec/labkit/tracing/rails/active_support/cache_write_instrumenter_spec.rb'
     - 'spec/support/grpc_service/test_services_pb.rb'
-    - 'tools/update-changelog.rb'
 
 # Offense count: 2
 # This cop supports unsafe autocorrection (--autocorrect-all).
@@ -539,7 +525,7 @@ Style/StringConcatenation:
     - 'lib/labkit/tracing/jaeger_factory.rb'
     - 'lib/labkit/tracing/redis/redis_interceptor_helper.rb'
 
-# Offense count: 6
+# Offense count: 4
 # This cop supports safe autocorrection (--autocorrect).
 # Configuration parameters: EnforcedStyle.
 # SupportedStyles: single_quotes, double_quotes
@@ -549,7 +535,6 @@ Style/StringLiteralsInInterpolation:
     - 'lib/labkit/tracing/grpc/server_interceptor.rb'
     - 'lib/labkit/tracing/jaeger_factory.rb'
     - 'spec/labkit/logging/json_logger_spec.rb'
-    - 'tools/update-changelog.rb'
 
 # Offense count: 10
 # This cop supports safe autocorrection (--autocorrect).

data/AGENTS.md

@@ -1,3 +1,4 @@
+<<<<<<< before updating
 # AGENTS.md
 
 Instructions for AI agents and automated tooling working in this repository.
@@ -134,3 +135,39 @@ When a change does not fit one layer clearly, say so in the MR instead of pickin
   Mention the sync agent on the review thread to have it draft the scenario MR; if it cannot, open a labkit-spec issue and link it from the thread.
 - Never edit Lua scripts, key construction, header names, metric names, or log field names to fix a Ruby-only bug.
   If a fix seems to need that, it is a contract change.
+=======
+# Agent guidelines
+
+This project uses [Conventional Commits](https://www.conventionalcommits.org/).
+Commit messages drive automated [semantic releases](https://semantic-release.gitbook.io/)
+(see `.releaserc.json`), so use `feat:`, `fix:`, etc. prefixes to ensure the
+correct version bump and changelog entry.
+
+## AI-authored GitLab comments
+
+Wrap the full body of any comment, note, or reply you post to GitLab (issues,
+merge requests, epics — via `glab`/`glab api`) in `<:robot:>` / `</:robot:>`
+tags (GitLab emoji shortcode, renders as 🤖), so readers can tell at a glance
+that it's AI-generated:
+
+```
+<:robot:>
+
+...full comment body...
+
+</:robot:>
+```
+
+This applies to newly posted comments. It does not apply to code, commit
+messages, or MR/issue descriptions unless asked.
+
+<!--
+####################################################################
+#   🌊✨ PLEASE ADD PROJECT SPECIFIC RULES BELOW THIS LINE ✨🌊   #
+#   The section above is managed by the common-template-copier     #
+#   template and is updated automatically on `copier update`.      #
+#   Add your project-specific instructions below this line so      #
+#   they are preserved when the template is updated.               #
+####################################################################
+-->
+>>>>>>> after updating

data/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

data/Gemfile

@@ -3,3 +3,8 @@
 source "https://rubygems.org"
 
 gemspec
+
+# Exports RSpec results to the DX Observer when GLCI_OBSERVER_AUTH_TOKEN is set.
+# Exporter source: https://gitlab.com/gitlab-org/quality/analytics/test-metrics-exporters
+# Owned by: @gitlab-org/quality/analytics (group::development analytics)
+gem 'gitlab-rspec-metrics-exporter', '~> 0.2', groups: [:development, :test]

data/README.md

@@ -80,27 +80,14 @@ pass.
 
 Please also review the [development section of the LabKit (go) README](https://gitlab.com/gitlab-org/labkit#developing-labkit) for details of the LabKit architectural philosophy.
 
-To work on some of the scripts we use for releasing a new version,
-make sure to add a new `.env.sh`.
-
-```console
-cp .env.example.sh .env.sh`
-```
-
-Inside `.env.sh`, add a personal acccess token for the `CHANGELOG_GITLAB_TOKEN`
-environment variable. Next source the file:
-
-```console
-. .env.sh
-```
-
 ### Releasing a new version
 
-Releasing a new version can be done by pushing a new tag, or creating
-it from the
-[interface](https://gitlab.com/gitlab-org/labkit-ruby/-/tags).
-
-A new changelog will automatically be added to the release on Gitlab.
+Releases are cut automatically by
+[semantic-release](https://github.com/semantic-release/semantic-release)
+when changes are merged to `master` or to an `N-N-stable` branch. The
+[Conventional Commits](https://www.conventionalcommits.org/) type of each
+commit decides the version bump (see [AGENTS.md](AGENTS.md)), and the
+release notes are generated from those commit messages.
 
 The new version will automatically be published to `gitlab-labkit` on
 [rubygems](https://rubygems.org/gems/gitlab-labkit) when the pipeline

data/lib/labkit/json_schema/README.md

@@ -66,7 +66,7 @@ Labkit::JsonSchema::RefResolver.cache.clear
 
 ## Use Case Example
 
-The `RefResolver` is used in the User Experience SLI Registry [lib/labkit/user_experience_sli/registry.rb](lib/labkit/user_experience_sli/registry.rb) to validate user experience definitions against a JSON schema.
+The `RefResolver` is used in the User Experience SLI Registry [lib/labkit/user_experience_sli/registry.rb](../user_experience_sli/registry.rb) to validate user experience definitions against a JSON schema.
 
 ## Implementation Details
 

data/lib/labkit/rspec/matchers/user_experience_matchers.rb

@@ -173,7 +173,7 @@ RSpec::Matchers.define :complete_user_experience do |user_experience_id, error:
     "Failed to complete user experience '#{user_experience_id}':\n" \
       "expected checkpoint='end' counter to increase by 1, but increased by #{@checkpoint_change}\n" \
       "expected total='error: #{error}' counter to increase by 1, but increased by #{@total_change}\n" \
-      "expected apdex='success: #{success}' counter to increase by 1, but increased by #{@apdex_change}"
+      "expected apdex='success: #{success}' counter to increase by #{error ? 0 : 1}, but increased by #{@apdex_change}"
   end
 
   match_when_negated do |actual|
@@ -192,7 +192,7 @@ RSpec::Matchers.define :complete_user_experience do |user_experience_id, error:
     @total_change = total_after - total_before
     @apdex_change = apdex_after - apdex_before
 
-    @checkpoint_change.zero? && @total_change.zero? && @apdex_change == (error ? 1 : 0)
+    @checkpoint_change.zero? && @total_change.zero? && @apdex_change.zero?
   end
 
   failure_message_when_negated do

data/performance.yml

@@ -0,0 +1,70 @@
+# Performance contract for labkit-ruby
+# https://handbook.gitlab.com/handbook/engineering/testing/performance-contracts/
+#
+# This file is the single entry point for performance contract tooling.
+# Customize the sections relevant to your service and remove the rest.
+# Schema reference: https://handbook.gitlab.com/handbook/engineering/testing/performance-contracts/#schema-definition
+
+version: "1.0"
+service:
+  name: "labkit-ruby"
+  description: "Performance contract for labkit-ruby"
+
+# ---------------------------------------------------------------------------
+# Frontend / UI contracts (SiteSpeed)
+# Uncomment and configure if this service has a frontend component.
+# Budget files live in the sitespeed-measurement-setup submodule.
+# ---------------------------------------------------------------------------
+# frontend:
+#   enabled: true
+#   budgets:
+#     production: testrunner/sitespeed-measurement-setup/performance/budgets/environments/production.json
+#     staging:    testrunner/sitespeed-measurement-setup/performance/budgets/environments/staging.json
+#     mr:         testrunner/sitespeed-measurement-setup/performance/budgets/environments/mr.json
+#   teams:
+#     labkit-ruby:
+#       url_dir: testrunner/sitespeed-measurement-setup/gitlab/desktop/urls
+#       budget:  testrunner/sitespeed-measurement-setup/performance/budgets/teams/labkit-ruby.json
+#   default_budget: mr
+
+# ---------------------------------------------------------------------------
+# Backend / Service contracts (k6 / CPT)
+# Define endpoint categories with latency and error-rate targets.
+# Choose a tier as a starting point, then tune from baseline data.
+#
+# Tier 1 (fast reads):  p95=100ms,  p99=250ms,  error_rate=0.001
+# Tier 2 (std reads):   p95=500ms,  p99=1000ms, error_rate=0.005
+# Tier 3 (writes):      p95=1500ms, p99=3000ms, error_rate=0.01
+# Tier 4 (git ops):     p95=5000ms, p99=10000ms,error_rate=0.001
+# ---------------------------------------------------------------------------
+# endpoints:
+#   fast_reads:
+#     description: >
+#       Single item lookup by ID. Simulates one indexed DB read.
+#     routes:
+#       - "GET /api/v1/items/{id}"
+#     metrics:
+#       latency_p95_ms: 100
+#       latency_p99_ms: 250
+#       error_rate_threshold: 0.001
+
+# ---------------------------------------------------------------------------
+# Resource budgets (informational; enforcement planned for a future iteration)
+# ---------------------------------------------------------------------------
+# resources:
+#   memory_limit_mb: 256
+#   cpu_limit_cores: 0.5
+#   connection_pool_max: 10
+
+# ---------------------------------------------------------------------------
+# SLI mapping -- links contract endpoints to Prometheus metrics emitted by
+# LabKit v2. Fill in once your service is instrumented.
+# ---------------------------------------------------------------------------
+# sli_mapping:
+#   metrics_namespace: gitlab
+#   component: labkit-ruby
+#   fast_reads:
+#     requests_total_metric: gitlab_http_requests_total
+#     duration_metric: gitlab_http_request_duration_seconds
+#     endpoint_id_label: "GET /api/v1/items/{id}"
+#     feature_category_label: labkit_ruby

data/scripts/prepare-dev-env.sh

@@ -21,6 +21,28 @@ warn() {
   echo >&2 -e "Recommended reading: https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/docs/developer-setup.md"
 }
 
+# `mise plugins update` contacts GitHub for every registered plugin: slow, and
+# it adds up when many vendored copies of this script run across many projects
+# on the same machine. Throttle it to once a day using a stamp file in the
+# user's cache directory, deliberately outside the project so that the throttle
+# is shared by every project that vendors this script.
+mise_plugins_update() {
+  local stamp_dir="${XDG_CACHE_HOME:-${HOME:-}/.cache}/common-template-copier"
+  local stamp_file="${stamp_dir}/mise-plugins-update"
+
+  # `find -mtime -1` rather than `stat`, which is spelled differently on
+  # GNU/BSD. It prints nothing when the stamp is missing or over a day old.
+  if [[ -z ${FORCE_MISE_PLUGINS_UPDATE-} ]] && [[ -n $(find "$stamp_file" -mtime -1 2>/dev/null) ]]; then
+    echo >&2 "skipping 'mise plugins update' (ran in the last 24h; set FORCE_MISE_PLUGINS_UPDATE=1 to force)"
+    return 0
+  fi
+
+  mise plugins update -q
+
+  # Best effort: a machine without a writable cache dir just updates every time.
+  mkdir -p "$stamp_dir" && touch "$stamp_file" || true
+}
+
 if command -v mise >/dev/null; then
   echo >&2 -e "mise installed..."
 elif command -v rtx >/dev/null; then
@@ -53,8 +75,8 @@ fi
 
 # install mise/asdf dependencies
 echo "installing required plugins with mise install.."
-mise plugins update -q
 mise trust --yes
+mise_plugins_update
 mise install
 
 # set PROMPT_COMMAND to empty value for mise if unset

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-labkit
 version: !ruby/object:Gem::Version
-  version: 5.6.0
+  version: 5.6.1
 platform: ruby
 authors:
 - Andrew Newdigate
@@ -562,9 +562,10 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".claude/hooks/precommit-validate.sh"
+- ".claude/settings.json"
 - ".copier-answers.yml"
 - ".editorconfig"
-- ".env.example.sh"
 - ".gitignore"
 - ".gitlab-ci-asdf-versions.yml"
 - ".gitlab-ci-other-versions.yml"
@@ -574,6 +575,7 @@ files:
 - ".gitlab/merge_request_templates/default.md"
 - ".gitleaks.toml"
 - ".mise.toml"
+- ".opencode/plugins/precommit-validate.ts"
 - ".pre-commit-config.yaml"
 - ".releaserc.json"
 - ".rspec"
@@ -583,6 +585,7 @@ files:
 - ".tool-versions"
 - ".yamllint.yaml"
 - AGENTS.md
+- CLAUDE.md
 - CODEOWNERS
 - CONTRIBUTING.md
 - Dangerfile
@@ -712,6 +715,7 @@ files:
 - lib/labkit/user_experience_sli/experience.rb
 - lib/labkit/user_experience_sli/null.rb
 - lib/labkit/user_experience_sli/registry.rb
+- performance.yml
 - renovate.json
 - scripts/prepare-dev-env.sh
 - scripts/update-asdf-version-variables.sh

data/.env.example.sh

@@ -1,7 +0,0 @@
-export CI_PROJECT_ID=10947578
-export CI_API_V4_URL="https://gitlab.com/api/v4"
-export CI_PROJECT_URL="https://gitlab.com/gitlab-org/ruby/gems/labkit-ruby"
-# Don't keep secrets in plaintext files. Use a keyring or 1password to load
-# it instead and export it as an env var.
-token=$(load-your-token)
-export GITLAB_TOKEN=$token