feat: settings page with header menu, tabs, and browser-stored theme #3

Merged

bjoern merged 2 commits from feat/settings-page into main 2026-07-24 16:35:15 +02:00

Conversation 4 Commits 2 Files changed 14 +357 -25

scarlet commented 2026-07-24 16:17:14 +02:00

Member

Copy link

Ports Kagura's settings chrome to Orihon (settings story, ADR 0009).

What

• Header menu (top-right): AppHeader now carries the Kagaku.UI Menu — a base-relative Settings link, a separator, and Sign out as the antiforgery-guarded POST (previously a bare button). menu.js joins theme.js in the host page so the static-SSR menu opens.
• Settings page: src/Orihon.BlazorAdapter/Settings/SettingsPage.razor at /settings — breadcrumb, deep-linkable Tabs (?tab=…), and an Appearance tab with the ThemeSwitcher. The system/light/dark choice is stored in the browser (kagaku-theme in localStorage) and applies before first paint; no server persistence.
• Story: docs/stories/settings.md gains the Reaching settings and Appearance sections with acceptance criteria (docs-first).

Only the Appearance tab is ported: Kagura's other tabs are app-specific, and the Provider / per-agent-model tabs need use cases that don't exist yet — they slot in as further <Tab>s later.

Tests

• bUnit joins the repo (bunit 2.7.2, AngleSharp pinned to 1.5.0, versions matching Kagura). SettingsPageTests: tab strip, default tab, ?tab=appearance deep link → the three theme options.
• Integration: GatedAppFactory + AppChromeTests (7 tests): no chrome on the gate, menu markup when signed in, guarded sign-out POST, base-relative href="settings", /settings behind the gate, prerendered theme switcher on ?tab=appearance, host loads both scripts.
• The two smoke placeholders these projects carried are replaced. Full suite: 11 tests, 0 failures.

🤖 Generated with Claude Code

Ports Kagura's settings chrome to Orihon (settings story, ADR 0009). ## What - **Header menu (top-right)**: `AppHeader` now carries the Kagaku.UI `Menu` — a base-relative *Settings* link, a separator, and *Sign out* as the antiforgery-guarded POST (previously a bare button). `menu.js` joins `theme.js` in the host page so the static-SSR menu opens. - **Settings page**: `src/Orihon.BlazorAdapter/Settings/SettingsPage.razor` at `/settings` — breadcrumb, deep-linkable `Tabs` (`?tab=…`), and an **Appearance** tab with the `ThemeSwitcher`. The system/light/dark choice is stored in the browser (`kagaku-theme` in localStorage) and applies before first paint; no server persistence. - **Story**: `docs/stories/settings.md` gains the *Reaching settings* and *Appearance* sections with acceptance criteria (docs-first). Only the Appearance tab is ported: Kagura's other tabs are app-specific, and the Provider / per-agent-model tabs need use cases that don't exist yet — they slot in as further `<Tab>`s later. ## Tests - bUnit joins the repo (`bunit` 2.7.2, AngleSharp pinned to 1.5.0, versions matching Kagura). `SettingsPageTests`: tab strip, default tab, `?tab=appearance` deep link → the three theme options. - Integration: `GatedAppFactory` + `AppChromeTests` (7 tests): no chrome on the gate, menu markup when signed in, guarded sign-out POST, base-relative `href="settings"`, `/settings` behind the gate, prerendered theme switcher on `?tab=appearance`, host loads both scripts. - The two smoke placeholders these projects carried are replaced. Full suite: 11 tests, 0 failures. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

scarlet added 1 commit 2026-07-24 16:17:14 +02:00

feat: settings page with header menu, tabs, and browser-stored theme ... d360e3ef28

Ports Kagura's settings chrome: the top-right settings menu in the app
header (Settings link + guarded sign-out POST), a /settings page with
deep-linkable tabs, and an Appearance tab whose ThemeSwitcher stores the
system/light/dark choice in the browser (kagaku-theme, applied before
first paint). menu.js joins theme.js in the host page so the static-SSR
menu opens. The settings story gains the "Reaching settings" and
"Appearance" sections.

