docs: add three repository routine prompts - #43
Conversation
Add the routine prompts for the nightly PR babysitter, the deck merge follow-up, and the weekly ceremony audit. Each file carries the trigger, the repository list, and the complete prompt. The provider setup stays manual through the Claude routine picker. Co-Authored-By: Martin Zeman <N4M3Z@users.noreply.github.com>
|
@cursor review |
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — Although committed as Markdown and installed manually, these files introduce scheduled repository-scanning workflows with private-data access, network-boundary rules, and GitHub comment or issue writes. Their new operational and security-sensitive behavior warrants human review. Notes:
No code changes detected at You can add or adjust custom eligibility rules. Learn more. |
|
Failing step: Quality, Release notes attestation. Cause: The pull request body has no Release Notes section with a list entry. Suggested fix: Add a Release Notes heading and one list entry. Use |
Rewrite the three routine prompts with the BuildTask discipline: an authority section, untrusted-data rules, permitted and prohibited operations, coverage counts, a status order, and a fixed notification structure.
The merge follow-up posted per-PR consumer comments. The owner wants awareness: one daily notification with merges, pushes, releases, and fork-upstream movement across configured repositories. Add the configurable repo-digest template, move the audit to Monday 05:00 CET, and put the babysitter on hold.
Match the deck docs naming convention, for example BenchArtifact Anatomy.md.
|
Not reviewed. This change modifies prose outside the executable specification and workflow scope. Reviewed |
|
Not reviewed. This change modifies prose outside the executable specification and workflow scope. Reviewed |
Capture the routine best practices as a spec-driven change and a decision record. DECK-0004 fixes the environment matrix: the data sensitivity of what a session reads selects its environment, a private repository never mounts beside general egress, and the prompt register is the control layer. The routine-operations capability specifies the scanner register, the loud canary, the provider adaptations, and the manual provider setup. Sync the audit and digest templates with the decided environments.
The audit runs in the Default environment: the repository chips supply the checkouts and the GitHub proxy supplies API access. No private repository chip and no general egress. Move the schedule to Monday 05:40.
Four live runs failed on absent repository chips, and each notification guessed at environments instead of naming the chip row. The startup checks now map the 403 signature to its control, the headers call the repository grants chips and tell the owner to confirm they persist after Save, and the specification gains the Grant Diagnosis requirement.
Plan
Capture the routine operating practice in one place: the prompts, the specification, and the environment decision.
Changes
docs/routines/:Nightly PR Babysitter.md(on hold),Repository Digest.md, andWeekly Ceremony Audit.md, each in the scanner register with picker settings separated from the paste-ready prompt.docs/decisions/DECK-0004 Routine Environment Matrix.md: the environment follows the sensitivity of the readable data, and a private repository never mounts beside general egress.routine-operationsspec-driven change: the scanner register, the loud canary, honest degradation, provider adaptation, rendered-value privacy, and manual provider setup.Testing
rune spec validate routine-operationspasses.Release Notes
Note
Add routine-operations spec,
DECK-0004environment matrix, and three repository routine promptsMacroscope summarized 99a478e.