Prevent false cache_memory_miss failures in Repository Quality Improver

[Copilot]

Repository Quality Improver runs were being flagged as failed even when the agent completed successfully, because a first-run cache miss was reported as missing_data (cache_memory_miss). This created noisy failure issues on main despite cache-memory being enabled.

• Workflow prompt update (.github/workflows/repository-quality-improver.md)

  • Added explicit guidance in Phase 0.1 (Load Focus Area History) that missing history.json is an expected first-run condition.
  • Instructed the agent to initialize empty in-memory history and continue instead of emitting missing_data.
  • Clarified that missing_data should only be used when required analysis data is genuinely unavailable from repo/tools.

• Behavioral intent

  • Distinguishes expected cache initialization from actual missing data conditions.
  • Reduces false-positive workflow failure handling for this workflow.

If `history.json` does not exist, treat it as an expected first-run cache miss:
- Initialize an empty in-memory history object and continue.
- **Do not** call `missing_data` for cache-memory misses.
- Only use `missing_data` when required analysis data cannot be obtained...

[Copilot]

Pull request overview

Updates the Repository Quality Improver agentic workflow prompt to treat a missing history.json in cache-memory as an expected first-run condition, avoiding false missing_data / cache_memory_miss failures.

Changes:

• Clarifies that absence of history.json should initialize empty history and continue.
• Explicitly instructs the agent not to emit missing_data for cache-memory misses, reserving it for genuinely unavailable repo/tool data.

Show a summary per file

File	Description
.github/workflows/repository-quality-improver.md	Adds first-run cache-miss guidance for history.json to reduce noisy failure handling.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 1