Tighten Go Logger workflow scope and validation behavior

[Copilot]

The Go Logger Enhancement workflow was over-exploring the repository, drifting into unrelated baseline failures, and expanding scope beyond the intended single-file logging change. This updates the workflow prompt so runs stay narrow, cache-aware, and resilient to unrelated repo breakage.

• Scope control

  • Limit candidate exploration to at most 3 files before selecting a target.
  • Stop searching once 1 strong candidate is identified.
  • Require skipping files already recorded in cache-memory.

• Validation behavior

  • Instruct the agent to detect pre-existing repo-wide failures before validating its change.
  • Prefer package-scoped go test / go vet first for the edited file’s package.
  • Allow repo-wide checks only when the baseline is clean or the failure is clearly related to the edited file.

• Guardrails against unrelated fixes

  • Explicitly forbid widening scope to “fix the build” in untouched files.
  • Clarify that unrelated baseline failures should be reported as blockers, not folded into the PR.

• Compiled workflow update

  • Regenerate go-logger.lock.yml to reflect the prompt changes.

Example of the new validation guidance:

1. Record whether repo-wide verification is already broken before your edit.
2. Run targeted validation for the package you changed first:
   go test ./path/to/package
   go vet ./path/to/package
3. Run repo-wide tests only when they were green before your change, or when a failure clearly points to your edited file.

[Copilot]

Pull request overview

This PR tightens the Go Logger Enhancement agent workflow guidance to reduce unnecessary repository exploration, avoid scope creep into unrelated baseline failures, and introduce a more resilient validation sequence (package-scoped checks first), then regenerates the compiled lock workflow accordingly.

Changes:

• Add explicit guardrails to cap candidate exploration and stop searching once a strong target file is found (while excluding cache-memory processed files).
• Update validation guidance to detect pre-existing repo-wide failures and prefer package-scoped go test/go vet before broader checks.
• Regenerate .github/workflows/go-logger.lock.yml to reflect the updated prompt/compiler output.

Show a summary per file

File	Description
.github/workflows/go-logger.md	Tightens agent prompt constraints (exploration cap, no unrelated fixes) and refines validation guidance toward package-scoped checks first.
.github/workflows/go-logger.lock.yml	Regenerated compiled workflow reflecting the prompt changes and updated compiler/runtime wiring.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 7

[lpcox]

@copilot address review feedback to the .md file but ignore feedback on compiled .lock.yml files

[Copilot]

@copilot address review feedback to the .md file but ignore feedback on compiled .lock.yml files

Done. Updated the validation step in go-logger.md to replace the ./path/to/package placeholder with an explanation of how to derive the correct path from the edited file's directory, including a concrete example (internal/launcher/pool.go → ./internal/launcher). Lock file feedback ignored as requested.