feat: add spec traceability via t.Specification() and JUnit XML output

[aaron-zeisler]

Summary

Add first-class specification traceability to the test harness, inspired by the OpenFeature @Specification (Java) / [Specification] (.NET) pattern adapted for Go.

Framework changes (4 commits)

• SpecReference type and T.Specification(specID, number, summary) method on ldtest.T
• TestResult.Specifications field, propagated from T on test completion
• JUnit XML output: spec references surfaced as <properties> on <testcase> elements
• YAML schema: TestSpecReference type and specifications field on EvalTestSuite, automatically propagated to t.Specification() by the parameterized test runner

Test annotations (13 commits)

• All 17 specs annotated with t.Specification() calls (Go) or structured specifications fields (YAML)
• 5 specs renumbered to match latest sdk-specs main:
  • HOOK: gap-closing (3 reqs)
  • AUTOENVATTR: section shift starting at 1.2.3
  • DATASYSTEM v2: gap at old 1.2.4 closed
  • FLGEA: major renumbering in section 1.6
  • CONTEXT: complete rewrite with new numbering
• 2 PS annotations retained as comments on helper functions that don't accept *ldtest.T

Files changed

• framework/ldtest/: 4 files (new spec.go, modified test_scope.go, result.go, junit_test_logger.go)
• data/testmodel/eval.go: YAML schema extension
• sdktests/: 16 Go files
• data/data-files/: 30 YAML files

Test plan

• go build ./... passes
• gofmt clean
• CI lint passes
• Spot-check JUnit XML output contains <properties> with spec references (verified locally)
• Verify YAML specifications fields parse correctly (verified locally)

via LD Research 🤖

---

Note

Medium Risk
Mostly additive test-harness metadata, but it changes TestResult/JUnit XML output shape (adds <testcase><properties>), which could affect downstream CI/report parsers and any code assuming the previous structs.

Overview
Adds first-class specification traceability to the harness via t.Specification(specID, number, summary) and a new SpecReference type, capturing these references on TestResult at completion.

Surfaces recorded spec references in JUnit XML by emitting them as <property name="specification" ...> entries under each <testcase>.

Extends parameterized eval YAML suites with a specifications field (EvalTestSuite.Specifications) and propagates those references into the runtime t.Specification() calls; updates many Go/YAML tests to include these spec annotations and adds an AGENTS.md guide describing the conventions.

^{Reviewed by Cursor Bugbot for commit f57b4d1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 55149b3. Configure here.}