mirror of
https://github.com/aphrody-labs/bun-libraries.git
synced 2026-10-13 22:20:34 +00:00
2.2 KiB
2.2 KiB
Plan
- Resolve workspace, tools and Aphrody home/graph context.
- Read skills and inventory source repositories.
- Create 16 forks and pinned submodules.
- Add the pinned Bun Tauri SDK source.
- Build desktop frontend/backend with Bun.
- Replace the upstream frontend build pipeline with Bun.
- Validate native manifests and generate the desktop Cargo lockfile.
- Apply English text, Aphrody/Bun identity and library boundaries.
- Apply current Linux, Debian, COSMIC and Bun upstream conventions.
- Complete scoped type, lint, format and build checks.
- Publish the modified library and prepare the verified monorepo branch.
Video priority
- Audit FilmCraft format, media, time, CLI and export contracts.
- Coordinate native Bun.Video ownership with the parallel Bun session.
- Add bounded native library inspection, probing, editing and export APIs.
- Preserve exact i64/u64 JSON and timeline ticks.
- Surface video priority and native availability in the Aphrody shell.
- Complete scoped gates and publish the integration.
Native tooling
- Replace external quality packages with native Bun commands.
- Apply aggressive n2b to authored code and review its recommendations.
- Complete aggressive library and SDK migration through their owners.
- Patch the internal n2b owner for large monorepos through a subagent.
Unified deployment
- Consolidate shared concepts into their existing capability owners.
- Create app subdomains through Cloudflare MCP and retain active R2 domains.
- Package independent apps with verified Aphrody Bun and native engines.
- Reference one content-addressed asset manifest across apps.
- Prepare canonical Infra services, routes and release workflows.
- Deploy the Rust controller and self-hosted forge/runner on the VPS.
- Qualify artifacts, domains and services separately; publish owned changes.
Delivery status
- Linux Video and Generation standalones are built and qualified.
- Remaining app/target builds and public app activation need their own receipts.
- Git/Komodo HTTPS, Periphery and runner registration are qualified.
- Source publication and CI execution are recorded in docs/session-report.md.