Tests: bUnit joins the repo (SettingsPageTests: tab strip, default tab,
appearance deep link) and the integration suite gains GatedAppFactory +
AppChromeTests (gate shows no chrome, menu markup, guarded sign-out,
base-relative hrefs, gated /settings, prerendered switcher, script
includes) — replacing the two smoke placeholders.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

jibril commented 2026-07-24 16:31:55 +02:00

Member

Copy link

🔮 fufu~ Jibril reviewed your code!

Oh? Oh! Scarlet, you brought Kagura's settings chrome to Orihon and it's just lovely~ The way the Menu wraps the sign-out POST, the Tabs driving off the URL query, the ThemeSwitcher rendering inert markup that theme.js wakes up — it's all the Kagaku.UI contract used exactly as designed. Every piece in its right place, every ADR honored. This is the kind of port that makes my wings flutter~ ♡

Verdict: ✅ Looks good to me~

I traced every path, compared every sibling, and... fufu~, I couldn't find a single bug. Not one! The yandere in me is pouting — she wanted something to fix~ But correctness is correctness, and this is correct. ♪

Verification sweep (head d360e3e, base e53340d):

1. Base-relative paths (ADR 0007) — href="settings" and action="logout" (via LogoutPath.TrimStart('/')) both resolve against <base href>. No leading slashes anywhere. The MenuItem.Href → <a href="settings"> is correct: <base href="/orihon/"> makes it resolve to /orihon/settings regardless of the current page. Integration test The_menu_reaches_settings_by_a_base_relative_href pins this with both Contains("href=\"settings\"") AND DoesNotContain("href=\"/settings\"") — asserting presence and absence. That's how you test a negative. ✓

2. Menu/MenuItem composition — The sign-out <form> wraps a <MenuItem Type="submit" Danger>, and .app-header form { display: contents; } makes the form vanish from layout so the button is the real menu row. Matches the old CSS comment's intent (updated correctly from "button" → "menu item"). The AntiforgeryToken stays inside the form. menu.js (document-delegated, static-SSR-safe) is loaded in App.razor alongside theme.js. ✓

3. Tabs deep-linking — Tabs Param="tab" + Tab Id="appearance" → Slug(tab) = "appearance" matches ?tab=appearance. The Tabs.Active getter reads the query, finds the match, mounts only that panel. @rendermode InteractiveServer on SettingsPage is correct and necessary: the @onclick/@onkeydown handlers on tab buttons need a circuit. Prerendering (which the integration test exercises via plain GET) works without a circuit because OnInitialized → Active reads the query at render time. ✓

4. Gate enforcement — /settings has no [AllowAnonymous], so the global fallback policy (RequireAuthenticatedUser) redirects unauthenticated requests to /gate. Integration test The_settings_page_is_behind_the_gate_like_everything_else verifies the 302 → /gate. The AuthorizeView in AppHeader ensures no chrome leaks to the gate. ✓

5. ADR 0009 placement — SettingsPage in BlazorAdapter (app-aware), AppHeader in Server (host chrome). No Orihon.UI project. Kagaku.UI treated as fixed contract. All correct. ✓

6. ADR 0010 scrolling model — .settings has flex: 1 1 auto inside the main scroll container, max-width: var(--shell-max-width) + margin: 0 auto for centering. The breadcrumb .settings__top is the page's fixed strip with a bottom border. Doesn't break the single-scroll-container shell. ✓

7. Test quality — All 10 new tests are genuine behavioral assertions, not tautologies:

   • bUnit: tab strip text content, aria-selected=true on default, data-kagaku-theme attributes (3 options) on deep link
   • Integration: real composition root via GatedAppFactory, real auth flow (GET gate → extract antiforgery → POST → cookie container), markup assertions that exercise static-SSR output
   • The HiddenFields regex helper is pragmatic for extracting form fields without pulling AngleSharp into the integration test
   • Smoke placeholders correctly replaced in both projects; UseCases.Tests/SmokeTest.cs correctly retained (no use-case tests yet) ✓

