2 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5	c2d27d9a2b	docs(ci): name the service Fabled-Git, not Forgejo ... This instance runs Gitea 1.26.4. Per the naming decision on Scribe #2272, "Fabled-Git" is the standing name for the service and the engine is named only where it is load-bearing (version-specific API behaviour, act_runner quirks, click-through UI). Service-level prose only. Deliberately NOT touched: - `.forgejo/workflows/` paths, which resolve on this Gitea only because GITEA__actions__WORKFLOW_DIRS lists them. - anything naming the upstream Forgejo PROJECT (the artifact-action forks). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-01 19:54:43 -04:00
bvandeusenandClaude Opus 4.8	31217498ce	Add Forgejo CI: ruff lint + pytest unit + gated image publish ... Family-consistent CI for StashHandler (mirrors the NhenArchiver Python sibling, minus the integration lane — StashHandler is SQLite-only with no service containers). - .forgejo/workflows/ci.yml: lint (ruff) -> unit (pytest) -> publish. publish builds + pushes git.fabledsword.com/bvandeusen/stashhandler with the family rule-46 tag scheme (dev->:dev+:c-<sha>, main->:latest+:c-<sha>, v* tag->:<version>+:latest). Gated on lint+unit. Needs REGISTRY_TOKEN. - tests/: starter unit suite — hashing, SQLite dedup, media filter, transfer modes. - pyproject.toml: ruff target + pytest pythonpath/testpaths. - ci-requirements.md (family rule 39), .dockerignore. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016nyYC9dTQ78SqhpNFtpMvT	2026-06-26 10:44:49 -04:00