docs(changelog): add plan action arguments upsert fix to [Unreleased]

Document the fix from PR #4197: plan use no longer crashes with
UNIQUE constraint violation when action arguments are already registered.

ISSUES CLOSED: #4174

CHANGELOG.md

@@ -202,6 +202,17 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - **`product-builder` Missing Supervisors**: Added missing `pr-fix-pool-supervisor` and
   `pr-merge-pool-supervisor` to the product-builder's supervisor launch list (18 total
   supervisors). Updated all numeric references, pre-flight checklists, and validation logic.
+- **Plan action arguments UNIQUE constraint**: `agents plan use` no longer crashes with
+  `sqlite3.IntegrityError: UNIQUE constraint failed: action_arguments.action_name, name`
+  when an action has arguments already registered via `action create`. Root cause was
+  `ActionRepository.update()` using SQLAlchemy's `.clear()` + `.append()` pattern, which
+  deferred the DELETE and processed the INSERT first. Fixed by using an explicit upsert
+  (delete-then-insert) strategy. (#4174)
+
+- `ActionRepository.update()` now uses explicit bulk `sa_delete()` + `session.flush()`
+  before re-inserting child rows for `action_arguments` and `action_invariants`, fixing
+  a `sqlite3.IntegrityError: UNIQUE constraint failed` crash when `agents plan use` was
+  called on an action that already had arguments registered via `action create`. (#4197)
 
 ---
 

docs/development/automation-tracking.md

@@ -360,6 +360,12 @@ Every agent that creates tracking issues must implement:
 - **Content**: Build orchestration status, worker pool health
 - **Cleanup**: Handled by automation-tracking-manager
 
+#### docs-writer
+- **Cycle Frequency**: Documentation reports every 10 cycles (~3.3 hours)
+- **Issue Types**: Documentation Report
+- **Content**: Docs created/updated/skipped, commit hash, milestone coverage
+- **Cleanup**: Deletes previous documentation report issues
+
 ## Searching and Filtering
 
 ### Finding Tracking Issues

docs/development/docs-writer.md

@@ -5,7 +5,7 @@
 **Reporting Interval**: Every 10 cycles (~3.3 hours)
 
 The `docs-writer` agent is a continuous documentation monitoring and generation
-service.  It runs in an isolated clone of the repository, polls for merged code
+service. It runs in an isolated clone of the repository, polls for merged code
 and milestone completions, and keeps project documentation current without human
 intervention.
 
@@ -35,8 +35,8 @@ cycle = 0
 LOOP:
     cycle += 1
 
-    # Create tracking issue every 10 cycles
-    if cycle % 10 == 0:
+    # Create tracking issue on first cycle and then every 10 cycles
+    if cycle == 1 or cycle % 10 == 0:
         automation-tracking-manager: CREATE_TRACKING_ISSUE
           agent_prefix: AUTO-DOCS
           tracking_type: Documentation Report
@@ -75,15 +75,23 @@ via the `automation-tracking-manager` subagent.
 Title: [AUTO-DOCS] Documentation Report (Cycle N)
 ```
 
-**Default label** (applied automatically by the manager):
+**Required labels** (all four must be applied):
 
 | Label | Purpose |
 |-------|---------|
 | `Automation Tracking` | Enables system-watchdog health monitoring |
+| `Type/Automation` | Marks as automation-related |
+| `State/In Progress` | Indicates agent is actively running |
+| `Priority/Medium` | Default priority |
 
-Additional labels (for example `Type/Automation`, `State/In Progress`, or
-`Priority/Medium`) can be added manually when teams need extra filtering, but
-they are optional and not applied by the manager today.
+Tracking issue bodies MUST include the standard automation tracking header with
+the reporting interval declaration, for example:
+
+```
+**Reporting Interval**: Every 10 cycles (~3.3 hours) (Next report expected: <timestamp>)
+```
+See [Automation Tracking System](automation-tracking.md#common-header-format) for
+the complete required structure.
 
 ### Cleanup Protocol
 
@@ -92,7 +100,7 @@ The `automation-tracking-manager` handles all cleanup:
 1. Finds the previous open `[AUTO-DOCS] Documentation Report (Cycle N)` issue
 2. Posts a closure comment
 3. Closes the issue
-4. Creates the new tracking issue with the `Automation Tracking` label
+4. Creates the new tracking issue with the four required labels
 
 Announcement issues (`[AUTO-DOCS] Announce: …`) are **never** deleted.
 
@@ -113,8 +121,10 @@ All documentation produced by this agent follows the project's
 ## Clone Isolation
 
 The agent always works in an isolated clone at `/tmp/docs-writer-<instance-id>/`.
-It never modifies files in `/app` or any shared directory.  The clone is
-deleted on exit (including on error).
+The instance identifier MUST be generated with a cryptographically strong
+mechanism such as `uuid.uuid4()` or `secrets.token_hex(8)` to avoid collisions
+or predictable directory names. It never modifies files in `/app` or any shared
+directory. The clone is deleted on exit (including on error).
 
 Push conflicts are resolved with `git pull --rebase origin master && git push`.
 After five consecutive push failures the clone is deleted and re-cloned fresh.
@@ -122,6 +132,15 @@ After five consecutive push failures the clone is deleted and re-cloned fresh.
 Since `master` is a protected branch, all documentation changes are submitted
 as pull requests from a feature branch.
 
+All Git authentication must rely on credential helpers or `GIT_ASKPASS`. The
+agent must not embed personal access tokens in remote URLs, because git will
+echo failing URLs (including credentials) to stderr when operations fail.
+
+When interacting with the Forgejo API, the agent MUST handle `HTTP 429` rate
+limit responses by backing off exponentially (starting at 60 seconds, capped at
+the 20 minute cycle delay) before retrying the request. This prevents tight
+retry loops during temporary throttling events.
+
 ---
 
 ## Related Documentation

docs/timeline.md

@@ -10,26 +10,25 @@ The following chart shows all 29 epics across 9 legendary workstreams, 7 milesto
 @startgantt
 
 title CleverAgents Core — Epic-Level Project Schedule
-footer Generated 2026-04-10 | 29 Epics | 9 Legendaries | 7 Milestones | 6 Developers | ~1650 SP | ~25 open bugs | 225 open PRs | Session 4 active
+footer Generated 2026-04-12 | 29 Epics | 9 Legendaries | 7 Milestones | 6 Developers | ~1650 SP | ~3 open bugs | 257 open PRs | Session 4 active
 
 Project starts 2026-02-03
 saturday are closed
 sunday are closed
 printscale weekly zoom 2
 
-today is 2026-04-10
+today is 2026-04-12
 today is colored in #FF6666
 
 ' ================================================================
-'  GANTT CHART UPDATE LOG (Day 100 — 2026-04-10)
-'  Changes: Day 100 refresh (cycle 2). Session 4 active (issue #4799, 32 workers).
-'  Open PRs: 221→225 (new PRs opened by agents). Open bugs: ~25 (Type/Bug label).
-'  M3 32% (249/770, scope expanded!), M4 49% (108/220), M5 43% (133/313),
-'  M6 18% (197/1085, scope massively expanded!), M7 38% (150/400),
-'  M8 45% (425/944), M9 28% (131/475).
-'  Massive scope expansion across all milestones since Day 98.
-'  pr-merge-pool-supervisor added as 17th supervisor. PR review reduced to 1 approval.
-'  git worktree sandbox merged. ACMS indexing pipeline wired.
+'  GANTT CHART UPDATE LOG (Day 102 — 2026-04-12)
+'  Changes: Day 102 refresh (cycle 1). Session 4 active (issue #4799, 32 workers).
+'  Open PRs: 225→257 (+32 new PRs). Open bugs: ~25→3 (Type/Bug label, major bug-fix wave).
+'  M3 28% (262/948, scope expanded 770→948), M4 46% (108/233), M5 40% (137/345),
+'  M6 17% (201/1181, scope expanded 1085→1181), M7 35% (152/433),
+'  M8 45% (427/956), M9 27% (132/489). v3.9.0 milestone added (13 open, 4 closed).
+'  Significant bug-fix wave: open bugs dropped from ~25 to 3.
+'  Open PRs grew from 225 to 257 (+32 new agent-driven PRs).
 ' ================================================================
 
 <style>
@@ -231,7 +230,7 @@ ganttDiagram {
 
 [Decisions + Validations M3 (#357)] as [M3] on {Luis} {Hamza} {Brent} {Jeff} requires 4 days
 [M3] starts at [M2]'s end
-[M3] is 65% completed
+[M3] is 28% completed
 [M3] is colored in LightSkyBlue/SteelBlue
 
 ' ── v3.3.0 MILESTONE ─────────────────────────────────────────
@@ -252,7 +251,7 @@ ganttDiagram {
 
 [Corrections + Checkpoints M4 (#358)] as [M4] on {Luis} {Jeff} {Brent} {Hamza} requires 3 days
 [M4] starts at [M3]'s end
-[M4] is 60% completed
+[M4] is 46% completed
 [M4] is colored in LightSkyBlue/SteelBlue
 
 
@@ -283,12 +282,12 @@ ganttDiagram {
 
 [ACMS v1 + Context Scaling M5 (#359)] as [M5] on {Hamza} {Jeff} {Aditya} {Brent} requires 4 days
 [M5] starts at [M4]'s end
-[M5] is 68% completed
+[M5] is 40% completed
 [M5] is colored in LightSkyBlue/SteelBlue
 
 [Autonomy Hardening + Stubs M6 (#360)] as [M6] on {Luis} {Jeff} {Hamza} {Brent} requires 5 days
 [M6] starts at [M5]'s end
-[M6] is 55% completed
+[M6] is 17% completed
 [M6] is colored in LightSkyBlue/SteelBlue
 
 
@@ -299,7 +298,7 @@ ganttDiagram {
 
 [Large Project Autonomy (#369)] as [LARGE] on {Luis} {Brent} {Jeff} requires 4 days
 [LARGE] starts 2026-03-17
-[LARGE] is 43% completed
+[LARGE] is 35% completed
 [LARGE] is colored in LightSkyBlue/SteelBlue
 
 ' ── v3.5.0 MILESTONE ─────────────────────────────────────────
@@ -445,7 +444,7 @@ saturday are closed
 sunday are closed
 printscale weekly zoom 2
 
-today is 2026-04-10
+today is 2026-04-12
 today is colored in #FF6666
 
 <style>
@@ -1966,13 +1965,13 @@ This section provides a high-level overview of the CleverAgents implementation r
 
 ### Current Status Summary
 
-As of Day 100 (2026-04-10), the project has **225 open PRs** and **~2777 open issues** across active milestones. **Session 4 is active (launched 2026-04-08, issue #4799) with 32 parallel workers and full supervisor fleet**. Bug count is **~25 open bugs** (Type/Bug label; UAT issues tracked separately). M8 (v3.7.0) is now **45% complete** (425/944 issues closed). M3 (v3.2.0) at **32%** (249/770 — scope massively expanded), M4 (v3.3.0) at **49%** (108/220), M5 (v3.4.0) at **43%** (133/313), M6 (v3.5.0) at **18%** (197/1085 — scope massively expanded), M7 (v3.6.0) at **38%** (150/400).
+As of Day 102 (2026-04-12), the project has **257 open PRs** and **~3181 open issues** across active milestones. **Session 4 is active (launched 2026-04-08, issue #4799) with 32 parallel workers and full supervisor fleet**. Bug count is **~3 open bugs** (Type/Bug label — major bug-fix wave since Day 100). M8 (v3.7.0) is now **45% complete** (427/956 issues closed). M3 (v3.2.0) at **28%** (262/948 — scope expanded 770→948), M4 (v3.3.0) at **46%** (108/233), M5 (v3.4.0) at **40%** (137/345), M6 (v3.5.0) at **17%** (201/1181 — scope expanded 1085→1181), M7 (v3.6.0) at **35%** (152/433).
 
-**M1, M2 fully complete. M3 (v3.2.0)**: 33% complete (248/757), 509 open issues — scope expanded massively. **M4 (v3.3.0)**: 49% complete (108/220), 112 open issues. **M5 (v3.4.0)**: 44% complete (133/301), 168 open issues. **M6 (v3.5.0)**: 18% complete (197/1065), 868 open issues — scope expanded massively. **M7 (v3.6.0)**: 38% complete (150/392), 242 open issues. **M8 (v3.7.0)**: 45% complete (423/938), 515 open issues. All milestones M3-M7 are **overdue**; M8 is in active v3.7.0 development.
+**M1, M2 fully complete. M3 (v3.2.0)**: 28% complete (262/948), 686 open issues — scope expanded massively. **M4 (v3.3.0)**: 46% complete (108/233), 125 open issues. **M5 (v3.4.0)**: 40% complete (137/345), 208 open issues. **M6 (v3.5.0)**: 17% complete (201/1181), 980 open issues — scope expanded massively. **M7 (v3.6.0)**: 35% complete (152/433), 281 open issues. **M8 (v3.7.0)**: 45% complete (427/956), 529 open issues. **M9 (v3.8.0)**: 27% complete (132/489), 357 open issues. All milestones M3-M7 are **overdue**; M8/M9 in active development. New v3.9.0 milestone added (13 open, 4 closed).
 
-!!! warning "Schedule Risk: All Milestones M3-M7 Overdue — Massive Scope Expansion — Session 4 Active (Day 100: 219 Open PRs, M3/M6 Scope Exploded)"
+!!! warning "Schedule Risk: All Milestones M3-M7 Overdue — Massive Scope Expansion — Session 4 Active (Day 102: 257 Open PRs, M3/M6 Scope Expanded)"
 
-    All milestones M3 through M7 have passed their target dates. **Session 4 active (launched 2026-04-08, issue #4799) with 32 parallel workers**. Open PRs at **219** (up from 1 — agents opened many new PRs). Open bugs at **~5** (Type/Bug label). Session tracker issue: #4799. **Current priorities**: (1) **M3 scope explosion** — 509 open issues (was 85 at Day 98); scope grew from 320 to 757 total. (2) **M6 scope explosion** — 868 open issues (was 450 at Day 98); scope grew from 638 to 1065 total. (3) **Merge 219 open PRs** — pr-merge-pool-supervisor added as 17th supervisor. (4) **Continue M8 push** — 45% complete, 515 issues remaining. (5) **Clear M4/M5 backlogs** — M4 at 49% (112 open), M5 at 44% (168 open).
+    All milestones M3 through M7 have passed their target dates. **Session 4 active (launched 2026-04-08, issue #4799) with 32 parallel workers**. Open PRs at **257** (up from 225 — agents opened 32 new PRs). Open bugs at **~3** (Type/Bug label — major bug-fix wave). Session tracker issue: #4799. **Current priorities**: (1) **M3 scope explosion** — 686 open issues; scope grew from 770 to 948 total. (2) **M6 scope explosion** — 980 open issues; scope grew from 1085 to 1181 total. (3) **Merge 257 open PRs** — pr-merge-pool-supervisor active. (4) **Continue M8 push** — 45% complete, 529 issues remaining. (5) **Clear M4/M5 backlogs** — M4 at 46% (125 open), M5 at 40% (208 open).
 
 ### Parallel Workstreams
 
@@ -5316,3 +5315,96 @@ Story points per developer per milestone.
 | M9 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
 | M6+ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
 | **Total** | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~1649 SP |
+
+### 2026-04-12 (Day 102)
+
+**Summary**
+
+Status: Behind 25+d
+Deadline risk: CRITICAL
+
+**Notes**
+
+- Day 102 update (2026-04-12, cycle 1). Session 4 active (issue #4799, 32 parallel workers, full supervisor fleet). Open PRs: 225→257 (+32 new agent-driven PRs). Open bugs (Type/Bug label): ~25→3 (major bug-fix wave since Day 100).
+- Milestone scope continued to expand since Day 100: M3 grew from 770→948 (+178), M4 grew from 220→233 (+13), M5 grew from 313→345 (+32), M6 grew from 1085→1181 (+96), M7 grew from 400→433 (+33), M8 grew from 944→956 (+12), M9 grew from 475→489 (+14). New v3.9.0 milestone added (17 total issues, 4 closed).
+- Milestone completions (Day 102): M3 28% (262/948, was 32% at Day 100 — scope expansion outpacing closures), M4 46% (108/233, was 49%), M5 40% (137/345, was 43%), M6 17% (201/1181, was 18%), M7 35% (152/433, was 38%), M8 45% (427/956, was 45% — stable), M9 27% (132/489, was 28%).
+- Significant bug-fix wave: open Type/Bug issues dropped from ~25 to 3 (issues #7989, #7991, #7992 — LockService not wired into plan lifecycle, ServiceRetryWiring dead code at runtime, UKOQueryInterface.get_resources_by_layer never returns resources). All three are Priority/Critical.
+- Open PRs grew from 225 to 257 (+32) as agents continued opening fix/feature PRs. PR #7957 (bug-hunt-pool-supervisor tracking prefix fix) is open and awaiting merge.
+- All milestones M3-M7 remain overdue. M8 and M9 have no deadlines and are in active development. Agent-driven issue creation continues at high velocity across all milestones.
+- v3.9.0 milestone newly created (2026-04-10) with 13 open and 4 closed issues — documentation and feature updates scope.
+
+
+#### Milestone forecast
+
+| Milestone | Target -> ETA | Delta | Risk |
+|-----------|---------------|-------|------|
+| M1 (v3.0.0) | (2026-02-15) -> COMPLETE | 0d | COMPLETE |
+| M2 (v3.1.0) | (2026-02-22) -> COMPLETE | 0d | COMPLETE |
+| M3 (v3.2.0) | (2026-02-26) -> ETA 2026-06-30 | +125d | CRITICAL — 686 open issues; 28% complete (scope expanded 770→948) |
+| M4 (v3.3.0) | (2026-03-02) -> ETA 2026-05-25 | +84d | CRITICAL — 125 open issues; 46% complete |
+| M5 (v3.4.0) | (2026-03-06) -> ETA 2026-06-01 | +87d | HIGH — 208 open issues; 40% complete |
+| M6 (v3.5.0) | (2026-03-10) -> ETA 2026-08-15 | +158d | CRITICAL — 980 open issues; 17% complete (scope expanded 1085→1181) |
+| M7 (v3.6.0) | (2026-03-28) -> ETA 2026-06-25 | +89d | HIGH — 281 open issues; 35% complete |
+| M8 (v3.7.0) | (no deadline) -> ETA 2026-07-20 | N/A | HIGH — 529 open issues; 45% complete (stable) |
+| M9 (v3.8.0) | (no deadline) -> ETA 2026-08-01 | N/A | MEDIUM — 357 open issues; 27% complete |
+
+#### Track forecast
+
+| Track | Status | ETA | Risk | Blocking |
+|-------|--------|-----|------|----------|
+| Track A (Plan lifecycle + persistence) | Complete | Done | LOW | None |
+| Track B (Projects/resources + sandbox) | In Progress | ETA 2026-06-01 | HIGH | 208 open issues in v3.4.0; scope expanded +32 since Day 100 |
+| Track C (Actors/tools/skills/validations) | In Progress | ETA 2026-05-25 | CRITICAL | 125 open issues in v3.3.0; 3 critical bugs open (LockService, RetryWiring, UKO) |
+| Track D (Change tracking + apply pipeline) | In Progress | ETA 2026-06-30 | CRITICAL | 686 open issues in v3.2.0; scope expanded +178 since Day 100 |
+| Track Q (Quality automation) | Ongoing | N/A | HIGH | 3 Priority/Critical bugs open; 257 open PRs need merge; pr-merge-pool-supervisor active |
+| Track T (Testing) | Active | Ongoing | HIGH | 257 open PRs need review; UAT bugs ongoing; Session 4 active |
+
+#### Developer forecast
+
+| Name | Days Ahead/Behind | Availability | Risk | Focus |
+|------|-------------------|--------------|------|-------|
+| Jeff | -27d behind | active | HIGH | Session 4 supervisor; M3/M4/M5 backlog clearance; architecture oversight; PR merge pool |
+| Luis | -27d behind | active | HIGH | M6 (v3.5.0) features; security hardening; LockService/RetryWiring critical bugs; PR review pool |
+| Hamza | -27d behind | active | HIGH | Resource DAG; v3.6.0 features; UKO layer bug (#7992); PR reviews |
+| Aditya | -27d behind | active | HIGH | M5 features; TDD counterparts; domain model work; UAT testing |
+| Brent | -27d behind | active | HIGH | Bug fixes; TDD counterparts; quality automation; 3 critical bugs triage |
+| Rui | -27d behind | active | HIGH | TUI features; UAT bug fixes; security bug-hunt; E2E testing |
+| Mike/Brian | N/A | standby | LOW | Infrastructure support |
+
+#### Task inventory
+
+Milestone per developer as of Day 102 (2026-04-12).
+
+| Milestone | Jeff | Aditya | Luis | Hamza | Brent | Rui | Unassigned | Total |
+|-----------|------|--------|------|-------|-------|-----|------------|-------|
+| M1 | 29/29 | 16/16 | N/A | 4/4 | 10/10 | N/A | 35/35 | 96/96 |
+| M2 | 26/26 | 14/14 | N/A | 1/1 | 5/5 | N/A | 6/6 | 56/56 |
+| M3 | N/A | N/A | N/A | N/A | N/A | N/A | 686 open | 262/948 |
+| M4 | N/A | N/A | N/A | N/A | N/A | N/A | 125 open | 108/233 |
+| M5 | N/A | N/A | N/A | N/A | N/A | N/A | 208 open | 137/345 |
+| M6 | N/A | N/A | N/A | N/A | N/A | N/A | 980 open | 201/1181 |
+| M7 | N/A | N/A | N/A | N/A | N/A | N/A | 281 open | 152/433 |
+| M8 | N/A | N/A | N/A | N/A | N/A | N/A | 529 open | 427/956 |
+| M9 | N/A | N/A | N/A | N/A | N/A | N/A | 357 open | 132/489 |
+| v3.9.0 | N/A | N/A | N/A | N/A | N/A | N/A | 13 open | 4/17 |
+| **Total** | **N/A** | **N/A** | **N/A** | **N/A** | **N/A** | **N/A** | **~3181 open** | **1525/4706 closed** |
+
+Note: "done/total" = closed/total for that milestone. Assignee data reflects Forgejo API as of Day 102 (2026-04-12). Most open issues are unassigned or assigned to freemo (Jeff). Agent-driven issue creation continues at high velocity. M3 grew from 770→948 (+178), M4 grew from 220→233 (+13), M5 grew from 313→345 (+32), M6 grew from 1085→1181 (+96), M7 grew from 400→433 (+33), M8 grew from 944→956 (+12), M9 grew from 475→489 (+14) since Day 100. Open bugs dropped from ~25 to 3 (major bug-fix wave). Open PRs grew from 225 to 257 (+32 new agent-driven PRs).
+
+#### Story point allocation
+
+Story points per developer per milestone.
+
+| Milestone | Jeff | Aditya | Luis | Hamza | Brent | Rui | Unassigned | Total |
+|-----------|------|--------|------|-------|-------|-----|------------|-------|
+| M1 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~172 SP |
+| M2 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~208 SP |
+| M3 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~104 SP |
+| M4 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~126 SP |
+| M5 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~129 SP |
+| M6 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
+| M7 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~100 SP |
+| M8 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
+| M9 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
+| M6+ | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~TBD SP |
+| **Total** | N/A | N/A | N/A | N/A | N/A | N/A | N/A | ~1649 SP |

robot/coverage_threshold.robot

@@ -34,8 +34,7 @@ Pyproject Coverage Source Includes Src
 
 Coverage Threshold Is 97 In Noxfile
     [Documentation]    Verify noxfile enforces 97% threshold via fail-under
-    [Tags]    tdd_issue    tdd_issue_4227    tdd_expected_fail
-    [Tags]    coverage    config
+    [Tags]    coverage    config    tdd_issue    tdd_issue_4227
     ${content}=    Get File    ${WORKSPACE}/noxfile.py
     Should Contain    ${content}    --fail-under=
 

scripts/validate_automation_tracking.py

@@ -24,6 +24,7 @@ AGENT_PREFIXES: dict[str, list[str]] = {
     "WATCHDOG": ["System Health", "Alert"],
     "GROOMER": ["Grooming Report", "Scope Alert"],
     "LIAISON": ["Status Update", "Human Activity Summary"],
+    "DOCS": ["Documentation Report"],
 }
 
 # Title format patterns
@@ -117,8 +118,16 @@ def validate_automation_tracking_issue(
         for label in labels
     ]
 
-    if "Automation Tracking" not in label_names:
-        errors.append("Missing required 'Automation Tracking' label")
+    required_labels = [
+        "Automation Tracking",
+        "Type/Automation",
+        "State/In Progress",
+        "Priority/Medium",
+    ]
+
+    for required_label in required_labels:
+        if required_label not in label_names:
+            errors.append(f"Missing required '{required_label}' label")
 
     # Validate body content (basic checks)
     body = issue_data.get("body", "")
@@ -139,9 +148,14 @@ def get_tracking_issues_from_repo(
     """Fetch automation tracking issues from repository.
 
     Note: This is a stub — in real usage, integrate with the Forgejo API.
+    Real implementations must paginate results because Forgejo limits
+    responses to 50 items per page by default.
     """
     print(f"Note: Repository validation for {owner}/{repo} requires API integration")
-    print("This is a demonstration of the validation logic.")
+    print(
+        "This is a demonstration of the validation logic. Real integrations must "
+        "paginate Forgejo API responses (commonly limited to 50 items per page)."
+    )
     return []
 
 
@@ -157,6 +171,7 @@ def _run_validate_all() -> int:
         ("[AUTO-WATCHDOG] System Health (Cycle 8)", True),
         ("[AUTO-GROOMER] Grooming Report (Cycle 23)", True),
         ("[AUTO-LIAISON] Status Update (Cycle 67)", True),
+        ("[AUTO-DOCS] Documentation Report (Cycle 1)", True),
         (
             "[AUTO-SESSION] Announce: Emergency system restart required",
             True,
@@ -222,7 +237,7 @@ def main() -> int:
         print(f"Message: {message}")
         return 0 if is_valid else 1
 
-    if args.repo:
+    elif args.repo:
         try:
             owner, repo_name = args.repo.split("/", 1)
             get_tracking_issues_from_repo(owner, repo_name)
@@ -232,7 +247,7 @@ def main() -> int:
             print("Error: Repository must be in format 'owner/repo'")
             return 1
 
-    if args.validate_all:
+    elif args.validate_all:
         return _run_validate_all()
 
     parser.print_help()