fix: the compile-time gates say what they mean - #82

Merged

btravers merged 21 commits into

mainfrom

fix/gates-say-what-they-mean

Aug 21, 2026

Commits on Aug 20, 2026

fix(core)!: the start gate names what is missing
btravers
committed
cbe8e24
fix(core): the start gate's arms are asserted, and its spec says what is true
btravers
committed
f5b7d24
fix(amqp,temporal): the composer gates print a sentence, not an expansion
btravers
committed
db7223d

Commits on Aug 21, 2026

fix(http): the undeclared-key gate names the rule, not 'never'
btravers
committed
0081e05
fix(http): the undeclared-key gate names the key, and the spec quotes the real type
btravers
committed
ac12553
docs: the kernel gate's diagnostic, and di's, as measured
btravers
committed
03d1924
docs: the how-to pages say what each gate prints
btravers
committed
bab2a08
docs: the reference pages quote the gates' real diagnostics
btravers
committed
52c38e5
docs: the example walkthroughs tell the two start-time refusals apart
btravers
committed
a77b4f4
docs: the package specs name the mechanism each gate uses
btravers
committed
a85f635
docs: the example and starter comments name the mechanism, not the wrong gate
btravers
committed
905527c
docs: the READMEs say the arity gate carries the port, not prints it
btravers
committed
7d861a6
docs: the arity gate's ports are spelled out, not hovered
btravers
committed
a46909b
docs: keep-a-port-private quotes a gate that was actually run
btravers
committed
af5be64
docs: the uncovered key was re-measured on the real contracts
btravers
committed
e4bd996
docs: record what each gate printed before and after
btravers
committed
9af980d
docs: the harness gate is measured, and it is the fourth mechanism
btravers
committed
f26a4c9
docs: the example fixtures name the marker, not the rest parameter
btravers
committed
e04a755
docs: the record claims only what the diff shows
btravers
committed
ce14658
docs: a seventh site, and one shared technique instead of two copies
btravers
committed
b4aa9a0
docs: runMain's comment names the cast, not a tuple that is gone
btravers
committed
06e90d3

Navigation Menu

Uh oh!

fix: the compile-time gates say what they mean - #82

fix: the compile-time gates say what they mean#82
btravers merged 21 commits into
mainfrom
fix/gates-say-what-they-mean

Commits on Aug 20, 2026

fix(core)!: the start gate names what is missing

fix(core): the start gate's arms are asserted, and its spec says what is true

fix(amqp,temporal): the composer gates print a sentence, not an expansion

Commits on Aug 21, 2026

fix(http): the undeclared-key gate names the rule, not 'never'

fix(http): the undeclared-key gate names the key, and the spec quotes the real type

docs: the kernel gate's diagnostic, and di's, as measured

docs: the how-to pages say what each gate prints

docs: the reference pages quote the gates' real diagnostics

docs: the example walkthroughs tell the two start-time refusals apart

docs: the package specs name the mechanism each gate uses

docs: the example and starter comments name the mechanism, not the wrong gate

docs: the READMEs say the arity gate carries the port, not prints it

docs: the arity gate's ports are spelled out, not hovered

docs: keep-a-port-private quotes a gate that was actually run

docs: the uncovered key was re-measured on the real contracts

docs: record what each gate printed before and after

docs: the harness gate is measured, and it is the fourth mechanism

docs: the example fixtures name the marker, not the rest parameter

docs: the record claims only what the diff shows

docs: a seventh site, and one shared technique instead of two copies

docs: runMain's comment names the cast, not a tuple that is gone