@adia-ai/adia-ui-forge 0.8.28 → 0.8.30
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "adia-ui-kit-forge",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.30",
|
|
4
4
|
"description": "Maintain the adia-ui (@adia-ai) framework itself \u2014 author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-factory (the consumer/app-author plugin).",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Kim",
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# Changelog — adia-ui-kit-forge
|
|
2
2
|
|
|
3
|
+
## [0.8.30] — 2026-08-07
|
|
4
|
+
|
|
5
|
+
### Maintenance
|
|
6
|
+
- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.30 work shipped in agent-harness v1 wave: MCP-client mode, guardrails/tracing/memory hardening, auto engine, chat agent-event rendering, human feedback loop. See `packages/agent/CHANGELOG.md#0830--2026-08-07` for details.
|
|
7
|
+
- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
|
|
8
|
+
- **`skills/` touched in this release window** (1 file(s), e.g. `references/mcp-pipeline-ops.md`) — carried by the entries above.
|
|
9
|
+
|
|
10
|
+
## [0.8.29] — 2026-08-06
|
|
11
|
+
|
|
12
|
+
### Maintenance
|
|
13
|
+
- **Lockstep version bump only.** No source changes in this package; bumped to maintain the lockstep version coherence enforced by `scripts/release/check-lockstep.mjs`. Substantive v0.8.29 work shipped in web-components (icon-ui tone prop gh#652) + web-modules (plan-envelope chrome gh#648) + a2ui-runtime (registry drift fix gh#645) + a2ui-compose (plan-turn executor gh#648) + a2ui-corpus (chunk re-harvest). See `0829--2026-08-06` for details.
|
|
14
|
+
- **`.claude-plugin/plugin.json` version bump** — moves in lockstep with package.json (the `/plugin update` cache key).
|
|
15
|
+
|
|
3
16
|
## [0.8.28] — 2026-08-05
|
|
4
17
|
|
|
5
18
|
### Maintenance
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adia-ai/adia-ui-forge",
|
|
3
|
-
"version": "0.8.
|
|
3
|
+
"version": "0.8.30",
|
|
4
4
|
"description": "Maintain the adia-ui (@adia-ai) framework itself \u2014 author primitives and shells, run the A2UI generation pipeline and its corpus, review gen-UI quality, sweep QA, cut releases, deploy. The maintainer counterpart to adia-factory (the consumer/app-author plugin).",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"adia-ui",
|
|
@@ -81,3 +81,28 @@ Score runs with `submit_feedback` keyed on the `executionId` from
|
|
|
81
81
|
(≥95 score + ≥4 rating across 3+ runs → `npm run feedback:promote`), and the
|
|
82
82
|
gap registry (`packages/a2ui/corpus/gaps/registry.json`).
|
|
83
83
|
`npm run feedback:report` surfaces the current state.
|
|
84
|
+
|
|
85
|
+
### Human signal (gh#668)
|
|
86
|
+
|
|
87
|
+
Every score in the store except a rating is self-graded — the validator marking
|
|
88
|
+
its own homework. Human thumbs are the only outside signal, and they arrive two
|
|
89
|
+
ways, both through the SAME function
|
|
90
|
+
(`packages/a2ui/retrieval/feedback/submit-feedback.js`) into the same JSONL:
|
|
91
|
+
|
|
92
|
+
- `submit_feedback` (MCP), and
|
|
93
|
+
- `POST /api/feedback` from a rendered surface — today the gen-UI gallery's
|
|
94
|
+
`<agent-feedback-bar-ui>` row (thumbs-up = rating 5, thumbs-down = 2).
|
|
95
|
+
|
|
96
|
+
`get_training_gaps` ranks weak domains on `blendedScore`
|
|
97
|
+
(`retrieval/feedback/human-signal.js`): `0.7 * humanScore + 0.3 * selfScore`
|
|
98
|
+
where a domain has both signals, `humanScore` alone where it has no self-grade,
|
|
99
|
+
`selfScore` alone where it has no thumbs. **A missing signal is not a zero** —
|
|
100
|
+
weighting an absent self-grade as 0 would rank a domain humans unanimously
|
|
101
|
+
approved below an unrated one the validator liked. So a domain the pipeline
|
|
102
|
+
scores 99 and humans thumb down ranks weak, not strong; `selfScore` averages
|
|
103
|
+
execution scores plus any `score` a rating carries inline, and `engine` /
|
|
104
|
+
`strategy` are triage context on the log, not blend inputs.
|
|
105
|
+
|
|
106
|
+
Verify the whole loop in a browser with `npm run probe:feedback-loop`. It is
|
|
107
|
+
scratch-by-default (temp store + temp screenshot dir); `PORT=…` if 3456 is
|
|
108
|
+
taken, `PROBE_REAL_STORE=1` to write the actual corpus feedback log.
|