Commit Graph

7 Commits

Author SHA1 Message Date
adcentury 026a2c8ba0 chore: replace Discord links with actionbook.dev/discord (CUE-412)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 23:41:14 +08:00
adcentury 234142f56d revert(docs): keep Why Actionbook section unchanged 2026-02-13 08:43:42 +08:00
adcentury 2b475c7c7b docs: align core tagline with resilience-first messaging 2026-02-13 08:36:09 +08:00
Adcent 1aaa6548e8 docs: make website CLI-first and demote MCP/SDK paths (#119) 2026-02-12 10:43:34 +08:00
sen c91746d24f refactor: remove extension isolated mode, unify browser docs (#111)
* [packages/actionbook-rs]refactor: remove extension isolated mode, unify browser docs

Simplify browser architecture from three modes to two:
- Isolated (default): launches a fresh Chrome profile via CDP
- Extension: connects to the user's running Chrome via bridge

Remove extension isolated mode entirely:
- Delete isolated_extension.rs, cdp_pipe.rs, cdp_http.rs
- Remove --isolated flag from CLI and config
- Simplify extension_bridge (remove isolated file helpers)
- Simplify launcher (remove pipe transport, LaunchResult)
- Clean up setup wizard and config fields
- Add legacy .isolated file cleanup for upgrade compatibility
- Fix stop() to also resolve legacy bridge-pid.isolated

Merge browser-extension.mdx into unified browser.mdx guide:
- Single page covers both Isolated and Extension modes
- Browser commands listed once (add --extension to switch)
- Update all cross-references in docs

* [packages/actionbook-rs]fix: add liveness check to extension stop PID resolution

Previously, `extension stop` blindly preferred the standard PID file over
the legacy `.isolated` file without checking liveness. In upgrade scenarios
where the legacy file held the live bridge PID and the standard file was
stale (PID possibly reused by OS), this could send SIGTERM to an unrelated
process.

Introduce `resolve_pid_for_port()` with liveness checking:
- Same PID in both files → select safely
- Different PIDs → check liveness, pick the live one
- Both alive → refuse to kill (Ambiguous), warn user
- Both dead → clean up stale files (BothMatchedButDead)

Includes 5 unit tests covering all branches.
2026-02-11 00:10:06 +08:00
sen 2e47ee6dab Add browser extension and CLI reference documentation (#95)
* [docs]feat: add browser extension documentation for PR #89

Add comprehensive documentation for the Chrome Extension Bridge feature:
- New guides/browser-extension.mdx with setup, usage, security, and
  troubleshooting sections
- docs.json navigation updated with new page entry
- index.mdx gains Integration Options card section (CLI/Extension/MCP)
- installation.mdx table and links include extension method
- cli-and-skills.mdx adds extension mode tip after browser examples
- api-reference/cli.mdx adds extension subcommands and --extension
  global flag documentation

* [docs]fix: update extension docs to reflect GitHub Release install flow

Sync documentation with PR #93 changes: extension is now downloaded
from GitHub Releases instead of extracted from embedded CLI binary.
2026-02-09 18:42:47 +08:00
Adcent e29ee02281 [docs]feat: add Mintlify documentation site
- Add introduction page with demo video, Why Actionbook section, and How It Works steps
- Configure Mintlify theme with black/white color scheme
- Add Actionbook logo (light/dark variants)
- Set up navigation structure with Documentation and API Reference tabs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-16 21:23:06 +08:00