Lucas WintherandClaude Fable 5.2
a28ee25855
Fork-only. Appends a Fork Workflow section to AGENTS.md and adds GEMINI.md, per-tool permission files and docs/ pages for agent driven development. Not for upstream. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
1.6 KiB
1.6 KiB
TODO
Fork-only durable backlog for things noticed and deliberately not fixed.
Small, specific, independently actionable. Remove only when actually done.
(In Go source, upstream's FIXME/TODO comment convention still applies.)
Now
- Install a Go toolchain on the development host (go.mod needs 1.26; CI
builds with 1.27.x). Until then every
gocommand has to run in thegolang:1.26container - seedocs/PERMISSIONS.md. - Install
golangci-lintv2 sogolangci-lint runcan be verified and moved into the Allow tier.
Next
- Propose a CI check for this fork:
AGENTS.md,CLAUDE.md,GEMINI.mdand thedocs/agent files exist, andAGENTS.mdis at most 150 lines. - Upstream CI (
.github/workflows/build.yml) is gated ongithub.repository == 'rclone/rclone'and the remote is Gitea, so this fork has no CI at all. Decide whether to add a Gitea Actions workflow.
Someday
Recurring
- Maintain
AGENTS.md:- Add a rule only in response to a real failure. Do not pre-empt hypothetical mistakes.
- Update in the same commit as the convention change.
- Prune quarterly, and re-check the Fork Workflow section against
upstream's
AGENTS.mdafter each upstream merge.
Known issues
RCLONE_CONFIG=/notfound go test ./...in the baregolang:1.26container fails 7 packages (list indocs/PERMISSIONS.md).fs/loggerneedsrsync; the mount, serve and smb failures are undiagnosed and are probably missing container tooling (FUSE, git-annex), not code. Confirm on a host with Go installed before treating a full-suite failure as a regression.