Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions devlog/_fin/260726_announcements/031_guided_tour_draft.md
Original file line number Diff line number Diff line change
Expand Up @@ -394,14 +394,12 @@ available from a manual entry point.
Closing the window is a decision, and treating it as one is more honest than
trapping the user in a flow they walked away from.

### D4 — `040` gains a positive verification procedure
### D4 — positive verification procedure withdrawn

Closes R3. Since H3 makes the geometry unassertable in happy-dom, the gate list
must contain a way to make the tour APPEAR, not only checks that it stays hidden:

```
OPENCODEX_HOME=$(mktemp -d) ocx start # genuine first run, real config untouched
```
The proposed `OPENCODEX_HOME`-only procedure is unsafe and does not close R3.
As D4′ establishes, no positive first-run procedure should be documented until
the implementation pass verifies full isolation of Codex, Grok, shell and
system-environment state, together with use of a non-default port.
Comment on lines +399 to +402

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the unsafe command from the earlier section

When a reviewer follows this draft's manual-verification instructions, lines 91–107 still present OPENCODEX_HOME=$(mktemp -d) ocx start as the command that safely leaves the real configuration untouched, and lines 272–275 still direct readers back to it. Adding a withdrawal only here leaves the actionable unsafe procedure in place even though this same document explains that it can rewrite the real Codex, Grok, shell, and system-environment state; replace the earlier how-to section and its R3 reference with the withdrawal as well.

Useful? React with 👍 / 👎.


### D5 — the cost question is answered by scope, not by argument

Expand Down
Loading