[routine:archivist] Evaluate Task 2 (Mintlify coverage) hit rate after 30 days

[JacobPEvans-personal]

Background

PR #20 rewrote Archivist as two tasks rotating daily:

• Task 1 (readme-quality): scores READMEs, opens PR fixing lowest-scorer
• Task 2 (mintlify-coverage): checks JacobPEvans/docs navigation against repo list, files issue if uncovered

Reviewer feedback flagged this as "two routines in a trench coat" — different output types (PR vs issue), different target repo, different state semantics. Accepted as compromise for the initial deploy; revisit data-driven.

Request

After 30 days of Archivist runs (target: 2026-06-25 or later), inspect the archivist-state gist run_log:

• How many readme-quality runs produced a PR vs no-op?
• How many mintlify-coverage runs produced an issue vs no-op?

If mintlify-coverage hit rate is low (most runs no-op because the docs site stays in sync), fold Task 2 into Morning Briefing as a weekly section and rename Archivist back to single-purpose README quality.

If hit rate is reasonable (≥1 issue per 7 days on average), keep the two-task structure.

Why now

Architecture-critic feedback acknowledged the compromise; this issue commits to revisiting it once we have data.

Provenance

• Filed by: Routine rewrite implementation (PR feat(routines): rewrite six new routines, ground-truthed and hardened #20).
• Why this issue: Follow-up harden(custodian): block Write/Edit + move deploy earlier #5 from the PR plan.
• Label: cloud-routine