Reading /srv/bulgar · 26 components · manifest generated 2026-10-17Settings
This project is not routed to a worker yet. The brief is still correct — assign it above to see which session to paste it into.
Dev Control does not send this for you. the Claude CLI has no send or message command, and the two channels that exist - the session messaging socket and tmux send-keys - are both an arbitrary shell where the input is the command; Dev Control will not type into a live session from a browser
The public website of BULGAR, a brand development company operating from Thailand across Asia. **YOUR BRAND DEVELOPER.** Strategy. Creative. Technology. Culture.
Last commit 0ec9c85 — Homepage V1.1: real client wall, hero exit, intro curtain, frame parallax
Dev Control reports both and changes neither. The manifest is a human document; updating it is your call.
Nothing is serving it. Start it on the worker: preview-serve.sh start <component>.
No public deployment is recorded for this repository, so nothing has been checked. That is not the same as being offline.
Only 1 milestone is recorded here, so a percentage would be 0% or 100% and nothing else — it would look far more certain than it is. The count is shown instead. DRAFT means this list of 1 milestone is Dev Control’s proposal, read off runs, reports, branches and the manifest — you have not confirmed it is the right list. Confirm the roadmap and the word disappears.
Vercel and Supabase open their dashboards. Dev Control holds no credential for either and cannot confirm this project is on them.
Progress is milestone weight only — settled weight over total weight. It is never derived from commits, lines of code, file counts or elapsed time. Each draft below cites the real evidence it came from.
Nothing is settled yet.
Equal weight unless there is a real reason otherwise. Nothing here touches git.
Nothing is blocked.
AUTO-REGISTERED 2026-10-17 by bin/estate-sync.py from the checkout at /srv/bulgar/projects/bulgar-pro-web. The commands above are the ones this repository's own package.json declares; nothing here is guessed. Everything else is a placeholder awaiting a human: the project family, what this component IS, whether it needs credentials or services, and how to run it. It is deliberately NOT startable - an entry with a start_command takes a preview port and shifts every port after it - so give it one by hand, with a pinned port, if it should have a preview.
2 branches · 0 agent branches · 0 wip branches