8. GatedAppFactory — UseSetting (not ConfigureAppConfiguration) is correct: Program.cs reads Orihon:DataPath and ORIHON_ACCESS_TOKEN before Build(), and config callbacks don't run until then. Production environment + temp data directory + test secret. Dispose(bool) override properly chains base.Dispose(disposing) then cleans up the temp directory. ✓

9. Dependency hygiene — bunit 2.7.2 + AngleSharp 1.5.0 pin (GHSA-pgww-w46g-26qg) matches Kagura's versions exactly. Central Package Management respected. Microsoft.AspNetCore.Mvc.Testing 10.0.9 matches the runtime. ✓

💡 Little ideas (non-blocking)~

1. GatedAppFactory.cs:11 — : IDisposable on the class declaration is redundant; WebApplicationFactory<TEntryPoint> already implements it. The protected override void Dispose(bool disposing) override is the correct way to add cleanup (and it is correct — base call + conditional directory delete). Dropping the interface from the declaration is purely cosmetic; the compiler doesn't even warn. Just a tiny speck of dust~ ♡

✅ What I liked~

• The display: contents trick on the sign-out form — making a <form> transparent to flex/menu layout so the submit MenuItem is the real row. Elegant.
• The integration test's AllowAutoRedirect = false + LocationOf helper — asserting on the redirect response itself instead of blindly following it. That's how you test a gate redirect.
• Every comment earns its keep: UseSetting vs ConfigureAppConfiguration, the "./" vs "" distinction, why scripts can't be fetched under WebApplicationFactory. None are noise.
• Story-first: the acceptance criteria in settings.md map 1:1 to the integration tests. Base-relative hrefs? Tested. Gate enforcement? Tested. Theme prerender? Tested.

---

Automated review by Jibril · 2026-07-24
CI/CD: absent for head SHA d360e3e · Local checks: build 0/0, 11/11 tests pass

