ac/android_cast
1
0
Fork 0
mirror of git://f0xx.org/android_cast synced 2026-07-29 04:18:09 +03:00
Code Issues Packages Projects Releases Wiki Activity

sync BE

Browse Source
This commit is contained in:
Anton Afanasyeu
2026-06-08 19:02:12 +02:00
parent c1591fa849
commit 3bd9a24559
24 changed files with 907 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
.cursor/rules/dev-help-request-reminder.mdc Normal file
View File

@@ -0,0 +1,49 @@
---
description: Remind developer about help_request.pdf when agent work depends on human input
alwaysApply: true
---
# Developer help-request reminder
When **any** of your work, replies, or session wrap-ups depend on the **developer / project owner** (not agent-only), you **must** remind them about the hands-on checklist.
## Trigger — remind when
- Tasks are **blocked** or **slowed** waiting on dev (DNS, MX/SPF, SMTP, device QA, OTA URLs, WireGuard bastion ops, inbound mail test, etc.)
- You end a session where dev-owned items from [docs/20260608_ALPHA_PRIORITIES.md](docs/20260608_ALPHA_PRIORITIES.md) remain open
- You mention “blocked on you”, “developer when back”, or similar
- Auth/mail path needs live email (tasks **2.1–2.4**, **E1–E5** in 2FA doc)
- LAN alpha QA (**6.x**) or backend validation needing a physical device (**5.2**)
## What to cite
Primary checklist (markdown + PDF):
- **`tmp/20260608_help_request.md`**
- **`tmp/20260608_help_request.pdf`**
If a **new** dev session needs a different checklist, create `tmp/YYYYMMDD_help_request.md` + PDF per [docs/20260608_ALPHA_PRIORITIES.md](docs/20260608_ALPHA_PRIORITIES.md) § bottom line — then cite that file instead.
## Format (end of reply — separate block, impossible to miss)
Use when triggers apply (can combine with BE deploy banner if both apply):
```
───────────────────────────────────────────────────────────────
📋 YOUR ACTION — help_request.pdf
───────────────────────────────────────────────────────────────
• Open: tmp/20260608_help_request.pdf (or latest tmp/*_help_request.pdf)
• Unblocks: … (1–3 bullets — what agent work is waiting on you)
• Reply when done: … (what to paste back — MX, SPF, inbound test, etc.)
───────────────────────────────────────────────────────────────
```
Keep bullets short. Do **not** bury this in prose.
## Agent habit
At the **start** of a turn, if open work still has dev dependencies from the task graph, briefly note that the help checklist exists — do not wait until session end only.
Do **not** show the block when there are zero dev dependencies in that reply.