- logo: restore the mirrored right half — the inline mark was missing the
<use> mirror, rendering a lopsided single-page glyph
- verdict line: one uniform 22px line; counts inherit the display face
- font sizes up across the board (table 10->11px, titles 16/17->17/18px,
stat figures 17->19px, sections 10->11px)
- overview Sites table: state column widens and never wraps
- topbar: Library + Log out grouped right, matching the original chrome
- Lanes: sidecar line moved under the Poll lanes explanation
- Resume renders inside the same pausebar slot as Pause
- lane problems (refusing / no browser / not checking) render danger red;
a deliberate pause stays patina
- series notes: chips capped at two with a +N tail instead of stacking
- pending 'requested N ago' now renders once, in the action cell only
Throwaway UI prototype for issue #122: what a dense operations view
looks like without leaving Cinder. Three structural variants switchable
via ?variant=A|B|C and a floating bar:
- A: narrow 760px prose rows, no new tokens
- B: wide 1080px borderless aligned-column table
- C: wide two-line blocks
Fixes#122's question; see issue for the four open decisions.
Forge usage lived in three places (`AGENTS.md`, `docs/agents/issue-tracker.md`, and habit). This moves the how-to-run-`tea` half into a model-invoked skill that fires on any issue/PR task, and reduces `AGENTS.md` to identity plus pointers.
- **new** `.claude/skills/gitea/SKILL.md` — command table plus the traps `tea <cmd> --help` will not tell you.
- `AGENTS.md` — Forge section is now one line: Gitea not GitHub, `gh` and the `issue://`/`pr://` URIs fail, then pointers to the skill, `docs/agents/issue-tracker.md`, and `docs/agents/triage-labels.md`.
- `.claude/skills/implement-tickets/SKILL.md` — pointer split: tracker conventions to the doc, `tea` usage to the skill.
Both `docs/agents/` files are untouched; the skill cites them instead of restating them.
Facts in the skill are measured against `tea` 0.14.2 on 2026-08-17, not remembered:
- `gh` is not installed, so `read issue://71` errors — there is no fallback to add.
- **A bare read is a truncated read.** Without `--comments`, `tea issue <n>` drops every comment silently, with no prompt under a non-TTY: issue #123 prints 40 lines bare, 132 with the flag. The skill makes `--comments` mandatory for any read meant to understand a ticket, with `tea issue list --fields index,comments` as the checkable count.
- Issues and PRs share one index space; output is rendered boxes so parsing needs `-o json`; `close` takes no `--comment`; labels never auto-create; multi-line bodies need a heredoc; `tea` exposes neither sub-issues nor dependencies.
Unmeasured and marked as such: whether `--comments` covers a PR's review-comment stream — no PR in this repo has comments, so `tea pr review-comments <n>` is named without a claim about overlap.
Reviewed-on: #126
Co-authored-by: Sulthan Zaki <sultankiki05@gmail.com>
Co-committed-by: Sulthan Zaki <sultankiki05@gmail.com>
2026-08-17 17:52:16 +07:00
1 changed files with 1371 additions and 0 deletions
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
sulthan