syncthing: remove stale deleted files from upstream

This commit is contained in:
Syncthing
2026-05-30 12:01:52 +00:00
parent df2f387708
commit d3bf71cadb
59 changed files with 77 additions and 0 deletions
Vendored Executable → Regular
View File
Executable → Regular
View File
Executable → Regular
View File
View File
+3
View File
@@ -0,0 +1,3 @@
# Index
[[work/_index]] | [[personal/_index]] | [[family/_index]]
+74
View File
@@ -0,0 +1,74 @@
---
namespace: work
tags: [asana, ddg, workflow, rules]
last_synced: 2026-04-27
confidence: 1.0
---
# DuckDuckGo Asana Workflow
## Alex's Identity
- **Assignee GID**: `1202406491309495`
- **Role**: macOS Browser Developer at DuckDuckGo
- **Career advisor**: Dominik
## Task Sources in DB
| `source` | Meaning | Eagle's default role |
|----------|---------|---------------------|
| `my_tasks` | Assigned to Alex | DRI — drives to completion |
| `delegated` | Created by Alex, assigned to others | Delegator — tracks progress |
| `following` | Alex is a follower/CC | Observer — no action unless asked |
| `project` | In a shared project Alex follows | Context only |
## Task Type Classification
**Ship Review** — name contains "Ship Review:" or is in "Ship Reviews" project
- Alex as assignee → DRI (drives all AOR approvals)
- Alex as named reviewer → AOR Reviewer (provide feedback, signal done)
**Tech Design** — name contains "Tech Design:", "TD:", or "Design Doc:"
- Alex as assignee/author → address feedback, drive to approval
- Alex as reviewer → review, comment, approve/iterate
**PFR (Product Feedback Request)** — name starts "PFR:"
- 3-day implicit deadline. Requestor summarizes decision after window closes.
**Rotation** — name contains "Maintenance Rotation", "Triage Rotation", "Release DRI", "PFM DRI"
- Has date range + structured checklist
## Status Labels
`NEEDS ACTION` | `WAITING` | `BLOCKED` | `STALLED` | `ON TRACK` | `OVERDUE` | `MONITORING`
Priority order in brief: OVERDUE → NEEDS ACTION → BLOCKED → STALLED → WAITING → MONITORING
## Weekly Rhythms
- **TP (Top Priority)**: one task per week, set Monday. Tier 1 = primary. Stale if not changed >2 weeks.
- **1-Must**: one task per day, set each morning. Should be achievable today.
- **1:1 with Dominik**: weekly. Prep agenda in advance.
- **Quick Wins Days**: periodic WedFri sprints. Shift from project deep-work to clearing backlog.
- **Rotation**: active if assigned "Maintenance Rotation" or similar. Handoff notes due Friday.
## Key Rules
- Silence ≠ approval. Never assume a task is done without explicit confirmation.
- "No action needed" on a DRI task requires proof (all approvals collected).
- If someone addressed your feedback and re-requested review → **you are the blocker**. NEEDS ACTION.
- Stale TP (>2 weeks unchanged) → surface it.
- Performance review deadline within 3 days → HIGH PRIORITY.
- Major incident with no postmortem >3 days after resolution → OVERDUE, critical.
## Asana MCP Usage Rules
Use Asana MCP only in two cases:
1. Task GID is referenced but missing from DB → `asana_get_task`
2. Stories in DB are incomplete/stale → `asana_get_stories_for_task`
Never bulk-query Asana live. Never use MCP to scan projects — that's sync.js's job.
## Related
[[personal-os-agent-rules]] [[personal-os-sync-pipeline]]
Vendored Executable → Regular
View File
Executable → Regular
View File
View File
View File
View File
Executable → Regular
View File
Vendored Executable → Regular
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File
View File