cb7907ef33
LOG EVIDENCE: 1. notVisible: wasVisible never set for entries already on screen at list load. Removed wasVisible guard — trackingActive (100pt scroll) is sufficient protection. 2. aboveVP: maxY never goes below 0. LazyVStack destroys views at ~maxY=0. Changed threshold from maxY<0 to maxY<30 (nearly off). 3. notDown flickering: per-entry deltas are ~1pt, causing direction to flip between down/not-down on every callback. Made direction sticky: scrollingDown stays true until 30pt of cumulative upward scroll is detected. Prevents jitter from sub-pixel noise. Removed debug logging. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Gitea CI Workflows
security.yml
Runs on push/PR to master. Three jobs:
- dependency-audit —
npm audit --audit-level=highfor budget and frontend - secret-scanning — checks for tracked .env/.db files and hardcoded secret patterns
- dockerfile-lint — verifies all Dockerfiles have
USER(non-root) andHEALTHCHECK
Runner Setup
The runner is configured in the Gitea docker-compose at /media/yusiboyz/Media/Scripts/gitea/docker-compose.yml.
What was done:
- Added
[actions] ENABLED = trueto Gitea'sapp.ini - Added
runnerservice (gitea/act_runner) to Gitea's docker-compose - Generated runner token via
docker exec -u git gitea gitea actions generate-runner-token - Token stored in
/media/yusiboyz/Media/Scripts/gitea/.envasRUNNER_TOKEN - Runner registered as
platform-runnerwith labels: ubuntu-latest, ubuntu-24.04, ubuntu-22.04
To regenerate token (if needed):
cd /media/yusiboyz/Media/Scripts/gitea
docker exec -u git gitea gitea actions generate-runner-token
# Update .env with new RUNNER_TOKEN value
docker compose up -d runner
To check runner status:
docker logs gitea-runner