Track WP26 CubeSat and stakeholder-chain editor feedback #35

Track Zargham’s 2026-11-10 CubeSat/stakeholder-model feedback against the view editor. This is intake, not evidence that maintainers have reproduced or accepted every reported expectation.

Report pinned to the reported revision · 31 screenshots · Model sources.

Reported bugs and missing capabilities

• Investigate stale exploration error banner after successful source apply #14 — Bug 1; suggestion 6
• Make recovery snapshot identity and freshness clear before restoring #15 — Bug 2; suggestion 6
• Add a source file to an existing project from Explorer #16 — Bug 3; suggestion 7
• Render analysis and verification cases with their usage context and evidence pointers #17 — Bug 4; suggestion 1; feature F-5
• Investigate missing inherited parts in interconnection views of typed usages #18 — Bug 5; suggestion 8
• Clarify and verify exposure/filter scope across diagram representations #19 — Bug 6; suggestion 8
• Investigate wildcard exposure expanding private imports and standard libraries #20 — Bug 7
• Investigate inherited-name rejection for verify relationships in typed verification objectives #21 — Bug 8
• Investigate duplicate-name rejection for verify targets with the same short name #22 — Bug 9
• Explain competing-tab recovery conflicts and the effect of Retry recovery #23 — Bug 10; related Bug 2

Stakeholder-to-evidence chain

F-5 is combined with Bug 4 above because they require the same case-rendering capability.

• Show authored attribute values on overview and configuration nodes #24 — Feature F-1; suggestion 4; section 2 item 8
• Expose verification evidence and environment attributes in requirements inspection #25 — Feature F-2; suggestion 2
• Include concerns and stakeholder context in requirements inspection #26 — Feature F-3
• Render concern stakeholder bindings to their bound parts #27 — Feature F-4

Other actionable suggestions and reading workflows

• Expose attribute documentation and metadata during diagram inspection #28 — Suggestion 3; section 2 item 9
• Visualize calculation dependencies and their model consumers #29 — Suggestion 5; Bug 4 workaround
• Make large interconnection and stakeholder views readable on entry #30 — Suggestion 9; section 2 items 7 and 13
• Improve available diagram space and panel discoverability at narrow widths #31 — Suggestion 10; section 2 item 10
• Clarify Code, Split and Diagram layout controls for first-time readers #32 — Suggestion 11; section 2 item 12
• Make table and model-tree selection reveal useful, predictable details #33 — Suggestion 11; section 2 items 14–16
• Distinguish rendering and inspection activity from unapplied source drafts #34 — Suggestion 11; section 2 item 17

Evidence and scope rules

• Bug 1 did not reproduce in the report’s cold pass. Bug 2 may reflect the last successful save, and later instances followed a competing-tab save failure; silent loss has not been established.
• Bugs 8–9 are parser disagreements requiring authoritative semantic analysis. Another parser accepting source does not establish correctness.
• Bug 6 compares different filters/projections; verify exposure, filter and representation semantics independently before treating the difference as a defect.
• The app already supports multi-file import. Bug 3 requests adding files to an existing open project.
• The dated hosted build was not identified by commit. Compare each finding with an exact current build and engine pins before claiming a fix or deployment.
• The report’s screenshot-lag observation (section 2 item 11) has no established editor cause. Qualify whether it belongs to the browser/automation capture surface before filing a product defect. External tab navigation/interference was explicitly excluded by the report.
• Preserve the successes: named views, source/issue inspection, requirements and negated satisfaction, CSV/matrix workflows, and the distinction between declared verification and executed results.
• No delivery dates, assignments, conformance decisions, local reproductions or deployed fixes are implied by this intake. The editor guide merged in PR feat: add optional accessible editor guide #13 addresses discoverability, not proof that the reported usability concerns are resolved.

Issues were requested in this repository only; no GitHub Project board was created or populated.

Implementation update — 2026-11-11

• Investigate stale exploration error banner after successful source apply #14 and Investigate missing inherited parts in interconnection views of typed usages #18 are implemented and locally verified; PR #37 into develop is pending hosted checks at head 618e776. Issues were closed at the requester’s direction; merge/deployment are not claimed. The synchronization commit has the same file tree as tested 3ca0d7f. Verification and limits.
• Make recovery snapshot identity and freshness clear before restoring #15 and Explain competing-tab recovery conflicts and the effect of Retry recovery #23 are closed after PR #36 merged into develop as 2f58240 on 2026-11-11. Deployment is not established.
• Investigate wildcard exposure expanding private imports and standard libraries #20 remains open: immediate exposure can legitimately include private imported memberships, while a separate intermediate-import admission defect is reproduced. Investigation and retained upstream reproduction. No safe resolver fix is integrated.
• The other items remain open. No claim that all WP26 feedback is resolved or that a hosted deployment changed.