feat: tasks app, security hardening, mobile fixes, iOS app shell
- Custom SQLite task manager replacing TickTick wrapper - 73 tasks migrated from TickTick across 15 projects - RRULE recurrence engine with lazy materialization - Dashboard tasks widget (desktop sidebar + mobile card) - Tasks page with project tabs, add/edit/complete/delete - Security: locked ports to localhost, removed old containers - Gitea Actions runner configured and all 3 CI jobs passing - Fixed mobile overflow on dashboard cards - iOS Capacitor app shell (Second Brain) - Frontend/backend guide docs for adding new services - TickTick Google Calendar sync re-authorized Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
33
claude.txt
Normal file
33
claude.txt
Normal file
@@ -0,0 +1,33 @@
|
||||
Issue `#8` is the remaining CI/security automation task.
|
||||
|
||||
Current state:
|
||||
- Repo-side workflow already exists at `.gitea/workflows/security.yml`
|
||||
- Runner setup notes already exist at `.gitea/README.md`
|
||||
- The missing piece is operational: a Gitea Actions runner is not configured, so the workflow does not execute
|
||||
|
||||
Your job:
|
||||
1. Re-verify the current repo state before changing anything.
|
||||
2. Review:
|
||||
- `.gitea/workflows/security.yml`
|
||||
- `.gitea/README.md`
|
||||
3. Add the minimal files, scripts, or compose service needed to make Gitea runner setup easy for this environment.
|
||||
4. Document exact setup steps for running a Gitea Actions runner against this Gitea instance.
|
||||
5. If live access is available, verify the runner can register and that the workflow actually executes.
|
||||
6. Do not mark issue `#8` complete unless workflow execution is confirmed. Otherwise keep it `Partial` or `Blocked`.
|
||||
|
||||
What `#8` means:
|
||||
- Automatically run dependency audits
|
||||
- Automatically scan for tracked secrets/runtime DB files
|
||||
- Automatically check Dockerfiles for non-root `USER` and `HEALTHCHECK`
|
||||
|
||||
Important constraints:
|
||||
- Do not overstate completion
|
||||
- Separate repo-side completion from operational completion
|
||||
- If a runner token or Gitea admin action is required, document that as a manual step
|
||||
- Do not change admin credentials during this pass
|
||||
|
||||
Expected output:
|
||||
- `Completed:`
|
||||
- `Partial:`
|
||||
- `Blocked:`
|
||||
- `Manual ops actions:`
|
||||
Reference in New Issue
Block a user