7 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	4799d191a0	Fork tooling: a build check and a rename pass in the strip, a notice check in CI ... strip.py compiles the stripped tree, so a dual-licensed file that only serves an Enterprise feature fails the import instead of the merge, as v0.16.23's tests/src/directory/issuer.rs does. Upstream's tests of the features the fork rebuilt are expected not to compile there and are listed in build-check-known.txt; an error anywhere else fails the run. Checked against both imports: v0.16.22 passes with its 16 expected errors, v0.16.23 fails on issuer.rs alone. Imports the strip leaves unused are reported. It also renames the upstream name where clients, users or operators meet it as an identifier, from tools/fork/renames.py: wire-protocol names, the web interface's client id, store keys, configuration defaults and the served schema. main is renamed with the same module, so a re-import arrives purged and those lines don't conflict. notice-check.py fails CI when an upstream file the fork changed, measured against the upstream branch, lacks its AGPL 5(a) notice; --fix adds it. It runs beside the name check in a renamed fork-checks job. Also commits v0.16.23's strip report under docs/fork/strip-reports/, which the import in #18 left out.	2026-09-22 19:02:34 -07:00
jcoffey-dev	9f444d2458	Fork tooling: the third-party code upstream carries, listed and checked ... A few of upstream's dual-licensed files carry code from other projects under MIT or BSD terms. The fork redistributes it, so their licenses require the notices to travel with it. THIRD-PARTY.md reproduces them. strip.py now reads the stripped tree's comments for another copyright holder, another license, or a note that code came from somewhere else, and names any file THIRD-PARTY.md doesn't cover. It reports, never fails: the notice goes in with the merge that brings the release in. On v0.16.22 it finds 14 files, all of them covered. The rest of the report is byte-for-byte what the committed one says, so the scan disturbs nothing it already did.	2026-09-19 16:59:36 -07:00
jcoffey-dev	11d780b3d3	Copyright of the fork's own files is Coffey Labs's	2026-09-18 15:30:27 -07:00
jcoffey-dev	1c6640e4b3	Strip tooling: remove the enterprise feature from build scripts' --features lists ... Upstream's Dockerfiles and CI pass --features "... enterprise" on the cargo command line, which the manifest edits don't reach. 11 occurrences at v0.16.22. Dockerfile.build and Dockerfile.fdb are now scanned too, whatever their extension.	2026-09-18 10:52:34 -07:00
jcoffey-dev	dedcc0fe94	Move the specs under docs/spec, ahead of the source import	2026-09-18 10:21:43 -07:00
jcoffey-dev	826e8bc97f	Strip tooling: remove dangling mod declarations left by ossify.py	2026-09-18 10:20:18 -07:00
jcoffey-dev	e79036d097	Strip tooling: wrap upstream's ossify.py with export, marker checks, Cargo edits and verification	2026-09-18 10:11:57 -07:00