Skip to content

Walk the install as the owner and fix what breaks - #36

Open
leeovery wants to merge 6 commits into
fix3/e15-disclosurefrom
fix3/e16-install
Open

Walk the install as the owner and fix what breaks#36
leeovery wants to merge 6 commits into
fix3/e15-disclosurefrom
fix3/e16-install

Conversation

@leeovery

Copy link
Copy Markdown
Owner

The install surfaces audited by driving them: wheel built, start.md followed literally through the create path and the join path, every command run, every claim checked.

  • The one substantive bug: joining on a fresh machine leaves LFS media as pointer files — git lfs install --local does not materialize them; Step 4 now runs git lfs pull
  • Step 6 pointed a fresh session at docs/shortcut.md as a repo path — but the install never clones the engine (uvx), so nothing existed there; now the raw URL, plus the missing skip condition when the owner declined the shortcut
  • Step 5's relocated scheduling content reconciled: the task prompt names the skill heading that actually exists, placeholders follow the file's own convention, and the relocation-dropped "do a run now" is restored on the no-desktop path
  • capture.md's materialization order corrected to the code's load-bearing sequence (LFS-verify → delete asset → rewrite pointer)
  • Smaller: join path re-asked questions the paste pre-answered; the commit step ran from the wrong directory; README's instance layout omitted files its own prose depends on
  • Device-verified iOS Shortcuts UI steps untouched; nothing in them flagged as stale

🤖 Generated with Claude Code

leeovery and others added 6 commits August 24, 2026 08:54
The instance README's run-it-on-another-machine paste names an existing
dex and its repo, but Step 1 unconditionally opened with the new-or-
existing question — a session following the join prompt would ask the
owner what the owner's own paste had just stated. The interview now takes
{mode} and {repo} from the request that brought it here when they are
already in it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Driven on a simulated fresh machine: a clone on a box that never ran
`git lfs install` globally checks LFS media out as pointer files, and
`git lfs install --local` alone does not materialize them — any joined
instance with media would read pointers where binaries belong. The join
path now runs `git lfs pull` after the local install, with the reason
stated.

Same step, two smaller defects: the inbox parenthetical claimed it
"reconciles waiting captures" (it materializes staged binaries and checks
the standing release; text captures wait untouched) and dropped the
command's own commit-and-push-now instruction; and the new path's
"Commit" bullet never said where, leaving `gh repo create --source .`
runnable from {home}. Both paths also set {name}, which Step 5 needs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The content moved from first-run.md verbatim, still speaking the skill's
dialect: `<instance>-run` and "<absolute path to {instance}>" against
this file's {name}/{instance} variables (and {instance} already IS the
absolute path), and a task prompt telling the runner to perform an
"Every-run procedure" when the skill's heading reads "Every run". The
move also dropped the section's closing "do a run now, whatever the
host" — the desktop path kept its Run now, the no-desktop path ended
setup without ever running the instance. Restored on that bullet.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Step 6 pointed at `docs/shortcut.md`, a path in the engine repo — which
the install never clones (the instance runs the engine via uvx), so a
session following start.md had nothing at that path. The step now names
the raw URL to fetch. It also ran unconditionally, though the interview
asks whether the owner wants the shortcut at all and a local-only
instance has no repo to capture into — skip conditions stated. The
token walkthrough now points at the guide's Before-you-begin section
instead of restating its click-path, keeping the expiration and
org-repo detail single-homed where the shortcut is built.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The protocol doc said inbox rewrites the capture's frontmatter and then
deletes the asset — the code's order is LFS-verify, delete, rewrite, and
inbox.py calls it load-bearing: the verify precedes the delete so a
binary that failed to stage never loses its only remote copy, and the
pointer rewrite lands last so an interrupted run re-enters cleanly. A
client author reasoning about the orphaned-asset failure mode needs the
real sequence.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The under-the-hood section opens on the bin/dex shim and the synced
skills, then gave an instance layout with neither .claude/ nor bin/ in
it. Both listed now, and CLAUDE.md's gloss matches what the seed holds:
identity and scope, importing the synced contract.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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