Skip to content

chore: release 1.3.0 - #107

Merged
omob merged 1 commit into
mainfrom
chore/release-1.3.0
Jul 7, 2026
Merged

chore: release 1.3.0#107
omob merged 1 commit into
mainfrom
chore/release-1.3.0

Conversation

@omob

@omob omob commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Minor release (per VERSIONING.md) covering the efficacy-validation-driven work merged in #100#106.

Version: 1.2.0 → 1.3.0 across package.json (RDA), paa-service, frontend, and README install pins.

CHANGELOG [1.3.0] documents:

  • Added — behavioral rule pack (velocity/fan-out → REVIEW, recall 0→0.80 with zero added FP), context-field dropout augmentation, context-sensitivity probe.
  • Changed (fresh-install behaviour) — demo rules seed inactive by default; db-migrate now registers the default model + segment thresholds; calendar features computed from event-time ms.
  • Notes — upgraders see a one-time context-sensitivity warning (the probe working).

Also records the measured context-dropout trial in CONTEXT_DROPOUT_RETRAIN.md: gap 0.9998→0.0009 (mechanism works) but typology recall unchanged on context-signalled synthetic data — it needs behavioural-fraud labels. Candidate was not deployed.

Not a major: no API/schema/Kafka breaks; both seed changes skip existing rows, so upgrades are non-destructive.

🤖 Generated with Claude Code

Version bump across RDA/PAA/Sentinel packages and README pins. CHANGELOG
[1.3.0] documents the efficacy-validation-driven fixes (demo rules
opt-in, db-migrate model seed, calendar timestamp units) and additions
(behavioral rule pack, context-dropout augmentation, context-sensitivity
probe), with the fresh-install behaviour changes called out.

Also records the measured context-dropout trial in
CONTEXT_DROPOUT_RETRAIN.md: the mechanism closes the context gap
0.9998 -> 0.0009 but does not add behavioural typology recall on
context-signalled training data — it needs behavioural-fraud labels.
@omob
omob merged commit 5f1dcca into main Jul 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant