Learnt from: CR
Repo: grimmory-tools/grimmory PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-03-26T01:46:48.863Z
Learning: PRs in this repo are expected to link an approved issue and include local test output

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 393
File: frontend/src/app/features/readers/pdf-reader/pdf-reader.component.ts:255-263
Timestamp: 2026-04-07T09:28:12.814Z
Learning: In the Grimmory frontend (Angular), always flag manual resource management patterns when automatic alternatives are available via modern Angular mechanisms. This includes, but is not limited to:
- Manual `document.addEventListener` / `removeEventListener` with stored cleanup functions (e.g., `mouseMoveCleanup`, `documentClickCleanup`, `keydownCleanup`, `touchCleanup` as fields) — prefer registering teardown via `DestroyRef.onDestroy(cleanupFn)` instead.
- Manually tracked `Subscription` fields (e.g., `annotationSaveSubscription`, `annotationCacheSubscription`) that are explicitly unsubscribed in `ngOnDestroy()` — prefer `takeUntilDestroyed(destroyRef)` piped in the stream.
- Any lifecycle-coupled teardown that can be automated through `DestroyRef`, `takeUntilDestroyed`, Angular signals, or other Angular v16+ primitives. Always flag these patterns in code under `frontend/src/app/` (Angular project in grimmory-tools/grimmory).

Learnt from: zachyale
Repo: grimmory-tools/grimmory PR: 439
File: frontend/src/app/features/series-browser/components/series-browser/series-browser.component.ts:178-196
Timestamp: 2026-04-11T03:56:00.030Z
Learning: In the Grimmory Angular frontend (frontend/src/app/), the preferred holistic approach for reactive localization (auto-updating on language switch) is: (1) Use `translateSignal()` from `jsverse/transloco` for individual reactive translated strings. (2) For option/label arrays, create a single `activeLang` signal via `toSignal(t.langChanges$, { initialValue: t.getActiveLang() })` and derive option arrays as `computed()` signals that read `activeLang()` — this eliminates all manual `langChanges$` subscriptions and `ngOnDestroy` wiring. The team explicitly prefers this signal/computed pattern over manual subscribe-in-ngOnInit approaches when implementing reactive i18n.

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 385
File: frontend/src/app/app.component.ts:55-56
Timestamp: 2026-04-05T21:16:04.342Z
Learning: In the grimmory frontend (Angular), always suggest modern Angular patterns when reviewing code. For example:
- Prefer `DestroyRef` + `takeUntilDestroyed(destroyRef)` (Angular v16+) over manually managing `Subscription` arrays and calling `unsubscribe()` in `ngOnDestroy()`.
- Prefer `inject()` for dependency injection over constructor injection.
- Prefer Angular signals and computed values over BehaviorSubjects/Observables where appropriate.

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 502
File: booklore-api/src/main/java/org/booklore/service/reader/ChapterCacheService.java:0-0
Timestamp: 2026-04-14T12:46:59.296Z
Learning: In grimmory-tools/grimmory (booklore-api), the team targets Java 25 with `--enable-preview` and actively aims to use the most modern Java conventions available. When reviewing or suggesting code for this project, always prefer modern Java 25 idioms and features (e.g., unnamed variables `_`, records, pattern matching for switch/instanceof, sealed classes, sequenced collections, `Stream.toList()`, text blocks, etc.) over older or more conservative patterns. Do not suggest reverting modern constructs to legacy alternatives.

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 334
File: booklore-api/src/main/java/org/booklore/service/reader/EpubReaderService.java:402-407
Timestamp: 2026-04-02T09:25:48.330Z
Learning: In grimmory-tools/grimmory, before commenting on any file processing code (epub or pdf), always verify the current state of the relevant upstream grimmory libraries: `grimmory-tools/epub4j` (for epub) and `grimmory-tools/PDFium4j` (for pdf). These custom libraries may have different APIs, capabilities, and limitations compared to the third-party libraries they replace. Issues about streaming, buffering, or API surface may need to be filed/addressed in those upstream repos rather than in grimmory itself.

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 334
File: booklore-api/src/main/java/org/booklore/util/koreader/EpubCfiService.java:53-62
Timestamp: 2026-04-03T09:45:37.512Z
Learning: In grimmory-tools/grimmory, always prefer throwing errors using `ApiError` (e.g., `ApiError.INVALID_INPUT.createException("...")`) instead of generic Java exceptions like `IllegalArgumentException` or `RuntimeException`. When suggesting error handling in code reviews for this project, always recommend `ApiError`-based exceptions over raw Java exceptions.

Learnt from: balazs-szucs
Repo: grimmory-tools/grimmory PR: 334
File: booklore-api/src/main/java/org/booklore/service/reader/EpubReaderService.java:402-407
Timestamp: 2026-04-02T09:25:48.330Z
Learning: In grimmory-tools/grimmory, epub processing uses `org.grimmory.epub4j` from https://github.com/grimmory-tools/epub4j. This is a grimmory-maintained fork and is fundamentally different from `io.documentnode.epub4j`. Do NOT generalize API knowledge, behavior, or limitations of `io.documentnode.epub4j` to the grimmory fork. Before raising review comments on epub-related file processing code, verify the current API and capabilities in the grimmory-tools/epub4j repository.

Learnt from: CR
Repo: grimmory-tools/grimmory PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-03-26T01:46:48.863Z
Learning: Applies to booklore-api/src/test/**/*.java : Prefer focused unit tests; use `SpringBootTest` only when the Spring context is required

Learnt from: CR
Repo: grimmory-tools/grimmory PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-03-26T01:46:48.863Z
Learning: Start from the root `Justfile` unless you have a clear reason to drop into a subproject