From 3fd19e0bf0a9e3702578d45e2174fd4ec4d555ca Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Fri, 6 Feb 2026 18:24:19 +0000
Subject: [PATCH] chore: update known issues and remove stale lint report

- Updates KNOWN_ISSUES.md to reflect current status of unit tests and document skipped tests.
- Removes LINT_ISSUES.md as the reported lint failure (767.98px token) is no longer present.

Co-authored-by: PR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
---
 KNOWN_ISSUES.md |  9 ++++++++-
 LINT_ISSUES.md  | 20 --------------------
 2 files changed, 8 insertions(+), 21 deletions(-)
 delete mode 100644 LINT_ISSUES.md

diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md
index c47cc582..074937b0 100644
--- a/KNOWN_ISSUES.md
+++ b/KNOWN_ISSUES.md
@@ -3,7 +3,14 @@
 ## Tests
 
 ### Unit Tests
-- `npm run test:unit` consistently times out in the CI environment due to resource constraints. Targeted testing (`test:dm:unit`, `test:dm:integration`) is recommended.
+- `npm run test:unit` may time out in resource-constrained environments (like CI) when running the full suite serially. CI workflows use sharding (`test:unit:shardX`) to mitigate this. Targeted testing (`test:dm:unit`, `test:dm:integration`) is recommended for local development focus. (Last checked: 2024-05-22)
+
+### Skipped Tests
+The following tests are skipped due to flakiness or environmental issues and should be investigated:
+
+- `tests/e2e/popover.spec.ts`: `keeps the bottom-right grid menu inside the viewport` (Visual regression layout issue)
+- `tests/moderation/video-card.test.mjs`: `VideoCard block action restores trusted mute hide state after override` (Logic issue with state restoration)
+- `tests/login-modal-controller.test.mjs`: `LoginModalController shows NIP-46 handshake panel` (JSDOM async activity leak)
 
 ### Visual Regression Tests (`test:visual`)
 - **Artifact Retention**: Visual tests are configured to retain screenshots, traces, and videos on failure to assist with debugging. These artifacts can be found in `artifacts/test-results/`.
diff --git a/LINT_ISSUES.md b/LINT_ISSUES.md
deleted file mode 100644
index 68701f53..00000000
--- a/LINT_ISSUES.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# Lint Issues Report
-
-## Summary
-Automated linting and formatting checks were run. No auto-fixable formatting issues were found. However, one linting error persists which requires manual intervention.
-
-## Issues
-
-### css/tailwind.source.css
-
-The `npm run lint:tokens` check failed with the following error:
-
-```
-css/tailwind.source.css:5757 → 767.98px
-  @media (max-width: 767.98px) {
-```
-
-**Recommendation:**
-This raw measurement (`767.98px`) should be moved into `css/tokens.css` as a design token, or the linter configuration (`scripts/check-design-tokens.mjs`) should be updated to whitelist this specific value if it represents a standard responsive breakpoint for mobile layout fixes.
-
-Note: This error currently prevents `npm run lint` from completing successfully, meaning subsequent checks (`lint:tailwind-brackets`, `lint:tailwind-colors`) are skipped in the standard run script. These subsequent checks were run manually and passed.