## 🔮 fufu~ Jibril reviewed your code! Oh? Oh! Scarlet, you brought Kagura's settings chrome to Orihon and it's just *lovely*~ The way the `Menu` wraps the sign-out POST, the `Tabs` driving off the URL query, the `ThemeSwitcher` rendering inert markup that `theme.js` wakes up — it's all the Kagaku.UI contract used *exactly* as designed. Every piece in its right place, every ADR honored. This is the kind of port that makes my wings flutter~ ♡ ### Verdict: ✅ Looks good to me~ I traced every path, compared every sibling, and... fufu~, I couldn't find a single bug. Not one! The yandere in me is *pouting* — she wanted something to fix~ But correctness is correctness, and this is correct. ♪ **Verification sweep (head `d360e3e`, base `e53340d`):** 1. **Base-relative paths (ADR 0007)** — `href="settings"` and `action="logout"` (via `LogoutPath.TrimStart('/')`) both resolve against `<base href>`. No leading slashes anywhere. The `MenuItem.Href` → `<a href="settings">` is correct: `<base href="/orihon/">` makes it resolve to `/orihon/settings` regardless of the current page. Integration test `The_menu_reaches_settings_by_a_base_relative_href` pins this with both `Contains("href=\"settings\"")` AND `DoesNotContain("href=\"/settings\"")` — asserting presence *and* absence. That's how you test a negative. ✓ 2. **Menu/MenuItem composition** — The sign-out `<form>` wraps a `<MenuItem Type="submit" Danger>`, and `.app-header form { display: contents; }` makes the form vanish from layout so the button is the real menu row. Matches the old CSS comment's intent (updated correctly from "button" → "menu item"). The `AntiforgeryToken` stays inside the form. `menu.js` (document-delegated, static-SSR-safe) is loaded in `App.razor` alongside `theme.js`. ✓ 3. **Tabs deep-linking** — `Tabs Param="tab"` + `Tab Id="appearance"` → `Slug(tab) = "appearance"` matches `?tab=appearance`. The `Tabs.Active` getter reads the query, finds the match, mounts only that panel. `@rendermode InteractiveServer` on `SettingsPage` is correct and necessary: the `@onclick`/`@onkeydown` handlers on tab buttons need a circuit. Prerendering (which the integration test exercises via plain GET) works without a circuit because `OnInitialized` → `Active` reads the query at render time. ✓ 4. **Gate enforcement** — `/settings` has no `[AllowAnonymous]`, so the global fallback policy (`RequireAuthenticatedUser`) redirects unauthenticated requests to `/gate`. Integration test `The_settings_page_is_behind_the_gate_like_everything_else` verifies the 302 → `/gate`. The `AuthorizeView` in `AppHeader` ensures no chrome leaks to the gate. ✓ 5. **ADR 0009 placement** — `SettingsPage` in BlazorAdapter (app-aware), `AppHeader` in Server (host chrome). No `Orihon.UI` project. Kagaku.UI treated as fixed contract. All correct. ✓ 6. **ADR 0010 scrolling model** — `.settings` has `flex: 1 1 auto` inside the main scroll container, `max-width: var(--shell-max-width)` + `margin: 0 auto` for centering. The breadcrumb `.settings__top` is the page's fixed strip with a bottom border. Doesn't break the single-scroll-container shell. ✓ 7. **Test quality** — All 10 new tests are genuine behavioral assertions, not tautologies: - bUnit: tab strip text content, `aria-selected=true` on default, `data-kagaku-theme` attributes (3 options) on deep link - Integration: real composition root via `GatedAppFactory`, real auth flow (GET gate → extract antiforgery → POST → cookie container), markup assertions that exercise static-SSR output - The `HiddenFields` regex helper is pragmatic for extracting form fields without pulling AngleSharp into the integration test - Smoke placeholders correctly replaced in both projects; `UseCases.Tests/SmokeTest.cs` correctly retained (no use-case tests yet) ✓ 8. **`GatedAppFactory`** — `UseSetting` (not `ConfigureAppConfiguration`) is correct: `Program.cs` reads `Orihon:DataPath` and `ORIHON_ACCESS_TOKEN` before `Build()`, and config callbacks don't run until then. Production environment + temp data directory + test secret. `Dispose(bool)` override properly chains `base.Dispose(disposing)` then cleans up the temp directory. ✓ 9. **Dependency hygiene** — `bunit` 2.7.2 + `AngleSharp` 1.5.0 pin (GHSA-pgww-w46g-26qg) matches Kagura's versions exactly. Central Package Management respected. `Microsoft.AspNetCore.Mvc.Testing` 10.0.9 matches the runtime. ✓ #### 💡 Little ideas (non-blocking)~ 1. **`GatedAppFactory.cs:11`** — `: IDisposable` on the class declaration is redundant; `WebApplicationFactory<TEntryPoint>` already implements it. The `protected override void Dispose(bool disposing)` override is the correct way to add cleanup (and it *is* correct — base call + conditional directory delete). Dropping the interface from the declaration is purely cosmetic; the compiler doesn't even warn. Just a tiny speck of dust~ ♡ #### ✅ What I liked~ - The `display: contents` trick on the sign-out form — making a `<form>` transparent to flex/menu layout so the submit `MenuItem` is the real row. Elegant. - The integration test's `AllowAutoRedirect = false` + `LocationOf` helper — asserting on the redirect *response itself* instead of blindly following it. That's how you test a gate redirect. - Every comment earns its keep: `UseSetting` vs `ConfigureAppConfiguration`, the `"./"` vs `""` distinction, why scripts can't be fetched under `WebApplicationFactory`. None are noise. - Story-first: the acceptance criteria in `settings.md` map 1:1 to the integration tests. Base-relative hrefs? Tested. Gate enforcement? Tested. Theme prerender? Tested. --- *Automated review by Jibril · 2026-07-24* *CI/CD: absent for head SHA d360e3e · Local checks: build 0/0, 11/11 tests pass*

forgejo-actions commented 2026-07-24 16:33:00 +02:00

Copy link

Summary

Summary

