Skip to content

fix: unify workspace-scoped Lody session deep links - #1151

Open
lodystage[bot] wants to merge 4 commits into
mainfrom
fix/unified-lody-session-deeplinks
Open

lodystage[bot] wants to merge 4 commits into
mainfrom
fix/unified-lody-session-deeplinks

Conversation

@lodystage

@lodystage lodystage Bot commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Related issue

Internal same-repository change; no linked issue.

Summary

  • Unify all channels on lody session URIs with workspace IDs across prompts, mentions, paste, navigation, MCP and Markdown export; preserve exact children and authorization boundaries.
  • Preserve existing OS defaults; forward legacy common cloud routes only to the Stable private alias, with visible redacted failures. Keep chat/new local. Windows first launch fills an absent handler.
  • Isolate invalid batch-status items; paste compound links as child mentions; tolerate partial export items; normalize punctuation/emphasis and skip unrelated URLs.
  • Wait for child metadata, cancel abandoned navigation and expire pending restoration after 15 seconds. Centralize runtime/packaging schemes.
  • Update bilingual draft Specs and owning note: contract.

Diff baseline

The shallow checkout has a stale local main without a merge base. The branch includes main at 7700f42; review uses the verified origin/main merge base.

Test plan

  • Passed 97 focused regression tests and all 48 repository script tests.
  • Passed workspace typecheck, lint, formatting, localization and boundary checks.
  • Full check encountered sandbox subprocess restrictions. Full CI rerun stopped at React act with inherited NODE_ENV=production; that individual case passed with NODE_ENV=test. Full-suite completion is not claimed.
  • Docs check retains six pre-existing missing Kimi/Pi submodule links; no new errors.
  • Clean Windows installation, installer registration before first launch, real packaged OS dispatch/default selection and hosted callback deployment remain unverified. Injected OS tests do not establish release acceptance.

Context handoff

Internal implementation; regular PR explicitly requested. Specs remain draft. No claimed human approval, production rollout or captured authoring transcripts.

@github-actions

Copy link
Copy Markdown
Contributor

Desktop PR regression failed on commit c51bf60cb22f5ab88c096fd79b69038510119050.

Recordings not attached

  • Run evidence: failure-index.json is missing

The Actions artifact retains the complete trace, screenshots, logs, and runtime evidence.

Preserve existing defaults, hand legacy cloud routes to Stable, isolate invalid batch references, and bound session restoration. Share the scheme catalog and harden paste and Markdown export.

Model: gpt-5
Keep parent and tab relationships internal, normalize legacy selectors on export, and document one public address format.

Model: gpt-5

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant