Skip to content

fix: read paths never fetch — info and session-start hook go purely local - #35

Merged
zheng-weihao merged 1 commit into
orbcli:mainfrom
zheng-weihao:info-no-fetch
Aug 13, 2026
Merged

fix: read paths never fetch — info and session-start hook go purely local#35
zheng-weihao merged 1 commit into
orbcli:mainfrom
zheng-weihao:info-no-fetch

Conversation

@zheng-weihao

@zheng-weihao zheng-weihao commented Aug 13, 2026

Copy link
Copy Markdown
Member

What changed

orbit info and the orbit context --startup reignite block no longer fetch — read paths are purely local again (zero network).

#29's touchpoint fetch made every info and every session start with worktrees pay N serial remote round-trips (the default branch plus each tracked branch, one fetch each), multiplying with scoped-branch residue. Measured: orbit info 4.83s wall / ~0.4s CPU → 0.51s on a repo with 4 tracked branches; 19.7s → 0.55s on a pool carrying more scoped-branch residue; context --startup 24.5s → 1.8s with two repos added.

Ruling: without an async daemon, auto-fetch on a main path taxes a synchronous caller for advisory freshness — low friction outranks it (cf. VSCode's background autofetch never blocking startup). Auto-fetch may return only off the main path.

  • orbit_info and orbit_context_reignite (text + JSON) drop orbit_touchpoint_fetch, keeping config maintenance (local writes); fetching touchpoints narrow to orbit sync / orbit prune
  • remoteAhead reads last-fetched refs, refreshed by sync / prune or the user's own fetch/pull
  • skill contract (SKILL.md + CONSTRAINTS.md) steps 3/5 state the last-fetched-refs semantics; cold-start sync becomes a two-trigger rule (remoteAhead > 0, or a stale last fetch when the task depends on fresh code)
  • spec-docs (commands / worktree / hooks / knowledge / warnings), USAGE, ROADMAP, CHANGELOG sync to the new contract
  • tests: the two info-fetch cases rewritten to the new contract (info never fetches — upstream warning reflects last-fetched refs; a remote-lost branch's stale ref stays put)

Checklist

…ocal

- orbcli#29's touchpoint fetch made every `orbit info` and every session start
  with worktrees pay N serial remote round-trips (default branch + each
  tracked branch, one fetch each), multiplying with scoped-branch residue;
  measured baselines: `orbit info` 4.83s wall / ~0.4s CPU on a repo with
  4 tracked branches, 19.7s on a pool carrying more scoped-branch residue,
  `context --startup` 24.5s with two repos added
- ruling: without an async daemon, auto-fetch on a main path taxes a
  synchronous caller for advisory freshness — low friction outranks it
  (cf. VSCode's background autofetch never blocking startup); auto-fetch
  may return only off the main path
- info and the context --startup reignite block drop the touchpoint fetch
  and keep config maintenance (local writes); remoteAhead now reads
  last-fetched refs, refreshed by sync / prune or the user's own fetch/pull;
  fetching touchpoints narrow to sync / prune
- skill contract (SKILL.md + CONSTRAINTS.md): steps 3/5 state the
  last-fetched-refs semantics; cold-start sync becomes a two-trigger rule
  (remoteAhead > 0, or a stale last fetch when the task depends on fresh code)
- spec-docs, USAGE, ROADMAP, CHANGELOG and the two info-fetch bats cases
  sync to the new contract; full suite 367/367 on latest main

Signed-off-by: Zheng Weihao <zheng-weihao@outlook.com>
@zheng-weihao
zheng-weihao merged commit dbf04e0 into orbcli:main Aug 13, 2026
2 checks passed
@zheng-weihao
zheng-weihao deleted the info-no-fetch branch August 24, 2026 11:07
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