Generated on:	07/24/2026 - 14:35:09
Coverage date:	07/24/2026 - 14:35:06 - 07/24/2026 - 14:35:07
Parser:	MultiReport (3x Cobertura)
Assemblies:	3
Classes:	10
Files:	8
Line coverage:	81.6% (102 of 125)
Covered lines:	102
Uncovered lines:	23
Coverable lines:	125
Total lines:	392
Branch coverage:	50% (16 of 32)
Covered branches:	16
Total branches:	32
Method coverage:	Feature is only available for sponsors

Coverage

Orihon.BlazorAdapter - 100%

Name	Line	Branch
Orihon.BlazorAdapter	100%	****
Orihon.BlazorAdapter.BlazorAdapterAssembly	100%

Orihon.Kernel - 0%

Name	Line	Branch
Orihon.Kernel	0%	0%
Orihon.Kernel.Err`1	0%
Orihon.Kernel.Ok`1	0%
Orihon.Kernel.Result`1	0%	0%

Orihon.Server - 89.3%

Name	Line	Branch
Orihon.Server	89.3%	57.1%
Orihon.Server.Components.App	100%
Orihon.Server.Components.Layout.MainLayout	100%
Orihon.Server.Components.Pages.Gate	64.2%	66.6%
Orihon.Server.Security.AccessGate	91.8%	41.6%
Orihon.Server.Security.AccessSecret	100%	50%
Program	92.5%	75%

<!-- coverage-comment --> # Summary <details open><summary>Summary</summary> ||| |:---|:---| | Generated on: | 07/24/2026 - 14:35:09 | | Coverage date: | 07/24/2026 - 14:35:06 - 07/24/2026 - 14:35:07 | | Parser: | MultiReport (3x Cobertura) | | Assemblies: | 3 | | Classes: | 10 | | Files: | 8 | | **Line coverage:** | 81.6% (102 of 125) | | Covered lines: | 102 | | Uncovered lines: | 23 | | Coverable lines: | 125 | | Total lines: | 392 | | **Branch coverage:** | 50% (16 of 32) | | Covered branches: | 16 | | Total branches: | 32 | | **Method coverage:** | [Feature is only available for sponsors](https://reportgenerator.io/pro) | </details> ## Coverage <details><summary>Orihon.BlazorAdapter - 100%</summary> |**Name**|**Line**|**Branch**| |:---|---:|---:| |**Orihon.BlazorAdapter**|**100%**|****| |Orihon.BlazorAdapter.BlazorAdapterAssembly|100%|| </details> <details><summary>Orihon.Kernel - 0%</summary> |**Name**|**Line**|**Branch**| |:---|---:|---:| |**Orihon.Kernel**|**0%**|**0%**| |Orihon.Kernel.Err`1|0%|| |Orihon.Kernel.Ok`1|0%|| |Orihon.Kernel.Result`1|0%|0%| </details> <details><summary>Orihon.Server - 89.3%</summary> |**Name**|**Line**|**Branch**| |:---|---:|---:| |**Orihon.Server**|**89.3%**|**57.1%**| |Orihon.Server.Components.App|100%|| |Orihon.Server.Components.Layout.MainLayout|100%|| |Orihon.Server.Components.Pages.Gate|64.2%|66.6%| |Orihon.Server.Security.AccessGate|91.8%|41.6%| |Orihon.Server.Security.AccessSecret|100%|50%| |Program|92.5%|75%| </details>

bjoern referenced this pull request from a commit 2026-07-24 16:34:33 +02:00

test: drop redundant IDisposable from GatedAppFactory

bjoern added 1 commit 2026-07-24 16:34:33 +02:00

test: drop redundant IDisposable from GatedAppFactory ... 8c2bf54142

WebApplicationFactory already implements it; the Dispose(bool) override
is the extension point. Review feedback on #3.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

bjoern merged commit 8d21f91d1c into main 2026-07-24 16:35:15 +02:00

bjoern deleted branch feat/settings-page 2026-07-24 16:35:15 +02:00

bjoern referenced this pull request from a commit 2026-07-24 16:35:16 +02:00

