Repository navigation
Releases: Phocinae/dsh-phocinae
Releases · Phocinae/dsh-phocinae
Release list
v0.2.5
Full Changelog: v0.2.4...v0.2.5
v0.2.4
Changed
- The five READMEs carry version anchors: v1.0 / v1.0 corrected / v1.1, so
the generation of the published figures to cite is explicit, and the
pre-correction reading (0.7948 / −82% / 18%) is marked deprecated upstream —
do not cite. The v1.1 numbers themselves are unchanged from 0.2.3. bench/compare-upstream.mjsgained arowsV11group (the v1.1 figures against
what this repository already records, with the GPU-latency and flip400 claims
left UNTESTED);fetchedAtis now documented as a hard-coded snapshot, and
bench/results/upstream-comparison.jsoncarries a timeliness field. The 0.2.1
report keeps its historical numbers and is dated as a snapshot. Documentation
only — no code changes.
v0.2.3
Changed
- Published numbers refreshed to the model's v1.1 figures: typed-decisions en
0.906 / zh 0.848, and the E1 gate at τ=0.6 measured at −55.0% LLM calls (79.6%
at τ=0.5) with a 0.9936 kept-subset accuracy. Documentation only — no code
changes.
v0.2.2
Fixed
- The
phocinaeskill is registered again. 0.1.2 shipped
skills/phocinae/SKILL.mdwith nothing registering it, so the file was inert;
0.2.0 then dropped it while rewriting the entry point, which was a feature
regression rather than a cleanup. The body now lives inlib/skill.mjsand
goes through the documentedctx.skills.register()surface, awaited through
ctx.inject(['skills'], …)like the tool registry. A host without a skill
registry is not an error — the tools and the gate are unaffected.
Changed
repository,homepageandbugspoint at the canonical
Phocinae/dsh-phocinae rather than a personal mirror, so the npm page sends
readers upstream.
v0.2.1
No code change from 0.2.0: lib/guard.mjs and every other shipped module hash
identically, and the only difference between the two tarballs is the version
string.
0.2.0 was briefly marked deprecated on npm, on the strength of a 404 from the
registry's CDN for its tarball. That 404 was replication lag, not a broken
publish — the tarball serves normally now, and its lib/guard.mjs is
byte-identical to this release's — so the notice was withdrawn. 0.2.1 remains
latest only because it is the newer of two identical releases.