feat: run wiki writer on daily schedule instead of closed PRs

Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>

Author: Copilot

docs/agentic-wiki-writer.md

@@ -4,7 +4,7 @@
 
 **Automatically generates and maintains GitHub wiki pages from your source code**
 
-The [Agentic Wiki Writer workflow](../workflows/agentic-wiki-writer.md?plain=1) keeps your project's GitHub wiki synchronized with the codebase. After each merged pull request (or on demand), it reads a `PAGES.md` template to understand what to document, then writes wiki pages directly from the source code.
+The [Agentic Wiki Writer workflow](../workflows/agentic-wiki-writer.md?plain=1) keeps your project's GitHub wiki synchronized with the codebase. Once a day (if any pull requests were merged to the default branch), it reads a `PAGES.md` template to understand what to document, then writes wiki pages directly from the source code. You can also trigger it manually on demand.
 
 > [!WARNING]
 > **The repository wiki must be initialized before running this workflow.** GitHub does not create the wiki git repository until at least one page exists. Go to your repository's **Wiki** tab and create a blank page (e.g. "Home") to initialize it. The workflow will fail with a git clone error if this step is skipped.
@@ -25,18 +25,20 @@ This walks you through adding the workflow to your repository.
 
 ```mermaid
 graph LR
-    A[PR merged / manual trigger] --> B{PAGES.md exists?}
-    B -->|No| C[Generate PAGES.md template]
-    B -->|Yes| D[Read PAGES.md template]
-    C --> E[Save template to .github/agentic-wiki/]
-    D --> F[Identify changed files from PR]
-    F --> G[Read relevant source files]
-    G --> H[Write wiki pages]
-    H --> I[Push wiki pages]
-    I --> J[Create PR if source changes needed]
+    A[Daily schedule / manual trigger] --> B{Any merges today?}
+    B -->|No| C[Skip - no wiki update needed]
+    B -->|Yes| D{PAGES.md exists?}
+    D -->|No| E[Generate PAGES.md template]
+    D -->|Yes| F[Read PAGES.md template]
+    E --> G[Save template to .github/agentic-wiki/]
+    F --> H[Identify changed files from recent merges]
+    H --> I[Read relevant source files]
+    I --> J[Write wiki pages]
+    J --> K[Push wiki pages]
+    K --> L[Create PR if source changes needed]
 ```
 
-On the first run (or when `regenerate-template` is enabled), the workflow generates a `PAGES.md` template describing the wiki structure it will maintain. On subsequent runs it follows the template — reading only the source files relevant to the merged PR, then writing updated wiki content.
+On the first run (or when `regenerate-template` is enabled), the workflow generates a `PAGES.md` template describing the wiki structure it will maintain. On subsequent runs it follows the template — reading only the source files relevant to the recently merged PRs, then writing updated wiki content.
 
 ### Key Features
 
@@ -52,12 +54,34 @@ Trigger the workflow manually with `regenerate-template: true` to create the ini
 
 ### Configuration
 
-The workflow triggers automatically on every merged PR to the default branch. You can also trigger it manually from the Actions tab:
+The workflow runs once a day (at midnight UTC) and checks whether any pull requests were merged to the default branch in the last 24 hours. If no merges happened, it exits early with no work done. You can also trigger it manually from the Actions tab.
 
-- **`regenerate-template`** (`boolean`, default `false`) — Set to `true` to rebuild the `PAGES.md` template from scratch.
+You can adjust the cadence or event structure to suit your team's workflow. For example, to run on every push to the default branch instead of on a schedule, replace the `schedule: daily` trigger with:
+
+```yaml
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+    ...
+```
+
+Or to run twice a day, change the schedule to:
+
+```yaml
+on:
+  schedule:
+    - cron: "0 6,18 * * *"
+  workflow_dispatch:
+    ...
+```
 
 After editing the workflow file, run `gh aw compile` to update the compiled workflow and commit all changes to the default branch.
 
+Available inputs for manual dispatch:
+
+- **`regenerate-template`** (`boolean`, default `false`) — Set to `true` to rebuild the `PAGES.md` template from scratch.
+
 ## PAGES.md Format
 
 The `PAGES.md` file at `.github/agentic-wiki/PAGES.md` is the single source of truth for your wiki structure. It is generated automatically on the first run and saved as a PR for you to review. After that, you can edit it freely to customize your documentation structure. You can also supply a `PAGES.md` yourself before the first run to pre-define the structure.

workflows/agentic-wiki-writer.md

@@ -2,17 +2,15 @@
 name: Agentic Wiki Writer
 description: >
   Generates GitHub wiki pages from source code using a PAGES.md template.
-  Runs on PR merge or manual dispatch with agent-driven triage.
+  Runs once a day if any merges to the default branch have happened, or on manual dispatch.
 on:
   workflow_dispatch:
     inputs:
       regenerate-template:
         description: "Regenerate PAGES.md from scratch (full regen)"
         type: boolean
         default: false
-  pull_request:
-    types: [closed]
-    branches: [main]
+  schedule: daily
 permissions:
   contents: read
   issues: read
@@ -119,19 +117,22 @@ You have persistent storage that survives across runs. To find the path, run `ls
 2. **Read memory files** from that directory before starting work.
 3. **After finishing**, use the `write` tool to save updated memory files to the same directory.
 
-## Step 0: Triage (PR merge triggers only)
+## Step 0: Triage (scheduled triggers only)
 
 If this workflow was triggered by `workflow_dispatch`, **skip this step entirely** — always proceed to Step 1.
 
-If this workflow was triggered by a `pull_request` event, you must first check that the PR was actually merged (not just closed), then determine whether the changes are likely to affect wiki documentation.
+If this workflow was triggered by the `schedule` event, check whether any pull requests have been merged into the default branch in the last 24 hours. If none have been merged, there is nothing to document — call the `noop` safe-output with "No merges to the default branch in the last 24 hours" and **stop**.
 
-### 0a. Check if PR was merged
+### 0a. Check for recent merges
 
-Use the GitHub tools to inspect the pull request that triggered this run. If the PR was **closed without merging**, call the `noop` safe-output with "PR was closed without merging" and **stop**.
+Use the GitHub tools to list recently merged pull requests. Look for any PRs merged into the default branch within the past 24 hours.
+
+- If **no PRs were merged** in the last 24 hours → call the `noop` safe-output and **stop**.
+- If **one or more PRs were merged** → continue to step 0b.
 
 ### 0b. Identify what changed
 
-Look at the files changed in the merged PR. Use the GitHub tools to list the PR's changed files.
+Collect the files changed across all PRs merged into the default branch in the last 24 hours. Use the GitHub tools to list the changed files for each merged PR.
 
 ### 0c. Load source map from memory
 
@@ -151,7 +152,7 @@ Use your judgment. If you're unsure whether a change affects the wiki, err on th
 
 ### 0e. Decision
 
-- If **no wiki update needed** → call the `noop` safe-output with a message explaining why (e.g., "PR only modified test files — no wiki impact") and **stop**.
+- If **no wiki update needed** → call the `noop` safe-output with a message explaining why (e.g., "Merged PRs only modified test files — no wiki impact") and **stop**.
 - If **wiki update needed** → proceed to **Step 1**.
 
 ## Step 1: Check for PAGES.md