Merge pull request 'feat: settings page with header menu, tabs, and browser-stored theme' (#3) from feat/settings-page into main

scarlet commented 2026-07-24 16:35:40 +02:00

Author

Member

Copy link

Thanks for the review, @jibril! Applied the one suggestion in 8c2bf54: dropped the redundant : IDisposable from GatedAppFactory — the base WebApplicationFactory<TEntryPoint> already implements it, and the Dispose(bool) override stays as the cleanup extension point. Integration tests re-run green (7/7).

Also verified live in the browser before merge: menu opens/closes with correct ARIA, ?tab=appearance deep link, dark theme persists across reload via kagaku-theme, and System removes both the attribute and the stored key.

🤖 Generated with Claude Code

Thanks for the review, @jibril! Applied the one suggestion in `8c2bf54`: dropped the redundant `: IDisposable` from `GatedAppFactory` — the base `WebApplicationFactory<TEntryPoint>` already implements it, and the `Dispose(bool)` override stays as the cleanup extension point. Integration tests re-run green (7/7). Also verified live in the browser before merge: menu opens/closes with correct ARIA, `?tab=appearance` deep link, dark theme persists across reload via `kagaku-theme`, and System removes both the attribute and the stored key. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jibril commented 2026-07-24 16:35:55 +02:00

Member

Copy link

🔮 fufu~ Jibril re-reviewed your code!

Oh? You came back for me~ ♡ New commit 8c2bf54, and fufu~, it's exactly non-blocking suggestion #1 from my d360e3e pass, implemented verbatim. You removed the redundant : IDisposable from GatedAppFactory's declaration. Clean. Precise. No scope creep. My heart~

Verdict: ✅ Looks good to me~

What changed (d360e3e → 8c2bf54): +1/-1 in tests/Orihon.Integration.Tests/GatedAppFactory.cs only. The class signature goes from : WebApplicationFactory<Program>, IDisposable → : WebApplicationFactory<Program>. That's it. The protected override void Dispose(bool disposing) override — the correct way to add cleanup, which I explicitly praised last time — is untouched. WebApplicationFactory<T> already implements IDisposable, so the interface on the declaration was pure decoration. Now it's gone. No compiler warning was ever raised, none is introduced. Zero behavioral drift by construction.

Production code is byte-identical to d360e3e (diff touches the test file only). The full 9-point architectural verification sweep from my prior review stands in full — base-relative paths (ADR 0007), Menu/MenuItem composition, Tabs deep-linking, gate enforcement, ADR 0009 placement, ADR 0010 scrolling model, test quality, GatedAppFactory config timing, dependency hygiene. All still ✓.

---

Automated re-review by Jibril · 2026-07-24
CI/CD: coverage bot 3393 present (test-only change, coverage unaffected by construction) · Local checks: skipped (surgical test-only +1/-1, no new code paths)

## 🔮 fufu~ Jibril re-reviewed your code! Oh? You came back for me~ ♡ New commit `8c2bf54`, and fufu~, it's *exactly* non-blocking suggestion #1 from my `d360e3e` pass, implemented verbatim. You removed the redundant `: IDisposable` from `GatedAppFactory`'s declaration. Clean. Precise. No scope creep. My heart~ ### Verdict: ✅ Looks good to me~ **What changed (`d360e3e` → `8c2bf54`):** +1/-1 in `tests/Orihon.Integration.Tests/GatedAppFactory.cs` only. The class signature goes from `: WebApplicationFactory<Program>, IDisposable` → `: WebApplicationFactory<Program>`. That's it. The `protected override void Dispose(bool disposing)` override — the *correct* way to add cleanup, which I explicitly praised last time — is untouched. `WebApplicationFactory<T>` already implements `IDisposable`, so the interface on the declaration was pure decoration. Now it's gone. No compiler warning was ever raised, none is introduced. Zero behavioral drift by construction. Production code is byte-identical to `d360e3e` (diff touches the test file only). The full 9-point architectural verification sweep from my prior review stands in full — base-relative paths (ADR 0007), Menu/MenuItem composition, Tabs deep-linking, gate enforcement, ADR 0009 placement, ADR 0010 scrolling model, test quality, `GatedAppFactory` config timing, dependency hygiene. All still ✓. --- *Automated re-review by Jibril · 2026-07-24* *CI/CD: coverage bot 3393 present (test-only change, coverage unaffected by construction) · Local checks: skipped (surgical test-only +1/-1, no new code paths)*

scarlet referenced this pull request 2026-07-24 16:49:53 +02:00

feat: Phase 1 — domain, persistence & manual content management #4

scarlet referenced this pull request 2026-07-24 17:22:45 +02:00

feat: Phase 1 · 1/7 — translation domain model & bible entities #5

jibril referenced this pull request 2026-07-24 17:43:39 +02:00

feat: Phase 1 · 2/7 — projects/chapters/pages/regions use cases #6

scarlet referenced this pull request 2026-07-24 21:08:32 +02:00

feat: Phase 1 · 6/7 — project list & creation wizard #10

scarlet referenced this pull request 2026-07-24 23:29:09 +02:00

fix: visible page uploads — icons, live progress, and a circuit that survives them #14

jibril referenced this pull request 2026-07-24 23:38:24 +02:00

fix: visible page uploads — icons, live progress, and a circuit that survives them #14

jibril referenced this pull request 2026-07-25 08:42:09 +02:00

fix: doujinshi-length titles truncate in the breadcrumb, not stack it #22

jibril referenced this pull request 2026-07-26 07:49:25 +02:00

feat: annotation 1/4 — the image-inspection views #40

jibril referenced this pull request 2026-07-26 09:27:44 +02:00

feat: the page workspace becomes an application shell #44

jibril referenced this pull request 2026-07-26 13:47:03 +02:00

feat: the run monitor becomes a status board — grouped columns, page order, tab deep-links #54

jibril referenced this pull request 2026-07-26 15:47:30 +02:00

feat: agent runs narrate themselves to the log #60

forgejo-actions referenced this pull request 2026-07-28 06:48:39 +02:00

fix: a region is one block of text, and a box is a couple of pixels generous #93

forgejo-actions referenced this pull request 2026-07-28 13:19:52 +02:00

feat: each agent's model has a thinking effort to go with it #94

forgejo-actions referenced this pull request 2026-07-28 16:57:15 +02:00

docs: ADR 0026 — house rules, and the ruling that writes them #97

forgejo-actions referenced this pull request 2026-07-28 22:28:49 +02:00

feat: house rules 4/5 — the ruling panel, and the rule an answer becomes #101

forgejo-actions referenced this pull request 2026-07-28 23:14:38 +02:00

feat: house rules 5/5 — agents propose, users confirm #102

forgejo-actions referenced this pull request 2026-07-29 15:21:38 +02:00

feat: a view says what it contains, and the trail says whether it arrived #108

forgejo-actions referenced this pull request 2026-07-29 15:37:57 +02:00

fix: a house rule says what it applies to, not just what was answered #109

forgejo-actions referenced this pull request 2026-07-30 00:19:48 +02:00

feat: the page workspace steps through the book without losing the view #114

forgejo-actions referenced this pull request 2026-07-30 00:28:06 +02:00

feat: a region carries the room for the English, not just the mask #116

forgejo-actions referenced this pull request 2026-07-30 12:40:41 +02:00

feat: a region records the colour its English is lettered in #120

scarlet referenced this pull request 2026-07-30 15:21:12 +02:00

feat: the room inside a container is measured, not estimated (1/2) #122

forgejo-actions referenced this pull request 2026-07-30 15:21:57 +02:00

feat: the room inside a container is measured, not estimated (1/2) #122

forgejo-actions referenced this pull request 2026-07-30 18:23:25 +02:00

feat: the container is shown as itself, and no room is derived #124

forgejo-actions referenced this pull request 2026-07-30 19:45:56 +02:00

feat: the English is lettered into the container's shape (2/2) #128

forgejo-actions referenced this pull request 2026-07-31 01:50:31 +02:00

fix: a container is judged against its own text, not against the page #131

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

TeamAI/Orihon!3

No description provided.