What Does This Do

Make strict trace writing mandatory for instrumentation tests.

• Remove InstrumentationSpecification.useStrictTraceWrites().
• Remove the JUnit InstrumentationTestConfig.strictTraceWrites(...) option.
• Configure both test harnesses with strict trace writes unconditionally.
• Remove the now-unnecessary strictness flag from the span and request-context decorators.
• Document how unresolved continuation failures should be handled.
• Update the continuation-leakage skill with the same policy.

Motivation

Disabling strict trace writes allowed incomplete traces and continuation lifecycle problems to be hidden. Instrumentation tests should expose those problems so they can be diagnosed and fixed.

If a continuation problem cannot be fixed immediately, the test should be quarantined with @Flaky and a useful reason or tracked issue.

@TrackScopeContinuations(enabled = false, reason = "...") remains available only for a proven incompatibility with the diagnostic itself. It does not disable strict trace writes.

  flowchart TD
      A[Instrumentation test] --> B[Strict trace writes enabled]
      B --> C{Continuation failure?}

      C -->|No| D[Test passes]
      C -->|Real lifecycle problem| E[Fix ownership or cleanup]
      E --> D
      E -->|Cannot fix immediately| F["@Flaky with reason or issue"]

      C -->|Diagnostic incompatibility| G["Disable tracking narrowly<br/>with documented reason"]
      G --> H[Strict trace writes remain enabled]

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]