# Obsidian Bug Tracker — Agent Contract

User-maintained bug reports live outside the repo. Read this file when asked to triage, investigate, or work from the bug backlog.

**Overrides** `agents-docs/AGENT_WORKFLOW.md` §8 (Autonomous Bug Fixing) unless the user explicitly asks you to fix a bug in code.

---

## Location

| Item | Path |
|------|------|
| Bug inbox | `/home/ludde/Nextcloud/Obsidian Vault/Log/Bugs/` |
| Attachments | `…/Bugs/attachments/<Bug title>/` |
| Dashboard | `/home/ludde/Nextcloud/Obsidian Vault/Log/Create bug.md` |
| Template | `/home/ludde/Nextcloud/Obsidian Vault/Log/Templates/Bug Report.md` |

---

## Allowed actions on vault files

Unless the user explicitly asks for more:

1. **Change `status`** in a bug note's YAML frontmatter (`Open` → `Resolved` or `Closed`).
2. **Move files** (e.g. reorganize notes or attachments when instructed).

Do **not** edit other vault fields or sections (`Investigation`, `Resolution`, description, etc.) unless the user asks.

---

## Allowed reads (unrestricted)

To understand and solve bugs you may read freely:

- All bug notes and attachments under `Log/Bugs/`
- The full MetoYou repo (code, tests, logs, docs)
- Runtime output, test results, and debug artifacts

Investigation findings belong in chat or in repo changes — not in the vault — unless the user asks you to update the note.

---

## Bug note format

Each note is Markdown with YAML frontmatter:

```yaml
---
title: Bug - …
type: bug
status: Open          # Open | Resolved | Closed
priority: Low | Medium | High | Critical
severity: Low | Medium | High | Critical
environment: …
created: YYYY-MM-DD HH:mm
tags: [bug]
---
```

Body sections: **Description**, **Steps to Reproduce**, **Expected Result**, **Actual Result**, **Logs / Screenshots**, **Investigation**, **Resolution**.

The dashboard (`Create bug.md`) uses Dataview; keep `type: bug` and `status` accurate so counts stay correct.

---

## Workflow

1. List open bugs: `Glob` or `ls` on `…/Log/Bugs/*.md`, filter `status: Open`.
2. Read the note and any linked attachments.
3. Investigate in the repo (read-only toward the vault).
4. Report findings to the user.
5. Only when told to fix: implement in repo (TDD, lint, build per `AGENTS.md`).
6. When a bug is done: update vault `status` to `Resolved` or `Closed` (and move files if the user specifies a convention).

---

## Open bugs (snapshot 2026-06-10)

| Title | Priority | Environment |
|-------|----------|-------------|
| Attachments gets syncronized corrupt | Critical | All major clients |
| Chats doesn't sync for multi client users | High | All |
| No android app icon | High | Android |
| No login screen mobile phone on startup | High | Android, Android Browser |
| Fresh users have the server list in dashboard completely empty until anything searched | High | — |
| Video attachment on android gets sent in the message bubble above with no preview image | High | Android |
| Local files should be remembered by client | High | — |
| Emojis should be user bound not client bound | Medium | All |

Re-scan the folder at session start; this table is not auto-updated.