Skip to content

Round 8 + final review fixes: captain prepares, engine room runs; clean demo; SECURITY.md (merge after Codex MERGE-FÄHIG + green CI, merge commit) - #7

Merged
lukisch merged 4 commits into
mainfrom
fix/gui-round8-20261013
Oct 13, 2026
Merged

lukisch merged 4 commits into
mainfrom
fix/gui-round8-20261013

Conversation

@lukisch

@lukisch lukisch commented Oct 13, 2026

Copy link
Copy Markdown
Member

Merge condition

Merge only after the second-model review (Codex) says MERGE-FÄHIG and the ci checks of this PR's head are green. Use a merge commit (no squash). Owner decision D-048: Codex may merge this PR after that review; nobody merges by admin.

What this is

Round 8 of the owner's GUI test and the fixes from the final acceptance review, on top of #6.

  • The captain only prepares (owner: "Run it ... schlecht gewählt"): a plan of several steps is kept as one new workflow under My use cases, its steps go to the job inbox, step 1 loads into the engine room, and the engine room names the workflow and runs all steps in order on request. Preparing the same plan again reuses that workflow.
  • "+ New use case" / "+ New blueprint" from a name and a first step; echo sounding on Folders; the notebook tile says "Start".
  • Local model servers that do not answer stay listed at the captain as "not reachable right now"; the approval checkbox sits next to its sentence.
  • Public demo: full-console controls that answered 404 there (captain, working folders, echo, new/adopt/remove, policy editor) are hidden in the demo; a click sweep over all seven demo views finds no 4xx and no page error.
  • SECURITY.md: the four mail addresses were on non-existent domains (ellmos.ai, open-bricks.org) or a domain without MX (lukasgeiger.com); GitHub private vulnerability reporting (enabled) is the only channel named.
  • README EN/DE follow the above.

Evidence

Local full suite 1187 passed, 2 skipped. Browser checks of every changed flow (Playwright) against the live console and a demo server.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HwEgw7w5b64hDRLmCG3okz

Lukas Geiger and others added 3 commits October 13, 2026 08:40
Lukas's GUI test on 2026-10-13, round 8:

- "+ New use case" (My use cases) and "+ New blueprint" (Blueprints) open
  a small form - a name and a first step - and the dialog that opens next
  takes further steps; an own blueprint is stored as a template.
- Echo sounding moves to Folders, next to the folders it listens to.
  NemoFold has no scheduler of its own: a scheduled use case writes a task
  file the person installs, and the echo shows the runs it produced.
- The research notebook tile says "Start" instead of "Open": it is no
  configurable workflow.
- F1 from the PR #6 review: no blank line at the end of model_planner.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FMTv7ecoTBXem1ndYqUtxj
… workflow

Lukas, 2026-10-13: "Run it ... schlecht gewählt. Wir wollen noch keinen run
es sollte nur prepare voyage sein und wenn es eine kombination ist wird im
hintergrund der workflow angelegt und nutzer informiert ..."

- The captain offers Prepare voyage only. A plan of several steps is first
  kept as one new workflow under My use cases ("New workflow created: ..."),
  its steps go to the job inbox, and step 1 loads into the engine room.
- The engine room names the loaded workflow at its top and runs all its
  steps in order on request (local, dry run), or one step at a time.
- Local model servers that do not answer stay listed at the captain as
  "not reachable right now" instead of vanishing; the transfer approval
  checkbox sits next to its sentence.

Full suite 1187 passed, 2 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HwEgw7w5b64hDRLmCG3okz
…oved

Final acceptance review (advisor) on 2026-10-13:

- The public demo runs the same wheel but showed full-console controls that
  answered 404 there: the captain, working folders, echo sounding, "+ New
  use case/blueprint", library adopt/remove buttons and the policy editor.
  They are marked data-full-only and hidden when the server reports the
  demo; a click sweep over all seven demo views now finds no 4xx answer
  and no page error.
- Preparing the same plan again reuses the combined workflow it already
  created instead of adding "(2)" copies.
- SECURITY.md listed four mail addresses on domains that do not exist
  (ellmos.ai, open-bricks.org) or have no MX record (lukasgeiger.com); a
  report there would vanish. GitHub private vulnerability reporting is
  enabled and is now the only channel named.
- README EN/DE: the captain only prepares, the engine room runs the
  combined workflow; new entries from scratch; echo on Folders; the demo's
  scope.

Full suite 1187 passed, 2 skipped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HwEgw7w5b64hDRLmCG3okz
@github-actions

Copy link
Copy Markdown

Welcome! 👋 Thanks for your first pull request in this repository.

A maintainer will review it soon. Please make sure:

  • Your changes are tested
  • Documentation is updated if needed
  • The PR description explains what and why

Thanks for contributing!

Codex review of PR #7: "Run all steps" stayed active during
/api/voyage-run, so a double click started the chain twice with different
run IDs. The button is disabled for the run and an in-flight guard ignores
further clicks; measured in the browser: three quick clicks, one
/api/voyage-run request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HwEgw7w5b64hDRLmCG3okz
@lukisch
lukisch merged commit 6b13d12 into main Oct 13, 2026
6 checks passed
@lukisch

lukisch commented Oct 13, 2026

Copy link
Copy Markdown
Member Author

Merged by Codex (OpenAI) as second-model reviewer per owner decision D-048; verdict MERGE-FÄHIG; CI green on head.

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