jepa-fx-risk

48 Commits 3 Branches 18 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
mathias	57b6352c98	fix(mod): move module path off the decommissioned gitea.d-ma.be host CD / Lint / Test / Vet (push) Successful in 5s Details go.mod declared this module under gitea.d-ma.be, the pre-rename host (infra ADR-0004). That name still resolves in DNS but no longer serves -- HTTPS to it fails outright -- so the declared path pointed at nothing. It built anyway, because a Go module does not have to be fetchable from its own declared path to compile locally. That is exactly what made it durable rot: nothing failed, so nothing flagged it. What it did break is anyone trying to depend on this repo -- `go get git.d-ma.be/mathias/<repo>` fails on the path mismatch, and an importer would have to spell the dead host. Verified safe before changing: nothing in the estate requires this module (checked every go.mod across the Go repos) -- these are leaf binaries, so the rename breaks no importer. Mechanical: module path plus every internal import rewritten, templ regenerated where applicable. Verified after -- go build, go vet, go test and golangci-lint (against a Go 1.26.1 toolchain, matching CI) all pass, and no gitea.d-ma.be reference remains in any .go/.templ/.mod file. Found by an estate-wide scan for the old host, prompted by the same rot turning up in tapir internal/web/views.templ (tapir@4bafd5f).	2026-09-05 14:46:41 +02:00
mathiasandClaude Sonnet 4.6	f01bdde7c2	refactor: rename hostexecutor → jepa-fx-risk (#9 ) Module path gitea.d-ma.be/mathias/hostexecutor → jepa-fx-risk. cmd/hostexecutor → cmd/jepa-fx-risk. templ upgraded 0.2.778 → 0.3.1020. Clean build + tests pass. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-24 11:58:42 +02:00
mathias	d1193a57c6	Initial commit	2026-05-27 21:55:18 +00:00

Author

SHA1

Message

Date

mathias

57b6352c98

fix(mod): move module path off the decommissioned gitea.d-ma.be host

CD / Lint / Test / Vet (push) Successful in 5s

Details

go.mod declared this module under gitea.d-ma.be, the pre-rename host
(infra ADR-0004). That name still resolves in DNS but no longer serves --
HTTPS to it fails outright -- so the declared path pointed at nothing.

It built anyway, because a Go module does not have to be fetchable from its
own declared path to compile locally. That is exactly what made it durable
rot: nothing failed, so nothing flagged it. What it did break is anyone
trying to depend on this repo -- `go get git.d-ma.be/mathias/<repo>` fails on
the path mismatch, and an importer would have to spell the dead host.

Verified safe before changing: nothing in the estate requires this module
(checked every go.mod across the Go repos) -- these are leaf binaries, so the
rename breaks no importer.

Mechanical: module path plus every internal import rewritten, templ
regenerated where applicable. Verified after -- go build, go vet, go test and
golangci-lint (against a Go 1.26.1 toolchain, matching CI) all pass, and no
gitea.d-ma.be reference remains in any .go/.templ/.mod file.

Found by an estate-wide scan for the old host, prompted by the same rot
turning up in tapir internal/web/views.templ (tapir@4bafd5f).

2026-09-05 14:46:41 +02:00

mathiasandClaude Sonnet 4.6

f01bdde7c2

refactor: rename hostexecutor → jepa-fx-risk (#9 )

Module path gitea.d-ma.be/mathias/hostexecutor → jepa-fx-risk.
cmd/hostexecutor → cmd/jepa-fx-risk. templ upgraded 0.2.778 → 0.3.1020.
Clean build + tests pass.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-24 11:58:42 +02:00

mathias

d1193a57c6

Initial commit

2026-05-27 21:55:18 +00:00