Lucio Lelii
0fe5a0109c
The direction badge always said "Bias". It derived the direction from biasExecutionContext.activeBiasProbes, and that field is not on the bias context at all - probes belong to a step view - so the lookup was always undefined and every variant fell through to the bias branch. My own change one commit ago. A persisted snapshot settles what the payload really is: bias and mitigation are tracked in four separate collections - annotations per node and activated subflows per container, one pair for each direction. The direction is which of them are non-empty, so a variant can now correctly read as Bias, Mitigation, or Bias + mitigation, including when an intervention was switched on for a whole container subflow rather than per annotation. A variant with nothing recorded says "unspecified" instead of guessing. The model was wrong in a second way, with a second victim: activeAnnotationIdsByNode is not sent either, so the bias highlighting on graph nodes read an absent field and never lit anything up. It now combines both directions. The model is corrected to the real shape and the two absent fields are gone from it, so nothing can quietly read undefined again. The derivation lives in pure, tested helpers rather than inline, and the dev fake now splits activations by direction like the real payload - flattening them hid this very difference in development. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .vscode | ||
| docker | ||
| docs | ||
| public | ||
| src | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .postcssrc.json | ||
| Dockerfile | ||
| README.md | ||
| angular.json | ||
| components.json | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.spec.json | ||
README.md
HumAInFlow
This project was generated using Angular CLI version 21.0.3.
Development server
To start a local development server, run:
ng serveOnce the server is running, open your browser and navigate to
http://localhost:4200/. The application will automatically
reload whenever you modify any of the source files.
Code scaffolding
Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
ng generate component component-nameFor a complete list of available schematics (such as
components, directives, or
pipes), run:
ng generate --helpBuilding
To build the project run:
ng buildThis will compile your project and store the build artifacts in the
dist/ directory. By default, the production build optimizes
your application for performance and speed.
Running unit tests
To execute unit tests with the Vitest test runner, use the following command:
ng testRunning end-to-end tests
For end-to-end (e2e) testing, run:
ng e2eAngular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
Additional Resources
For more information on using the Angular CLI, including detailed command references, visit the Angular CLI Overview and Command Reference page.