Record supplied VoidKontrol specification and repository guidance

This commit is contained in:
Codex
2026-09-21 05:00:08 +00:00
commit 700b34fb60
5 changed files with 247 additions and 0 deletions
+14
View File
@@ -0,0 +1,14 @@
# Domain Docs
Before exploring, read root `CONTEXT.md` (or `CONTEXT-MAP.md` when present) and relevant `docs/adr/` decisions. If absent, proceed silently; domain-modeling creates them when a real terminology or decision need arises.
This is a single-context layout:
```
/
├── CONTEXT.md
├── docs/adr/
└── src/
```
Use defined glossary terms consistently, and explicitly flag conflicts with existing ADRs.
+27
View File
@@ -0,0 +1,27 @@
# Issue tracker: Gitea
Issues and specs for this repo live as Gitea issues. Use the official [`tea`](https://gitea.com/gitea/tea) CLI for all operations.
## Conventions
- **Create an issue**: `tea issues create --title "..." --description "..."`.
- **Read an issue**: `tea issues <number>`.
- **List issues**: `tea issues`; use `tea issues --state all` for all states and `tea issues --format json` for machine-readable output.
- **Comment on an issue**: `tea comment issue <number>`.
- **Apply / remove labels**: `tea issues edit <number> --add-labels "..."` / `--remove-labels "..."`.
- **Close**: `tea issues close <number>`.
- **Pull requests**: use `tea pulls create`, `tea pulls <number>`, and `tea pulls checkout <number>`.
Configure the Gitea instance with `tea login add`. `tea` uses repository context from the current clone when available.
## Merge requests as a triage surface
**Pull requests as a request surface: no.**
## When a skill says "publish to the issue tracker"
Create a Gitea issue.
## When a skill says "fetch the relevant ticket"
Run `tea issues <number>`.
+9
View File
@@ -0,0 +1,9 @@
# Triage Labels
| Canonical role | Tracker label | 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 |