Skip to content

Remove legacy references - #28

Merged
1 commit merged into
mainfrom
fix/remove-legacy-references
Apr 9, 2025
Merged

Remove legacy references#28
1 commit merged into
mainfrom
fix/remove-legacy-references

Conversation

@joelteply

Copy link
Copy Markdown
Contributor

Summary

This PR removes unnecessary legacy references:

  • Remove 'ai-config' references from README as we don't need legacy support
  • Simplify ai-config.js implementation without warning messages
  • Improve README clarity

Test plan

  1. Verify README no longer mentions legacy command
  2. Test that both 'continuum' and 'ai-config' commands work identically
  3. Confirm clean output with no warnings

This makes the documentation more straightforward for this new project.

🤖 Generated with Claude Code

- Remove 'ai-config' references from README
- Simplify ai-config.js implementation without warning messages
- Improve README clarity
Copilot AI review requested due to automatic review settings April 9, 2025 04:31

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

@joelteply joelteply closed this pull request by merging all changes into main in da393ae Apr 9, 2025
@joelteply
joelteply deleted the fix/remove-legacy-references branch April 9, 2025 05:13
joelteply added a commit that referenced this pull request Jun 19, 2026
…t layer (#1689)

The old Node/TS web client is being reinvented on the new client SDK
(screenshot-as-spec, own modular container), not repaired. Its build is
prone to directory-reshuffle breakage from the headless-Rust work — e.g.
carl-install-smoke has been RED across all of canary because a tsx build
step resolves browser-index.ts to tools/ instead of src/, so its
`./browser/generated` import ENOENTs (the real, git-tracked file is
src/browser/generated.ts). That dead-layer break aborted the whole public
`curl install.sh | bash` before the headless core ever came up.

Decouple both the installer and the smoke gate from that layer:

install.sh:
- Host-side jtag CLI bundle build is now BEST-EFFORT / non-blocking. On
  failure it warns loudly and CONTINUES — the headless Rust core is the
  install deliverable, brought up by the container runtime regardless.
  (Previously a hard `fail` aborted install on the Node build break.)

carl-install-smoke.sh:
- New PRIMARY gate: wait for the continuum-core IPC socket
  (/root/.continuum/sockets/continuum-core.sock, the same signal as the
  compose healthcheck) via `docker compose exec`. "Smoke passed" now means
  "the headless core serves IPC", independent of the Node web build.
- The old widget-server :9003 render + jtag chat-e2e assertions are now
  ADVISORY (default-skipped, loud), re-enablable with CARL_CHECK_WEB_CLIENT=1
  once the new client container lands and they're rewritten against it.

Roadmap: #28 (the dead-layer path break, intentionally NOT deep-fixed),
#29 (new Node/TS client SDK + app as a modular container on the new SDK).

Co-authored-by: Claude Opus 4.8 <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.

2 participants