Names, paths, findings and gate counts below describe the recorded tree, not today's onboarding contract.
Current contract: onboarding.
Step 4b re-measure, 2026-11-13: an ordinary popup after the contract adjustments.
A fresh child agent (Claude Opus, high reasoning) worked in a just worktree checkout with the public contracts as its brief: .system/ including the RULES "Feature files" section, Registry.qml, FeatureEntry.qml, and features/audio/ and features/osd/ as references.
It recorded its reads, gate runs, and gaps. The parent read the key hunks, removed the shared test's hard-coded feature lists, and re-ran every gate.
Result
The tray lives in features/tray/: service, new pure model tray.js with its test, panel, load target, double, and suite. Registry.qml holds one tray entry.
FeatureEntry.empty lets the host shrink a registry popup to the shared compact empty size without naming it; media is still a name case.
Bar, PopoutHost, SurfaceManager, and popoutCatalog.js no longer name the tray; IPC stays explicit in shell.qml.
The horizontal tray flow moved to features/tray/fixtures/suite.mjs; the vertical empty/repopulate check stays in tasks.mjs because feature suites cannot change the Bar orientation.
Parent re-run: just lint 0 (includes just test and three load targets), just ui-test 10/10 in 29 s. The parent viewed the populated and empty tray screenshots at 1280×720; they match the existing geometry assertions. Screenshots are evidence, not owner approval.
Against the predictions
Metric
Pilot prediction
OSD (overlay)
Tray (popup)
Production files changed outside the feature
2
8
7
Test and harness files changed
4
9
9
Host-internal files read
0
about 12
about 14
Gate runs to first green
unmeasured
11 (6 red)
9 (2 red)
Both onboardings miss the pilot's prediction by about four times. The phase exit "one registry entry plus feature-local files is the entire wiring" is not met.
Where the cost comes from
Migration debris: an existing feature carries typed injection into Bar, PopoutHost, and SurfaceManager, name cases, an inline component, and a catalog entry. The contract describes adding a feature, not removing that wiring. Each remaining legacy popup will pay it once.
Entry growth: FeatureEntry gains a field per new need (overlayShown, empty). Expected while the shape settles, but each one is a central edit.
Shared test pins: the parent removed the hard-coded name lists from ui-test.test.mjs after this run; popout-catalog.test.mjs still mirrors registry entry data, and fixtures that construct Bar and SurfaceManager follow every typed host property.
Shared task fixture: feature suites run inside tasks.qml; anything a suite cannot do (orientation) stays in tasks.mjs.
Contract gaps
Empty-state sizing was not expressible. Workaround: FeatureEntry.empty; the compact size stays host policy.
No migration guidance: legacy host wiring had to be found by reading host files.
Typed host properties fan out to every fixture that constructs Bar or SurfaceManager.
Shared tests pinned registry names, suite lists, and counts (names and lists now derived; the catalog mirror remains).
Feature suites cannot change the Bar orientation; ipc is passed to suites but undocumented.
A load target cannot call double-only methods through the typed registry service without a var alias.
Open issues
No pre-move tray screenshot exists to diff against.
Production: after the merge, the live shell's reload logged Configuration Loaded with no warnings, and read-only trayState returned the session's two real items (Nextcloud, Cachy-Update) through featureRegistry.tray. Rendered tray icons in production remain unreviewed; the fixture double has an empty icon.
Gate counts per run come from the child's own record; the parent verified only the final tree.
# Independent tray onboarding
## Historical evidence
Names, paths, findings and gate counts below describe the recorded tree, not today's onboarding contract.
Current contract: [onboarding](../../specs/NL-SPEC-A7K4QX2M-nuguland-agent-onboarding/index.md).
Step 4b re-measure, 2026-11-13: an ordinary popup after the contract adjustments.
A fresh child agent (Claude Opus, high reasoning) worked in a `just worktree` checkout with the public contracts as its brief: `.system/` including the RULES "Feature files" section, `Registry.qml`, `FeatureEntry.qml`, and `features/audio/` and `features/osd/` as references.
It recorded its reads, gate runs, and gaps. The parent read the key hunks, removed the shared test's hard-coded feature lists, and re-ran every gate.
## Result
- The tray lives in `features/tray/`: service, new pure model `tray.js` with its test, panel, load target, double, and suite. `Registry.qml` holds one tray entry.
- `FeatureEntry.empty` lets the host shrink a registry popup to the shared compact empty size without naming it; media is still a name case.
- Bar, `PopoutHost`, `SurfaceManager`, and `popoutCatalog.js` no longer name the tray; IPC stays explicit in `shell.qml`.
- The horizontal tray flow moved to `features/tray/fixtures/suite.mjs`; the vertical empty/repopulate check stays in `tasks.mjs` because feature suites cannot change the Bar orientation.
- Parent re-run: `just lint` 0 (includes `just test` and three load targets), `just ui-test` 10/10 in 29 s. The parent viewed the populated and empty tray screenshots at 1280×720; they match the existing geometry assertions. Screenshots are evidence, not owner approval.
## Against the predictions
| Metric | Pilot prediction | OSD (overlay) | Tray (popup) |
| --- | --- | --- | --- |
| Production files changed outside the feature | 2 | 8 | 7 |
| Test and harness files changed | 4 | 9 | 9 |
| Host-internal files read | 0 | about 12 | about 14 |
| Gate runs to first green | unmeasured | 11 (6 red) | 9 (2 red) |
Both onboardings miss the pilot's prediction by about four times. The phase exit "one registry entry plus feature-local files is the entire wiring" is not met.
## Where the cost comes from
- Migration debris: an existing feature carries typed injection into Bar, `PopoutHost`, and `SurfaceManager`, name cases, an inline component, and a catalog entry. The contract describes adding a feature, not removing that wiring. Each remaining legacy popup will pay it once.
- Entry growth: `FeatureEntry` gains a field per new need (`overlayShown`, `empty`). Expected while the shape settles, but each one is a central edit.
- Shared test pins: the parent removed the hard-coded name lists from `ui-test.test.mjs` after this run; `popout-catalog.test.mjs` still mirrors registry entry data, and fixtures that construct Bar and `SurfaceManager` follow every typed host property.
- Shared task fixture: feature suites run inside `tasks.qml`; anything a suite cannot do (orientation) stays in `tasks.mjs`.
## Contract gaps
1. Empty-state sizing was not expressible. Workaround: `FeatureEntry.empty`; the compact size stays host policy.
2. No migration guidance: legacy host wiring had to be found by reading host files.
3. Typed host properties fan out to every fixture that constructs Bar or `SurfaceManager`.
4. Shared tests pinned registry names, suite lists, and counts (names and lists now derived; the catalog mirror remains).
5. Feature suites cannot change the Bar orientation; `ipc` is passed to suites but undocumented.
6. A load target cannot call double-only methods through the typed registry service without a `var` alias.
## Open issues
- No pre-move tray screenshot exists to diff against.
- Production: after the merge, the live shell's reload logged `Configuration Loaded` with no warnings, and read-only `trayState` returned the session's two real items (Nextcloud, Cachy-Update) through `featureRegistry.tray`. Rendered tray icons in production remain unreviewed; the fixture double has an empty icon.
- Gate counts per run come from the child's own record; the parent verified only the final tree.