feat: enforce R-FC-014 (recently-Done item without Cycle -> current cycle) hourly

[BigLep]

Summary

• Adds R-FC-014: any issue/PR in "🎉 Done", updated in the last 3 days, with no Cycle gets the current cycle set, mechanically enforced hourly like R-FC-012/013.
• This codifies the "recently completed items need a Cycle" check that previously only existed as a manual LLM-sweep step (foc-board-rules/sweep-playbook.md's "Recently Done" stage), not as a numbered, automated rule — R-FC-012 explicitly excludes Done items, so nothing mechanical covered this gap before.
• DoneCycleRule subclasses CycleRule, reusing its apply_one (including the "don't re-add a cycle a human cleared" mutation-log guard) and select()'s query shape, overriding only the _STATUS_FILTER class attribute (status:"🎉 Done" vs. R-FC-012's -status:"🎉 Done") — both share the same updated:>@today-3d window.
• Registered in registry.py; documented in foc-board-rules/field-completeness.md and foc-mechanical-rules/README.md (rules table + API-call-pattern table).

Test plan

• uv run pytest -q in foc-mechanical-rules/ (63 passed)
• Added DoneCycleRule tests: select() query shape, apply_one reuse, Rule subclass check
• Updated test_cli.py's full-rule-set assertion to include R-FC-014

🤖 Generated with Claude Code

https://claude.ai/code/session_01AkjQydxZny5DgxZi7BVmU2

[Copilot]

Pull request overview

This PR adds a new mechanical field-completeness rule (R-FC-014) to automatically assign the current Cycle to items that are in 🎉 Done, have no Cycle, and were updated within the last day, closing a previously manual “recently done” gap in Cycle hygiene.

Changes:

• Implement DoneCycleRule (R-FC-014) by subclassing CycleRule and overriding only select() to target Done items with a 1-day recency window.
• Register the new rule in the default rule set and update CLI tests to include it.
• Document R-FC-014 in the mechanical rules README and the board rule canon (field-completeness.md), including the API call pattern table.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
foc-mechanical-rules/foc_mechanical_rules/rules/cycle.py	Adds DoneCycleRule to reuse Cycle assignment logic with a Done-scoped query.
foc-mechanical-rules/foc_mechanical_rules/registry.py	Registers R-FC-014 in the default rule set.
foc-mechanical-rules/tests/test_cycle_rule.py	Adds unit tests for R-FC-014 query shape and apply_one reuse.
foc-mechanical-rules/tests/test_cli.py	Updates the “run all rules” assertion to include R-FC-014.
foc-mechanical-rules/README.md	Documents the new rule and its API call pattern.
foc-board-rules/field-completeness.md	Adds the canonical prose definition for R-FC-014.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Suppressed comments (2)

foc-mechanical-rules/README.md:53

• This table note says DoneCycleRule "overrid[es] only" _STATUS_FILTER, but the subclass also changes metadata (id/doc_url). Consider rewording to avoid a literally incorrect claim while keeping the point that behavior is reused.

| R-FC-014 (cycle) | 1 paginated board query (Done items only, same 3-day window as R-FC-012) | 1 GraphQL query (iterations, shared helper with R-FC-012) | none | Batched, same mechanism as R-FC-012 (`DoneCycleRule` subclasses `CycleRule`, overriding only the `_STATUS_FILTER` class attribute) |

foc-mechanical-rules/foc_mechanical_rules/rules/cycle.py:293

• DoneCycleRule's docstring says it targets items that "just moved to Done", but the selection is based on current status + updated:... and doesn't actually observe the status transition. Consider rewording to avoid implying a capability the query doesn't have.

    """Same "no cycle -> assign current cycle" logic as R-FC-012, scoped to
    items that just moved to Done instead of items that are still active.