Stage 3: the generators run in the module of datekeys-go

Like those of stage 2, the four generators of stage 3 run in the module
of the datekeys-go next to this repository, which they import, without
changing anything there: cd ../datekeys-go && go run ../datekeys-dart/tool/
… The tag spec-v0.11 and the draft v0.12, whose packages provider, agewrap,
profile and capsule.ParsePrelude are the same, give the same output as the
committed vectors, byte for byte.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

tool/bls12381_go_vectors.go

@@ -36,14 +36,15 @@
 //     the scheme of Quicknet) under keys drawn from the seed, and the verdict
 //     of its Verify on each and on edited copies.
 //
-// The seed is fixed: the output is the same on every run. Run it from a
-// scratch module that requires the reference implementation at spec-v0.11
-// (a module scratch whose go.mod has require g.activething.com/go/DateKeys
-// v0.0.0 and replace g.activething.com/go/DateKeys => an export of that tag,
-// with its go.sum, and GOFLAGS=-mod=mod), copied into it, passing the frozen
-// file of datekeys-ts:
+// The seed is fixed: the output is the same on every run. Run it in the
+// module of the reference implementation, which it imports, without changing
+// anything there, from the datekeys-go next to this repository: at the tag
+// spec-v0.11 or at the draft v0.12, whose packages that it uses are the
+// same, and so is the output.
 //
-//	go run bls12381_go_vectors.go path/to/bls12381-vectors.json > bls12381_vectors.json
+//	cd ../datekeys-go && go run ../datekeys-dart/tool/bls12381_go_vectors.go \
+//		../datekeys-ts/src/lib/dkc/testing/bls12381-vectors.json \
+//		> ../datekeys-dart/test/vectors/bls12381_vectors.json
 package main
 
 import (

tool/ibe_go_vectors.go

@@ -31,14 +31,15 @@
 // kyber's exported tags, and checks them on every fixture against what
 // tlock.TimeUnlock unwraps and against U = r·G2. A mismatch panics.
 //
-// Run it from a scratch module that requires the reference implementation at
-// spec-v0.11 (a module scratch whose go.mod has require
-// g.activething.com/go/DateKeys v0.0.0 and replace
-// g.activething.com/go/DateKeys => an export of that tag, with its go.sum,
-// and GOFLAGS=-mod=mod), copied into it, passing the directory of the
-// official fixtures and the frozen file of datekeys-ts:
+// Run it in the module of the reference implementation, which it imports,
+// without changing anything there, from the datekeys-go next to this
+// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages
+// that it uses are the same, and so is the output.
 //
-//	go run ibe_go_vectors.go path/to/testdata/fixtures path/to/ibe-vectors.json > ibe_vectors.json
+//	cd ../datekeys-go && go run ../datekeys-dart/tool/ibe_go_vectors.go \
+//		../datekeys-dart/testdata/fixtures \
+//		../datekeys-ts/src/lib/dkc/testing/ibe-vectors.json \
+//		> ../datekeys-dart/test/vectors/ibe_vectors.json
 package main
 
 import (

tool/release_go_vectors.go

@@ -19,13 +19,13 @@
 // Each verdict is "ok", with the file key for an unwrap, or the normative
 // code and the text of the error of Go.
 //
-// Run it from a scratch module that requires the reference implementation at
-// spec-v0.11 (a module scratch whose go.mod has require
-// g.activething.com/go/DateKeys v0.0.0 and replace
-// g.activething.com/go/DateKeys => an export of that tag, with its go.sum,
-// and GOFLAGS=-mod=mod), copied into it, passing the testdata directory:
+// Run it in the module of the reference implementation, which it imports,
+// without changing anything there, from the datekeys-go next to this
+// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages
+// that it uses are the same, and so is the output.
 //
-//	go run release_go_vectors.go path/to/testdata > release_vectors.json
+//	cd ../datekeys-go && go run ../datekeys-dart/tool/release_go_vectors.go \
+//		../datekeys-dart/testdata > ../datekeys-dart/test/vectors/release_vectors.json
 package main
 
 import (

tool/tlock_go_vectors.go

@@ -21,14 +21,14 @@
 // H2, H3 and H4 are unexported in kyber; they are restated with its tags, as
 // in tool/ibe_go_vectors.go, and the decryptions above check them.
 //
-// Run it from a scratch module that requires the reference implementation at
-// spec-v0.11 (a module scratch whose go.mod has require
-// g.activething.com/go/DateKeys v0.0.0 and replace
-// g.activething.com/go/DateKeys => an export of that tag, with its go.sum,
-// and GOFLAGS=-mod=mod), copied into it, passing the frozen file of
-// datekeys-ts:
+// Run it in the module of the reference implementation, which it imports,
+// without changing anything there, from the datekeys-go next to this
+// repository: at the tag spec-v0.11 or at the draft v0.12, whose packages
+// that it uses are the same, and so is the output.
 //
-//	go run tlock_go_vectors.go path/to/tlock-vectors.json > tlock_vectors.json
+//	cd ../datekeys-go && go run ../datekeys-dart/tool/tlock_go_vectors.go \
+//		../datekeys-ts/src/lib/dkc/testing/tlock-vectors.json \
+//		> ../datekeys-dart/test/vectors/tlock_vectors.json
 package main
 
 import (