sulthan
08749df050
Swap modernc.org/sqlite for jackc/pgx/v5 with no observable change: same endpoints, same wire format, same updated_at ordering rule. The schema now comes from numbered SQL embedded in the binary and applied on startup, one transaction each, recorded in schema_migrations. That replaces two pieces of SQLite-era machinery, both deleted rather than ported: the column probing (Postgres has ADD COLUMN IF NOT EXISTS, and there is no legacy database left to probe) and the Asura key rewrite, which has run clean on every start for months now that the userscripts strip build hashes before writing. Its regexp survives as latest.asuraBuildHash, where the poller still needs it to scope chapter links to a series whose slug carries a rotating hash. Types get real: favorite is a boolean, chapter numbers double precision, timestamps stay unix-ms bigint. SQLite's null-safe IS NOT becomes IS DISTINCT FROM, which is what implements the rule that only reading progress reorders a list. Inside COALESCE/NULLIF the status and kind parameters need an explicit ::text -- there is no target column to infer from and Postgres refuses to guess. Tests lose their free t.TempDir() database, so Docker is now a hard prerequisite for `go test ./...`: internal/pgtest starts one postgres:17-alpine per test binary and hands each test a database of its own. Also lands CONTEXT.md and the four ADRs written while scoping #18. BREAKING CHANGE: DB_PATH is retired for DATABASE_URL, which is required and has no default. Compose gains a postgres service on an internal network with its own volume; POSTGRES_PASSWORD joins .env. The old bookmarks-data volume is deliberately left undeclared so `docker compose down -v` cannot take the pre-migration database with it. main is not deployable until #25 and #26 land. Closes #20 Co-authored-by: Sulthan Zaki <sultankiki05@gmail.com> Co-committed-by: Sulthan Zaki <sultankiki05@gmail.com>
21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
# Triage Labels
|
|
|
|
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual
|
|
label strings used in this repo's issue tracker (Gitea — see `docs/agents/issue-tracker.md`).
|
|
|
|
| Label in mattpocock/skills | Label in our tracker | Meaning |
|
|
| -------------------------- | -------------------- | ---------------------------------------- |
|
|
| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this issue |
|
|
| `needs-info` | `needs-info` | Waiting on reporter for more information |
|
|
| `ready-for-agent` | `ready-for-agent` | Fully specified, ready for an AFK agent |
|
|
| `ready-for-human` | `ready-for-human` | Requires human implementation |
|
|
| `wontfix` | `wontfix` | Will not be actioned |
|
|
|
|
When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label
|
|
string from this table.
|
|
|
|
Gitea will not auto-create labels on `tea issue edit --add-labels`; create a missing one first with
|
|
`tea labels create --name "<label>" --color "#rrggbb"`.
|
|
|
|
Edit the right-hand column to match whatever vocabulary you actually use.
|