trybeacon 0.1.33 → 0.1.35

package/dist/lib/assets.js

@@ -27,8 +27,9 @@ The user already has Beacon running. You're going to map this repository's archi
 
 A single \`beacon_init_persist\` MCP tool call with:
 
-- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), and \`depends\` listing other component titles it relies on. Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
-- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card.
+- **hasFrontend**: \`true\` or \`false\` \u2014 does this repo have a frontend surface (UI code)? You just read the repo, so you know. Set it explicitly; it gates the frontend/backend \`layer\` distinction on the boards (a pure-backend repo never shows it).
+- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), \`depends\` listing other component titles it relies on \u2014 and, when \`hasFrontend\` is true, \`layer\` (\`"frontend" | "backend" | "fullstack"\`). Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
+- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card. When \`hasFrontend\` is true, give each a \`layer\` too (\`"frontend" | "backend" | "fullstack"\`).
 - **overview**: one paragraph describing what this project is and its stack. This lands in AGENTS.md as the project intro.
 - **conventions**: 3\u20138 concrete rules a contributor MUST follow \u2014 build/test commands, where code goes, patterns, things easy to get wrong. Infer from actual files, not assumptions.
 - **snapshot** (optional but encouraged): \`{ tables, relations, endpoints }\` for the existing database. If the project uses Prisma, read \`prisma/schema.prisma\`. If SQLAlchemy, read the model files. If Django, read \`models.py\`. If you find no obvious schema source, skip the snapshot \u2014 don't fabricate.
@@ -86,7 +87,7 @@ The one caveat: if the user manually edited an INIT-source node on the canvas (e
    - **~ changed**: COMPONENT_X (role expanded to cover Y)
    - **schema**: + 2 new tables (TableA, TableB); + 3 new endpoints; \u2212 1 deprecated endpoint
    No need to wait for confirmation \u2014 just show the diff so the user sees what's about to land.
-5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
+5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`, \`hasFrontend\` \u2014 re-assert it, the stack may have changed). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
 
 ## What you should NOT do
 
@@ -165,6 +166,8 @@ When listing endpoints, give each \`uses: [{ table, access }]\` so the endpoint\
 
 EVERY feature MUST carry \`category\` (e.g. AUTH | SEARCH | DATA | INTEL | BILLING | \u2026; \`cluster\` is accepted as an alias) and \`priority\` (0 = P0 critical, 1 = P1 high, 2 = P2 medium, 3 = P3 low). Beacon REJECTS a plan whose features omit either \u2014 \`beacon_propose_plan\` returns the list of what's missing, and an ExitPlanMode \`\`\`beacon block is denied \u2014 so set both on every feature instead of relying on defaults.
 
+When the workspace HAS A FRONTEND (Beacon knows \u2014 the agent set \`hasFrontend\` at init, or frontend files were detected), every feature must ALSO carry \`layer\`: \`"frontend" | "backend" | "fullstack"\` \u2014 which side of the stack the work lands on. Plans omitting it are REJECTED the same way category/priority are. It works on every surface that creates roadmap cards (\`beacon_propose_plan\`, the \`\`\`beacon block, \`beacon_start_feature\`, \`beacon_add_subtasks\` \u2014 sub-tasks default to the parent's layer) and on architecture components (\`beacon_describe_feature\` / \`beacon_init_persist\`). In a pure-backend repo, never set it \u2014 the boards don't show it there.
+
 REUSE before you create. Call \`beacon_map\` to see the features + categories that already exist. Beacon HARD-BLOCKS a feature that duplicates an existing one (it returns the existing feature to use instead) and one created without a category \u2014 so don't re-create work that's already on the board, and reuse an existing category rather than a near-synonym. \`category\` is the ONLY domain field. \`front\` (in \`beacon_start_feature\`) nests a feature UNDER an existing parent feature \u2014 it is NOT a domain tag; a \`front\` that matches no real feature is rejected.
 
 When listing features, give each \`dependsOn: ["Other feature title", \u2026]\` for any feature that must ship after another in the same plan. Beacon draws these as "depends on" links so the roadmap shows the dependency chain instead of loose, disconnected cards.

package/dist/lib/codex-install.js

@@ -27,8 +27,9 @@ The user already has Beacon running. You're going to map this repository's archi
 
 A single \`beacon_init_persist\` MCP tool call with:
 
-- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), and \`depends\` listing other component titles it relies on. Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
-- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card.
+- **hasFrontend**: \`true\` or \`false\` \u2014 does this repo have a frontend surface (UI code)? You just read the repo, so you know. Set it explicitly; it gates the frontend/backend \`layer\` distinction on the boards (a pure-backend repo never shows it).
+- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), \`depends\` listing other component titles it relies on \u2014 and, when \`hasFrontend\` is true, \`layer\` (\`"frontend" | "backend" | "fullstack"\`). Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
+- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card. When \`hasFrontend\` is true, give each a \`layer\` too (\`"frontend" | "backend" | "fullstack"\`).
 - **overview**: one paragraph describing what this project is and its stack. This lands in AGENTS.md as the project intro.
 - **conventions**: 3\u20138 concrete rules a contributor MUST follow \u2014 build/test commands, where code goes, patterns, things easy to get wrong. Infer from actual files, not assumptions.
 - **snapshot** (optional but encouraged): \`{ tables, relations, endpoints }\` for the existing database. If the project uses Prisma, read \`prisma/schema.prisma\`. If SQLAlchemy, read the model files. If Django, read \`models.py\`. If you find no obvious schema source, skip the snapshot \u2014 don't fabricate.
@@ -86,7 +87,7 @@ The one caveat: if the user manually edited an INIT-source node on the canvas (e
    - **~ changed**: COMPONENT_X (role expanded to cover Y)
    - **schema**: + 2 new tables (TableA, TableB); + 3 new endpoints; \u2212 1 deprecated endpoint
    No need to wait for confirmation \u2014 just show the diff so the user sees what's about to land.
-5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
+5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`, \`hasFrontend\` \u2014 re-assert it, the stack may have changed). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
 
 ## What you should NOT do
 
@@ -165,6 +166,8 @@ When listing endpoints, give each \`uses: [{ table, access }]\` so the endpoint\
 
 EVERY feature MUST carry \`category\` (e.g. AUTH | SEARCH | DATA | INTEL | BILLING | \u2026; \`cluster\` is accepted as an alias) and \`priority\` (0 = P0 critical, 1 = P1 high, 2 = P2 medium, 3 = P3 low). Beacon REJECTS a plan whose features omit either \u2014 \`beacon_propose_plan\` returns the list of what's missing, and an ExitPlanMode \`\`\`beacon block is denied \u2014 so set both on every feature instead of relying on defaults.
 
+When the workspace HAS A FRONTEND (Beacon knows \u2014 the agent set \`hasFrontend\` at init, or frontend files were detected), every feature must ALSO carry \`layer\`: \`"frontend" | "backend" | "fullstack"\` \u2014 which side of the stack the work lands on. Plans omitting it are REJECTED the same way category/priority are. It works on every surface that creates roadmap cards (\`beacon_propose_plan\`, the \`\`\`beacon block, \`beacon_start_feature\`, \`beacon_add_subtasks\` \u2014 sub-tasks default to the parent's layer) and on architecture components (\`beacon_describe_feature\` / \`beacon_init_persist\`). In a pure-backend repo, never set it \u2014 the boards don't show it there.
+
 REUSE before you create. Call \`beacon_map\` to see the features + categories that already exist. Beacon HARD-BLOCKS a feature that duplicates an existing one (it returns the existing feature to use instead) and one created without a category \u2014 so don't re-create work that's already on the board, and reuse an existing category rather than a near-synonym. \`category\` is the ONLY domain field. \`front\` (in \`beacon_start_feature\`) nests a feature UNDER an existing parent feature \u2014 it is NOT a domain tag; a \`front\` that matches no real feature is rejected.
 
 When listing features, give each \`dependsOn: ["Other feature title", \u2026]\` for any feature that must ship after another in the same plan. Beacon draws these as "depends on" links so the roadmap shows the dependency chain instead of loose, disconnected cards.

package/dist/lib/global-install.js

@@ -27,8 +27,9 @@ The user already has Beacon running. You're going to map this repository's archi
 
 A single \`beacon_init_persist\` MCP tool call with:
 
-- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), and \`depends\` listing other component titles it relies on. Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
-- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card.
+- **hasFrontend**: \`true\` or \`false\` \u2014 does this repo have a frontend surface (UI code)? You just read the repo, so you know. Set it explicitly; it gates the frontend/backend \`layer\` distinction on the boards (a pure-backend repo never shows it).
+- **components**: 8\u201325 main building blocks of this codebase. NOT every file. Group them by \`domain\` (short UPPERCASE: AUTH, API, DATA, UI, JOBS, INFRA, BILLING, SEARCH, \u2026). For each: a one-line technical \`role\`, a one-sentence plain-language \`plain\`, the few \`files\` that implement it (repo-relative), \`depends\` listing other component titles it relies on \u2014 and, when \`hasFrontend\` is true, \`layer\` (\`"frontend" | "backend" | "fullstack"\`). Use the dependency graph you can see in the source \u2014 files that import each other heavily usually belong together. If you spot a bug or something worth investigating while reading a component's code, add \`bugs: [{ note }]\` to that component \u2014 it renders as a bug flag on the node (attributed to the agent). Only flag what you actually saw in the code; don't speculate.
+- **roadmap**: 3\u20136 BROAD strategic directions. Big-picture themes only \u2014 "Harden auth & security", "Add observability", "Scale the data layer", "Pay down test-coverage debt". NOT detailed tasks. NOT file-level. Each gets a short title and one-line \`why\`. If one of them is a concrete BUG to fix (something broken you saw in the code), add \`kind: "BUG"\` so it renders as a typed bug card. When \`hasFrontend\` is true, give each a \`layer\` too (\`"frontend" | "backend" | "fullstack"\`).
 - **overview**: one paragraph describing what this project is and its stack. This lands in AGENTS.md as the project intro.
 - **conventions**: 3\u20138 concrete rules a contributor MUST follow \u2014 build/test commands, where code goes, patterns, things easy to get wrong. Infer from actual files, not assumptions.
 - **snapshot** (optional but encouraged): \`{ tables, relations, endpoints }\` for the existing database. If the project uses Prisma, read \`prisma/schema.prisma\`. If SQLAlchemy, read the model files. If Django, read \`models.py\`. If you find no obvious schema source, skip the snapshot \u2014 don't fabricate.
@@ -86,7 +87,7 @@ The one caveat: if the user manually edited an INIT-source node on the canvas (e
    - **~ changed**: COMPONENT_X (role expanded to cover Y)
    - **schema**: + 2 new tables (TableA, TableB); + 3 new endpoints; \u2212 1 deprecated endpoint
    No need to wait for confirmation \u2014 just show the diff so the user sees what's about to land.
-5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
+5. **Call \`beacon_init_persist\`** ONCE with the refreshed full analysis (same shape as init: \`components\`, \`roadmap\`, \`overview\`, \`conventions\`, \`snapshot\`, \`hasFrontend\` \u2014 re-assert it, the stack may have changed). It replaces all init-source nodes and regenerates \`AGENTS.md\`. Bug flags already on a component survive the refresh (they're carried over by title); add \`bugs: [{ note }]\` for anything NEW you found worth investigating \u2014 identical open flags are not duplicated.
 
 ## What you should NOT do
 
@@ -165,6 +166,8 @@ When listing endpoints, give each \`uses: [{ table, access }]\` so the endpoint\
 
 EVERY feature MUST carry \`category\` (e.g. AUTH | SEARCH | DATA | INTEL | BILLING | \u2026; \`cluster\` is accepted as an alias) and \`priority\` (0 = P0 critical, 1 = P1 high, 2 = P2 medium, 3 = P3 low). Beacon REJECTS a plan whose features omit either \u2014 \`beacon_propose_plan\` returns the list of what's missing, and an ExitPlanMode \`\`\`beacon block is denied \u2014 so set both on every feature instead of relying on defaults.
 
+When the workspace HAS A FRONTEND (Beacon knows \u2014 the agent set \`hasFrontend\` at init, or frontend files were detected), every feature must ALSO carry \`layer\`: \`"frontend" | "backend" | "fullstack"\` \u2014 which side of the stack the work lands on. Plans omitting it are REJECTED the same way category/priority are. It works on every surface that creates roadmap cards (\`beacon_propose_plan\`, the \`\`\`beacon block, \`beacon_start_feature\`, \`beacon_add_subtasks\` \u2014 sub-tasks default to the parent's layer) and on architecture components (\`beacon_describe_feature\` / \`beacon_init_persist\`). In a pure-backend repo, never set it \u2014 the boards don't show it there.
+
 REUSE before you create. Call \`beacon_map\` to see the features + categories that already exist. Beacon HARD-BLOCKS a feature that duplicates an existing one (it returns the existing feature to use instead) and one created without a category \u2014 so don't re-create work that's already on the board, and reuse an existing category rather than a near-synonym. \`category\` is the ONLY domain field. \`front\` (in \`beacon_start_feature\`) nests a feature UNDER an existing parent feature \u2014 it is NOT a domain tag; a \`front\` that matches no real feature is rejected.
 
 When listing features, give each \`dependsOn: ["Other feature title", \u2026]\` for any feature that must ship after another in the same plan. Beacon draws these as "depends on" links so the roadmap shows the dependency chain instead of loose, disconnected cards.

package/dist/lib/release.js

@@ -0,0 +1,2 @@
+// @bun
+var m=Object.defineProperty;var q=(b)=>b;function v(b,j){this[b]=q.bind(null,j)}var x=(b,j)=>{for(var k in j)m(b,k,{get:j[k],enumerable:!0,configurable:!0,set:v.bind(j,k)})};var y=(b,j)=>()=>(b&&(j=b(b=0)),j);var A="wenzorithelly/beacon",B="trybeacon",C="https://registry.npmjs.org/trybeacon/latest",w=(process.env.NEXT_PUBLIC_BEACON_SITE_URL??"https://www.trybeacon.sh").replace(/\/$/,""),D=`curl -fsSL ${w}/install.sh | sh`;export{w as SITE_URL,A as REPO_SLUG,B as NPM_PACKAGE,C as NPM_LATEST_URL,D as INSTALL_COMMAND};

package/dist/lib/semver.js

@@ -0,0 +1,2 @@
+// @bun
+var i=Object.defineProperty;var o=(r)=>r;function u(r,e){this[r]=o.bind(null,e)}var l=(r,e)=>{for(var n in e)i(r,n,{get:e[n],enumerable:!0,configurable:!0,set:u.bind(e,n)})};var f=(r,e)=>()=>(r&&(e=r(r=0)),e);function s(r){if(typeof r!=="string")return null;let e=r.trim().replace(/^v/i,"").match(/^(\d+)(?:\.(\d+))?(?:\.(\d+))?/);if(!e)return null;return[Number(e[1]),Number(e[2]??0),Number(e[3]??0)]}function m(r,e){let n=s(r),a=s(e);if(!n||!a)return!1;for(let t=0;t<3;t++){if(n[t]>a[t])return!0;if(n[t]<a[t])return!1}return!1}export{s as parseVersion,m as isNewerVersion};

package/dist/lib/workspaces.js

@@ -1,2 +1,2 @@
 // @bun
-var q=Object.defineProperty;var P=(Q)=>Q;function S(Q,X){this[Q]=P.bind(null,X)}var y=(Q,X)=>{for(var Z in X)q(Q,Z,{get:X[Z],enumerable:!0,configurable:!0,set:S.bind(X,Z)})};var k=(Q,X)=>()=>(Q&&(X=Q(Q=0)),X);var v={};y(v,{provisionDb:()=>o});import{createClient as w}from"@libsql/client";import{drizzle as b}from"drizzle-orm/libsql";import{migrate as m}from"drizzle-orm/libsql/migrator";import{readMigrationFiles as g}from"drizzle-orm/migrator";import{dirname as u,join as p}from"path";import{fileURLToPath as h}from"url";async function N(Q,X){return(await Q.execute({sql:"SELECT 1 FROM sqlite_master WHERE type='table' AND name = ?",args:[X]})).rows.length>0}async function n(Q,X){let Z=await Q.execute(`PRAGMA table_info("${X}")`);return new Set(Z.rows.map(($)=>String($.name)))}async function f(Q){if(!await N(Q,"__drizzle_migrations"))return 0;let X=await Q.execute('SELECT count(*) AS n FROM "__drizzle_migrations"');return Number(X.rows[0]?.n??0)}async function d(Q){for(let[X,Z]of Object.entries(s)){if(!await N(Q,X))continue;let $=await n(Q,X);for(let J of Z){if(!$.has(J))continue;await Q.execute(`UPDATE "${X}" SET "${J}" = CAST((julianday("${J}") - 2440587.5) * 86400000 AS INTEGER) WHERE typeof("${J}") = 'text'`)}}}async function o(Q,X=c){let Z=w({url:Q});try{await Z.execute("PRAGMA journal_mode = WAL;"),await Z.execute("PRAGMA foreign_keys = ON;"),await Z.execute("PRAGMA busy_timeout = 5000;");let $=await N(Z,"__drizzle_migrations"),J=await N(Z,"Node"),Y=!1;if(J&&!$){let B=g({migrationsFolder:X})[0];if(B)await Z.execute('CREATE TABLE IF NOT EXISTS "__drizzle_migrations" (id SERIAL PRIMARY KEY, hash text NOT NULL, created_at numeric)'),await Z.execute({sql:'INSERT INTO "__drizzle_migrations" ("hash", "created_at") VALUES (?, ?)',args:[B.hash,B.folderMillis]}),Y=!0}let L=await f(Z);if(await m(b(Z),{migrationsFolder:X}),await f(Z)>L)Y=!0;return await d(Z),{migrated:Y}}finally{Z.close()}}var l,c,s;var _=k(async()=>{l=u(u(u(h(import.meta.url)))),c=process.env.BEACON_MIGRATIONS_DIR||p(l,"drizzle"),s={Node:["createdAt","updatedAt"],Note:["createdAt","updatedAt"],DbTable:["createdAt","updatedAt"],Endpoint:["createdAt","updatedAt"],DraftTable:["createdAt"],SyncState:["codeGraphSyncedAt","updatedAt"],AppSetting:["updatedAt"],ProjectMeta:["updatedAt"],CodeFile:["updatedAt"]}});import{AsyncLocalStorage as a}from"async_hooks";import{spawnSync as t}from"child_process";import{createHash as r}from"crypto";import{existsSync as D,mkdirSync as U,readFileSync as x,writeFileSync as E}from"fs";import{homedir as i}from"os";import{basename as e,join as V}from"path";function K(){return process.env.BEACON_HOME||V(i(),".beacon")}function C(){return V(K(),"workspaces.json")}function R(Q){return r("sha256").update(Q).digest("hex").slice(0,12)}function TQ(Q=process.cwd()){let X=t("git",["rev-parse","--show-toplevel"],{cwd:Q,stdio:["ignore","pipe","ignore"]});if(X.status===0){let Z=X.stdout?.toString().trim();if(Z)return Z}return Q}function j(Q){return V(K(),Q)}function QQ(Q){return`file:${V(j(Q),"db.sqlite")}`}function M(){try{let Q=JSON.parse(x(C(),"utf8"));return Array.isArray(Q)?Q:[]}catch{return[]}}function O(Q){U(K(),{recursive:!0}),E(C(),JSON.stringify(Q,null,2))}function XQ(){return M().sort((Q,X)=>X.lastOpenedAt.localeCompare(Q.lastOpenedAt))}function G(Q){return M().find((X)=>X.id===Q)??null}function ZQ(Q,X,Z=new Date().toISOString()){let $=R(Q),J=M(),Y=J.find((H)=>H.id===$),L={id:$,path:Q,name:X||Y?.name||e(Q),lastOpenedAt:Z},B=[L,...J.filter((H)=>H.id!==$)];return U(j($),{recursive:!0}),O(B),L}function fQ(Q,X=new Date().toISOString()){let Z=M(),$=Z.find((J)=>J.id===Q);if(!$)return;$.lastOpenedAt=X,O(Z)}function vQ(Q){if(O(M().filter((X)=>X.id!==Q)),T()===Q)$Q(XQ()[0]?.id??null)}function W(){return V(K(),"active")}function T(){try{return x(W(),"utf8").trim()||null}catch{return null}}function $Q(Q){U(K(),{recursive:!0}),E(W(),Q??"")}function _Q(){let Q=T();return Q?G(Q):null}function DQ(){let Q=YQ()??T();return Q?G(Q):null}function xQ(Q){return G(Q)?.path??null}function EQ(){return D(C())}var A="beacon_ws";function F(Q,X){let Z=Q.headers.get("cookie");if(!Z)return null;for(let $ of Z.split(";")){let J=$.indexOf("=");if(J===-1)continue;if($.slice(0,J).trim()===X)return decodeURIComponent($.slice(J+1).trim())}return null}function RQ(Q){let X=Q.headers.get("x-beacon-workspace");if(X&&G(X))return X;let Z=F(Q,A);if(Z&&G(Z))return Z;return null}var JQ="x-beacon-workspace-path";async function WQ(Q){let X=Q.headers.get("x-beacon-workspace");if(X&&G(X))return X;let Z=Q.headers.get(JQ);if(Z&&(!X||R(Z)===X)){let J=ZQ(Z);return await GQ(J.id),J.id}let $=F(Q,A);if($&&G($))return $;return null}var I=new a;function AQ(Q,X){return Q?I.run(Q,X):X()}function YQ(){return I.getStore()??null}var z=new Set;function FQ(Q){z.delete(V(j(Q),"db.sqlite"))}async function GQ(Q){let X=j(Q),Z=V(X,"db.sqlite"),$=D(Z);if($&&z.has(Z))return{ok:!0,created:!1,migrated:!1};try{U(X,{recursive:!0});let{provisionDb:J}=await _().then(() => v),Y=await J(QQ(Q));return z.add(Z),{ok:!0,created:!$,migrated:$&&Y.migrated}}catch(J){return{ok:!1,created:!1,migrated:!1,error:J instanceof Error?J.message:String(J)}}}export{RQ as workspaceIdFromRequest,fQ as touchWorkspace,$Q as setActiveId,AQ as runWithWorkspace,WQ as resolveRequestWorkspaceId,TQ as repoRootFrom,vQ as removeWorkspace,EQ as registryExists,xQ as pathForWorkspace,XQ as listWorkspaces,R as idForPath,G as getWorkspace,YQ as getPinnedWorkspaceId,T as getActiveId,FQ as forgetWorkspaceDb,GQ as ensureWorkspaceDb,QQ as dbUrlFor,j as dataDirFor,DQ as currentWorkspace,K as beaconHome,ZQ as addWorkspace,_Q as activeWorkspace,JQ as BEACON_WS_PATH_HEADER,A as BEACON_WS_COOKIE};
+var m=Object.defineProperty;var p=(Q)=>Q;function h(Q,X){this[Q]=p.bind(null,X)}var l=(Q,X)=>{for(var Z in X)m(Q,Z,{get:X[Z],enumerable:!0,configurable:!0,set:h.bind(X,Z)})};var c=(Q,X)=>()=>(Q&&(X=Q(Q=0)),X);var A={};l(A,{provisionDb:()=>ZQ});import{createClient as n}from"@libsql/client";import{drizzle as s}from"drizzle-orm/libsql";import{migrate as o}from"drizzle-orm/libsql/migrator";import{readMigrationFiles as d}from"drizzle-orm/migrator";import{dirname as C,join as a}from"path";import{fileURLToPath as t}from"url";async function U(Q,X){return(await Q.execute({sql:"SELECT 1 FROM sqlite_master WHERE type='table' AND name = ?",args:[X]})).rows.length>0}async function QQ(Q,X){let Z=await Q.execute(`PRAGMA table_info("${X}")`);return new Set(Z.rows.map(($)=>String($.name)))}async function x(Q){if(!await U(Q,"__drizzle_migrations"))return 0;let X=await Q.execute('SELECT count(*) AS n FROM "__drizzle_migrations"');return Number(X.rows[0]?.n??0)}async function XQ(Q){for(let[X,Z]of Object.entries(e)){if(!await U(Q,X))continue;let $=await QQ(Q,X);for(let J of Z){if(!$.has(J))continue;await Q.execute(`UPDATE "${X}" SET "${J}" = CAST((julianday("${J}") - 2440587.5) * 86400000 AS INTEGER) WHERE typeof("${J}") = 'text'`)}}}async function ZQ(Q,X=i){let Z=n({url:Q});try{await Z.execute("PRAGMA journal_mode = WAL;"),await Z.execute("PRAGMA foreign_keys = ON;"),await Z.execute("PRAGMA busy_timeout = 5000;");let $=await U(Z,"__drizzle_migrations"),J=await U(Z,"Node"),G=!1;if(J&&!$){let K=d({migrationsFolder:X})[0];if(K)await Z.execute('CREATE TABLE IF NOT EXISTS "__drizzle_migrations" (id SERIAL PRIMARY KEY, hash text NOT NULL, created_at numeric)'),await Z.execute({sql:'INSERT INTO "__drizzle_migrations" ("hash", "created_at") VALUES (?, ?)',args:[K.hash,K.folderMillis]}),G=!0}let N=await x(Z);if(await o(s(Z),{migrationsFolder:X}),await x(Z)>N)G=!0;return await XQ(Z),{migrated:G}}finally{Z.close()}}var r,i,e;var I=c(async()=>{r=C(C(C(t(import.meta.url)))),i=process.env.BEACON_MIGRATIONS_DIR||a(r,"drizzle"),e={Node:["createdAt","updatedAt"],Note:["createdAt","updatedAt"],DbTable:["createdAt","updatedAt"],Endpoint:["createdAt","updatedAt"],DraftTable:["createdAt"],SyncState:["codeGraphSyncedAt","updatedAt"],AppSetting:["updatedAt"],ProjectMeta:["updatedAt"],CodeFile:["updatedAt"]}});import{AsyncLocalStorage as $Q}from"async_hooks";import{spawnSync as JQ}from"child_process";import{createHash as YQ}from"crypto";import{existsSync as q,mkdirSync as M,readFileSync as O,writeFileSync as f}from"fs";import{homedir as D}from"os";import{basename as GQ,join as Y,parse as VQ,resolve as R}from"path";function B(){return process.env.BEACON_HOME||Y(D(),".beacon")}function T(){return Y(B(),"workspaces.json")}function j(Q){return YQ("sha256").update(Q).digest("hex").slice(0,12)}function RQ(Q=process.cwd()){let X=JQ("git",["rev-parse","--show-toplevel"],{cwd:Q,stdio:["ignore","pipe","ignore"]});if(X.status===0){let Z=X.stdout?.toString().trim();if(Z)return Z}return Q}function F(Q){let X=R(Q);return X!==R(D())&&X!==VQ(X).root}function W(){return Y(B(),"deleted.json")}function _(){try{let Q=JSON.parse(O(W(),"utf8"));return Array.isArray(Q)?Q:[]}catch{return[]}}function S(Q){M(B(),{recursive:!0}),f(W(),JSON.stringify(Q,null,2))}function P(Q){return _().includes(Q)}function qQ(Q){let X=_();if(!X.includes(Q))S([...X,Q])}function BQ(Q){let X=_();if(X.includes(Q))S(X.filter((Z)=>Z!==Q))}function u(Q){return Y(B(),Q)}function KQ(Q){return`file:${Y(u(Q),"db.sqlite")}`}function L(){try{let Q=JSON.parse(O(T(),"utf8"));return Array.isArray(Q)?Q:[]}catch{return[]}}function v(Q){M(B(),{recursive:!0}),f(T(),JSON.stringify(Q,null,2))}function MQ(){return L().sort((Q,X)=>X.lastOpenedAt.localeCompare(Q.lastOpenedAt))}function V(Q){return L().find((X)=>X.id===Q)??null}function y(Q,X,Z=new Date().toISOString()){if(!F(Q))throw Error(`beacon: refusing to register a non-repo path as a workspace: ${Q}`);let $=j(Q);if(P($))throw Error(`beacon: workspace ${$} (${Q}) was deleted \u2014 run \`beacon\` or /beacon-init to re-add it`);let J=L(),G=J.find((z)=>z.id===$),N={id:$,path:Q,name:X||G?.name||GQ(Q),lastOpenedAt:Z},K=[N,...J.filter((z)=>z.id!==$)];return M(u($),{recursive:!0}),v(K),N}function DQ(Q,X){return BQ(j(Q)),y(Q,X)}function FQ(Q,X=new Date().toISOString()){let Z=L(),$=Z.find((J)=>J.id===Q);if(!$)return;$.lastOpenedAt=X,v(Z)}function WQ(Q){if(v(L().filter((X)=>X.id!==Q)),E()===Q)LQ(MQ()[0]?.id??null)}function k(){return Y(B(),"active")}function E(){try{return O(k(),"utf8").trim()||null}catch{return null}}function LQ(Q){M(B(),{recursive:!0}),f(k(),Q??"")}function SQ(){let Q=E();return Q?V(Q):null}function PQ(){let Q=UQ()??E();return Q?V(Q):null}function yQ(Q){return V(Q)?.path??null}function kQ(){return q(T())}var w="beacon_ws";function b(Q,X){let Z=Q.headers.get("cookie");if(!Z)return null;for(let $ of Z.split(";")){let J=$.indexOf("=");if(J===-1)continue;if($.slice(0,J).trim()===X)return decodeURIComponent($.slice(J+1).trim())}return null}function wQ(Q){let X=Q.headers.get("x-beacon-workspace");if(X&&V(X))return X;let Z=b(Q,w);if(Z&&V(Z))return Z;return null}var NQ="x-beacon-workspace-path";async function bQ(Q){let X=Q.headers.get("x-beacon-workspace");if(X&&V(X))return X;let Z=Q.headers.get(NQ);if(Z&&F(Z)&&!P(j(Z))&&(!X||j(Z)===X)){let J=y(Z);return await jQ(J.id),J.id}let $=b(Q,w);if($&&V($))return $;return null}var g=new $Q;function gQ(Q,X){return Q?g.run(Q,X):X()}function UQ(){return g.getStore()??null}var H=new Set;function mQ(Q){H.delete(Y(u(Q),"db.sqlite"))}async function jQ(Q){let X=u(Q),Z=Y(X,"db.sqlite"),$=q(Z);if($&&H.has(Z))return{ok:!0,created:!1,migrated:!1};try{M(X,{recursive:!0});let{provisionDb:J}=await I().then(() => A),G=await J(KQ(Q));return H.add(Z),{ok:!0,created:!$,migrated:$&&G.migrated}}catch(J){return{ok:!1,created:!1,migrated:!1,error:J instanceof Error?J.message:String(J)}}}export{wQ as workspaceIdFromRequest,FQ as touchWorkspace,qQ as tombstoneWorkspace,LQ as setActiveId,gQ as runWithWorkspace,bQ as resolveRequestWorkspaceId,RQ as repoRootFrom,WQ as removeWorkspace,kQ as registryExists,DQ as registerWorkspaceExplicit,yQ as pathForWorkspace,MQ as listWorkspaces,P as isWorkspaceDeleted,F as isRegistrableWorkspacePath,j as idForPath,V as getWorkspace,UQ as getPinnedWorkspaceId,E as getActiveId,mQ as forgetWorkspaceDb,jQ as ensureWorkspaceDb,KQ as dbUrlFor,u as dataDirFor,PQ as currentWorkspace,BQ as clearWorkspaceTombstone,B as beaconHome,y as addWorkspace,SQ as activeWorkspace,NQ as BEACON_WS_PATH_HEADER,w as BEACON_WS_COOKIE};

package/drizzle/0006_optimal_chronomancer.sql

@@ -0,0 +1,2 @@
+ALTER TABLE `Node` ADD `layer` text;--> statement-breakpoint
+ALTER TABLE `ProjectMeta` ADD `hasFrontend` integer;