Skip to content

Extract the marketing site to its own repository - #2

Merged
PouyanJay merged 1 commit into
mainfrom
chore/extract-landing-site
Jun 28, 2026
Merged

Extract the marketing site to its own repository#2
PouyanJay merged 1 commit into
mainfrom
chore/extract-landing-site

Conversation

@PouyanJay

Copy link
Copy Markdown
Owner

Removes `apps/site` from the monorepo. The landing page now lives in the dedicated telecode-landingpage repo (a self-contained, prerendered SvelteKit site).

Changes

  • Delete `apps/site/` — the marketing/landing site.
  • Keep `@telecode/ui` — `apps/web` still consumes its design tokens.
  • Reference cleanup: `CONTRIBUTING.md` (project-layout table), `CHANGELOG.md`, `docs/deploy-azure.md`, `.gitignore`.
  • `pnpm-lock.yaml` refreshed (drops `@telecode/site` from the workspace).

Verification

  • `pnpm typecheck` (5/5), `pnpm lint`, `pnpm format:check`, `pnpm test` (protocol/daemon/relay/web) — all green.

⚠️ Merge order

Repoint Vercel (telecode.io) to the `telecode-landingpage` repo before merging this. The currently-live site stays up until its next rebuild, but once `apps/site` is gone from `main`, any site build still pointed at this repo would fail. Merge after the Vercel project tracks the new repo.

The landing page now lives in a dedicated repo (telecode-landingpage); remove
apps/site from this monorepo. @telecode/ui stays — apps/web still consumes its
tokens. Update references in CONTRIBUTING, CHANGELOG, docs/deploy-azure, and
.gitignore.
@PouyanJay
PouyanJay merged commit e8088ce into main Jun 28, 2026
2 checks passed
@PouyanJay
PouyanJay deleted the chore/extract-landing-site branch June 28, 2026 11:32
PouyanJay added a commit that referenced this pull request Jul 5, 2026
… sessions in the list

- Concurrent permission gates (#4 "stuck"): the session view's approve/reject
  discarded the clicked gate's requestId and resolved the FIRST pending gate
  instead. With several gates open at once (parallel tool calls) the operator's
  click landed on the wrong request — it read as "nothing happened / stuck",
  which also drove the "had to reopen to see progress" symptom. Thread each
  gate's requestId through onDecide, matching how question/handover answers
  already work. onDecide now requires a requestId, so the type prevents a
  regression.
- Chained sessions (#2): a forked continuation was only marked inside the
  session view ("continued from" / "view continuation"). The dashboard list now
  marks it too with a "continuation" pill, via a new isContinuation on the row.
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