Repository navigation
0.0.1
The first release: the repository setup, the documentation site on
https://ferrofed.eu/, the architecture of record, the Cargo workspace and the
server binary's shape (configuration, telemetry, health, readiness and
shutdown). The ferrofed binary serves health and readiness only; the
federated query follows from v0.0.2.
Added
-
The Cargo workspace (#28): the root manifest with the family lint set, the
release profile and thepublish = falseswitch every library crate
inherits; theopenehr-*family declared as one lockstep pin group at 0.0.72,
with the versions guard failing when one member moves alone;deny.toml; the
serde_json::Valueban inclippy.toml; and every crate of the architecture's
crate map as a documented placeholder, with theferrofedbinary over a thin
library run path and the testkit's pin-matrix reader asserting each crate's
specification constant againstdocs/VERSIONS.md. -
The server binary shape (#29):
ferrofed serveandferrofed config check;
configuration from a TOML file andFERROFED__environment overrides with
unknown keys refused,_filesiblings for every secret, outbound
credentials per endpoint id, and a typed refusal (exit 78) on any bad value,
a broken log filter included;auto,jsonandprettyconsole formats;
GET /,GET /healthandGET /health/readinessover an indicator
registry; the request id, the panic catch (a500that carries neither the
panic message nor anything the client sent), the request timeout and the
body ceiling; a bounded drain onSIGTERM; and501for every path of the
ITS-REST surface until the façade lands. The request log records the
method, the matched route, the status, the latency and the request id, and
never a body, the AQL text, a header value, an unmatched path, or a query
value other than the digit-onlyoffsetandfetch, so a façade query's
patient identifier reaches no log line at any level (§5.4.3). -
The conformance matrix (#41):
conformance/matrix.tsvwith every
conformance point of section 17,conformance/tracks.tsvwith the section
16.3 tracks (track 8 deferred as provisional) and
conformance/requirements.tsvwith the reachability of all 46 requirements,
derived from the vendored specification byscripts/conformance/matrix.sh;
the// conformance:test marker; the tier-1conformance-matrixguard; and
the matrix rendered into the book's Evaluate part. -
The clinical-path storage rule (#40): an engine test reads the crate graph
and fails when a library crate reaches a storage implementation or the
application crate.
Fixed
scripts/checks/crate-version-guard.shno longer exits early on the change
that adds the rootCargo.toml, where the base has none.