@slopus/beer 0.1.2 → 0.1.6

package/dist/_workflows/_index.d.ts

@@ -1,4 +1,4 @@
-import type { Context } from "@/types";
+import type { Context } from "../types.js";
 export interface Workflow {
     id: string;
     title: string;

package/dist/_workflows/_index.js

@@ -1,10 +1,10 @@
-import { text } from "@text";
-import { bootstrap } from "@/_workflows/bootstrap.js";
-import { checkpointWorkflow } from "@/_workflows/checkpointWorkflow.js";
-import { planWorkflow } from "@/_workflows/planWorkflow.js";
-import { ralphLoopWorkflow } from "@/_workflows/ralphLoopWorkflow.js";
-import { ralphWorkflow } from "@/_workflows/ralphWorkflow.js";
-import { researchWorkflow } from "@/_workflows/researchWorkflow.js";
+import { text } from "../text/text.js";
+import { bootstrap } from "../_workflows/bootstrap.js";
+import { checkpointWorkflow } from "../_workflows/checkpointWorkflow.js";
+import { planWorkflow } from "../_workflows/planWorkflow.js";
+import { ralphLoopWorkflow } from "../_workflows/ralphLoopWorkflow.js";
+import { ralphWorkflow } from "../_workflows/ralphWorkflow.js";
+import { researchWorkflow } from "../_workflows/researchWorkflow.js";
 export const workflowBootstrap = {
     id: "bootstrap",
     title: text.workflow_bootstrap_title,

package/dist/_workflows/bootstrap.d.ts

@@ -1,4 +1,4 @@
-import type { Context } from "@/types";
+import type { Context } from "../types.js";
 /**
  * Runs the interactive bootstrap workflow for holdmybeer.
  */

package/dist/_workflows/bootstrap.js

@@ -1,17 +1,17 @@
-import { text, textFormatKey } from "@text";
-import { generateReadme } from "@/_workflows/steps/generateReadme.js";
-import { beerOriginalPathResolve } from "@/modules/beer/beerOriginalPathResolve.js";
-import { gitRemoteEnsure } from "@/modules/git/gitRemoteEnsure.js";
-import { gitRepoCheckout } from "@/modules/git/gitRepoCheckout.js";
-import { gitRepoEnsure } from "@/modules/git/gitRepoEnsure.js";
-import { githubOwnerChoicesGet } from "@/modules/github/githubOwnerChoicesGet.js";
-import { githubRepoCreate } from "@/modules/github/githubRepoCreate.js";
-import { githubRepoNameResolve } from "@/modules/github/githubRepoNameResolve.js";
-import { githubRepoStatusGet } from "@/modules/github/githubRepoStatusGet.js";
-import { githubRepoUrlBuild } from "@/modules/github/githubRepoUrlBuild.js";
-import { githubViewerGet } from "@/modules/github/githubViewerGet.js";
-import { promptConfirm } from "@/modules/prompt/promptConfirm.js";
-import { promptInput } from "@/modules/prompt/promptInput.js";
+import { text, textFormatKey } from "../text/text.js";
+import { generateReadme } from "../_workflows/steps/generateReadme.js";
+import { beerOriginalPathResolve } from "../modules/beer/beerOriginalPathResolve.js";
+import { gitRemoteEnsure } from "../modules/git/gitRemoteEnsure.js";
+import { gitRepoCheckout } from "../modules/git/gitRepoCheckout.js";
+import { gitRepoEnsure } from "../modules/git/gitRepoEnsure.js";
+import { githubOwnerChoicesGet } from "../modules/github/githubOwnerChoicesGet.js";
+import { githubRepoCreate } from "../modules/github/githubRepoCreate.js";
+import { githubRepoNameResolve } from "../modules/github/githubRepoNameResolve.js";
+import { githubRepoStatusGet } from "../modules/github/githubRepoStatusGet.js";
+import { githubRepoUrlBuild } from "../modules/github/githubRepoUrlBuild.js";
+import { githubViewerGet } from "../modules/github/githubViewerGet.js";
+import { promptConfirm } from "../modules/prompt/promptConfirm.js";
+import { promptInput } from "../modules/prompt/promptInput.js";
 /**
  * Runs the interactive bootstrap workflow for holdmybeer.
  */

package/dist/_workflows/checkpointWorkflow.d.ts

@@ -1,4 +1,4 @@
-import type { Context } from "@/types";
+import type { Context } from "../types.js";
 /**
  * Runs a checkpoint workflow with AI-generated commit message.
  * Expects: repository is initialized and configured for pushing to origin/main.

package/dist/_workflows/checkpointWorkflow.js

@@ -1,5 +1,5 @@
-import { text } from "@text";
-import { promptInput } from "@/modules/prompt/promptInput.js";
+import { text } from "../text/text.js";
+import { promptInput } from "../modules/prompt/promptInput.js";
 /**
  * Runs a checkpoint workflow with AI-generated commit message.
  * Expects: repository is initialized and configured for pushing to origin/main.

package/dist/_workflows/context/context.d.ts

@@ -1,5 +1,5 @@
-import { PathLock } from "@/modules/util/pathLock.js";
-import type { BeerSettings, GitHubRepoRef, PathLockResult, ProviderDetection, ProviderModelSelectionMode } from "@/types";
+import { PathLock } from "../../modules/util/pathLock.js";
+import type { BeerSettings, GitHubRepoRef, PathLockResult, ProviderDetection, ProviderModelSelectionMode } from "../../types.js";
 export interface ContextCheckpointOptions {
     remote?: string;
     branch?: string;

package/dist/_workflows/context/context.js

@@ -1,16 +1,16 @@
 import { lstat, mkdir, stat, symlink, unlink, writeFile } from "node:fs/promises";
 import path from "node:path";
-import { text as catalog } from "@text";
-import { contextApplyConfig } from "@/_workflows/context/utils/contextApplyConfig.js";
-import { contextAskGithubRepo } from "@/_workflows/context/utils/contextAskGithubRepo.js";
-import { contextGitignoreEnsure } from "@/_workflows/context/utils/contextGitignoreEnsure.js";
-import { progressMultilineStart } from "@/_workflows/context/utils/progressMultilineStart.js";
-import { generateCommit } from "@/_workflows/steps/generateCommit.js";
-import { beerSettingsRead } from "@/modules/beer/beerSettingsRead.js";
-import { gitPush } from "@/modules/git/gitPush.js";
-import { gitStageAndCommit } from "@/modules/git/gitStageAndCommit.js";
-import { providerDetect } from "@/modules/providers/providerDetect.js";
-import { PathLock } from "@/modules/util/pathLock.js";
+import { text as catalog } from "../../text/text.js";
+import { contextApplyConfig } from "../../_workflows/context/utils/contextApplyConfig.js";
+import { contextAskGithubRepo } from "../../_workflows/context/utils/contextAskGithubRepo.js";
+import { contextGitignoreEnsure } from "../../_workflows/context/utils/contextGitignoreEnsure.js";
+import { progressMultilineStart } from "../../_workflows/context/utils/progressMultilineStart.js";
+import { generateCommit } from "../../_workflows/steps/generateCommit.js";
+import { beerSettingsRead } from "../../modules/beer/beerSettingsRead.js";
+import { gitPush } from "../../modules/git/gitPush.js";
+import { gitStageAndCommit } from "../../modules/git/gitStageAndCommit.js";
+import { providerDetect } from "../../modules/providers/providerDetect.js";
+import { PathLock } from "../../modules/util/pathLock.js";
 /**
  * Runtime workflow context with repository-aware helpers.
  * Expects: projectPath points to the repository root.

package/dist/_workflows/context/context.spec.js

@@ -34,7 +34,7 @@ vi.mock("@/_workflows/context/utils/contextGitignoreEnsure.js", () => ({
 vi.mock("@/_workflows/context/utils/progressMultilineStart.js", () => ({
     progressMultilineStart: progressMultilineStartMock
 }));
-import { Context } from "@/_workflows/context/context.js";
+import { Context } from "../../_workflows/context/context.js";
 describe("Context", () => {
     beforeEach(() => {
         providerDetectMock.mockReset();

package/dist/_workflows/context/utils/contextApplyConfig.d.ts

@@ -1,4 +1,4 @@
-import type { BeerSettings } from "@/types";
+import type { BeerSettings } from "../../../types.js";
 /**
  * Applies a mutation to current settings and persists the result to .beer/settings.json.
  * Expects: projectPath is the repository root.

package/dist/_workflows/context/utils/contextApplyConfig.js

@@ -1,5 +1,5 @@
 import path from "node:path";
-import { beerSettingsWrite } from "@/modules/beer/beerSettingsWrite.js";
+import { beerSettingsWrite } from "../../../modules/beer/beerSettingsWrite.js";
 /**
  * Applies a mutation to current settings and persists the result to .beer/settings.json.
  * Expects: projectPath is the repository root.

package/dist/_workflows/context/utils/contextApplyConfig.spec.js

@@ -3,7 +3,7 @@ const beerSettingsWriteMock = vi.hoisted(() => vi.fn());
 vi.mock("@/modules/beer/beerSettingsWrite.js", () => ({
     beerSettingsWrite: beerSettingsWriteMock
 }));
-import { contextApplyConfig } from "@/_workflows/context/utils/contextApplyConfig.js";
+import { contextApplyConfig } from "../../../_workflows/context/utils/contextApplyConfig.js";
 describe("contextApplyConfig", () => {
     it("applies update, persists with refreshed timestamp, and keeps input immutable", async () => {
         const current = {

package/dist/_workflows/context/utils/contextAskGithubRepo.d.ts

@@ -1,4 +1,4 @@
-import type { GitHubRepoRef } from "@/types";
+import type { GitHubRepoRef } from "../../../types.js";
 /**
  * Prompts until a valid and accessible GitHub repository is provided.
  * Expects: question is a non-empty prompt text for the user.

package/dist/_workflows/context/utils/contextAskGithubRepo.js

@@ -1,6 +1,6 @@
-import { githubRepoExists } from "@/modules/github/githubRepoExists.js";
-import { githubRepoParse } from "@/modules/github/githubRepoParse.js";
-import { promptInput } from "@/modules/prompt/promptInput.js";
+import { githubRepoExists } from "../../../modules/github/githubRepoExists.js";
+import { githubRepoParse } from "../../../modules/github/githubRepoParse.js";
+import { promptInput } from "../../../modules/prompt/promptInput.js";
 /**
  * Prompts until a valid and accessible GitHub repository is provided.
  * Expects: question is a non-empty prompt text for the user.

package/dist/_workflows/context/utils/contextAskGithubRepo.spec.js

@@ -11,7 +11,7 @@ vi.mock("@/modules/github/githubRepoParse.js", () => ({
 vi.mock("@/modules/github/githubRepoExists.js", () => ({
     githubRepoExists: githubRepoExistsMock
 }));
-import { contextAskGithubRepo } from "@/_workflows/context/utils/contextAskGithubRepo.js";
+import { contextAskGithubRepo } from "../../../_workflows/context/utils/contextAskGithubRepo.js";
 describe("contextAskGithubRepo", () => {
     beforeEach(() => {
         promptInputMock.mockReset();

package/dist/_workflows/context/utils/contextGitignoreEnsure.spec.js

@@ -2,7 +2,7 @@ import { mkdtemp, readFile, rm, writeFile } from "node:fs/promises";
 import os from "node:os";
 import path from "node:path";
 import { afterEach, describe, expect, it } from "vitest";
-import { contextGitignoreEnsure } from "@/_workflows/context/utils/contextGitignoreEnsure.js";
+import { contextGitignoreEnsure } from "../../../_workflows/context/utils/contextGitignoreEnsure.js";
 const tempDirs = [];
 afterEach(async () => {
     await Promise.all(tempDirs.splice(0).map((dir) => rm(dir, { recursive: true, force: true })));

package/dist/_workflows/context/utils/progressMultilineStart.spec.js

@@ -1,5 +1,5 @@
 import { afterEach, describe, expect, it, vi } from "vitest";
-import { progressMultilineStart } from "@/_workflows/context/utils/progressMultilineStart.js";
+import { progressMultilineStart } from "../../../_workflows/context/utils/progressMultilineStart.js";
 const originalIsTTY = process.stderr.isTTY;
 afterEach(() => {
     process.stderr.isTTY = originalIsTTY;

package/dist/_workflows/planWorkflow.d.ts

@@ -1,4 +1,4 @@
-import type { Context } from "@/types";
+import type { Context } from "../types.js";
 /**
  * Builds a persisted implementation-task tree from blueprint and product source documents.
  * Expects: at least one planning source document exists in standard doc/ paths.

package/dist/_workflows/planWorkflow.js

@@ -1,14 +1,14 @@
 import path from "node:path";
-import { text } from "@text";
+import { text } from "../text/text.js";
 import { z } from "zod";
-import { planPromptChildren } from "@/modules/plan/planPromptChildren.js";
-import { planPromptDocument } from "@/modules/plan/planPromptDocument.js";
-import { planPromptPicker } from "@/modules/plan/planPromptPicker.js";
-import { planPromptRoot } from "@/modules/plan/planPromptRoot.js";
-import { planSourceDocumentsResolve } from "@/modules/plan/planSourceDocumentsResolve.js";
-import { treeSearchRun } from "@/modules/tree/treeSearchRun.js";
-import { treeStateRead } from "@/modules/tree/treeStateRead.js";
-import { treeStateRender } from "@/modules/tree/treeStateRender.js";
+import { planPromptChildren } from "../modules/plan/planPromptChildren.js";
+import { planPromptDocument } from "../modules/plan/planPromptDocument.js";
+import { planPromptPicker } from "../modules/plan/planPromptPicker.js";
+import { planPromptRoot } from "../modules/plan/planPromptRoot.js";
+import { planSourceDocumentsResolve } from "../modules/plan/planSourceDocumentsResolve.js";
+import { treeSearchRun } from "../modules/tree/treeSearchRun.js";
+import { treeStateRead } from "../modules/tree/treeStateRead.js";
+import { treeStateRender } from "../modules/tree/treeStateRender.js";
 const planNodeFrontmatterSchema = z.object({
     title: z.string().min(1),
     slug: z.string().min(1),

package/dist/_workflows/prompts/PROMPT_AGENTS_MD.md

@@ -0,0 +1,168 @@
+You are a senior software architect producing an AGENTS.md file — the definitive agent instruction manual for an AI coding assistant that will build a **new product from scratch**. There is no existing codebase to scan. Instead, you have research documents from studying an original project, and you must synthesize conventions, patterns, and rules for the new product based on what was learned.
+
+## Context
+
+- **Output File Path**: {outputPath}
+- **Original source repository:** {sourceFullName} (Use a `gh` tool to look into issues)
+- **Local checkout path:** {originalCheckoutPath} (the original project we studied — read for reference, not to copy)
+- **Product name:** {productName}
+
+The local checkout is the **original project we studied**. It is a reference, not our codebase. We are building a new product informed by what we learned from dissecting this one.
+
+Five documents have already been generated by analyzing the original project. Read them before starting:
+
+- **Research Summary**: {researchPath} — structured analysis of the original project's identity, architecture, dependencies, development lifecycle, conventions, and hidden knowledge.
+- **Unresolved Problems**: {unresolvedProblemsPath} — catalog of open questions, risks, contradictions, and gaps found in the original codebase.
+- **Key Decisions**: {decisionsPath} — comprehensive catalog of every significant decision visible in the original project, with analysis of what to keep and what to change.
+- **Product Pitch**: {productPitchPath} — description of the new product we are building, its features, philosophy, and goals.
+- **Technology Stack**: {technologyStackPath} — comprehensive stack recommendation with exact tools, versions, and conventions for the new product.
+
+## Core objective
+
+Produce an AGENTS.md that an AI agent reads before every task on the **new product**. It must be:
+- **Prescriptive**: tell the agent exactly how to write code for this new project
+- **Actionable**: every rule can be followed mechanically
+- **Minimal**: no filler, no aspirational statements, no repeating what tools already enforce
+- **Informed**: conventions are derived from lessons learned (what worked in the original, what didn't, what we're doing differently)
+
+This is NOT a description of the original project's conventions. This is the rulebook for the new one.
+
+================================================================
+SYNTHESIS PROCESS
+================================================================
+Follow this process in order. Do not skip phases. Do not guess when you can read.
+
+### Phase 1: Extract what to keep
+
+1. **Read the key decisions document.** For each decision marked as "keep" or with positive assessment:
+   - Extract the convention it implies
+   - Note the evidence that it worked well in the original
+
+2. **Read the research summary.** Extract conventions that are:
+   - Consistently applied across the original codebase
+   - Well-suited to the new product's goals (from the product pitch)
+   - Worth carrying forward as rules
+
+3. **Read the product pitch.** Extract:
+   - Stated design philosophy and values
+   - Technical architecture choices
+   - Features that imply specific coding patterns
+
+### Phase 2: Extract what to change
+
+4. **Read the unresolved problems document.** For each problem:
+   - Determine if it was caused by a convention (or lack of one)
+   - Design a rule that prevents the same problem in the new product
+
+5. **Read the key decisions document.** For decisions marked as problematic or with tensions:
+   - Determine the better alternative for the new product
+   - Write a concrete rule that enforces the better choice
+
+6. **Read the original codebase selectively** — only to verify or clarify specific patterns referenced in the research documents. Do not do a full codebase scan. Look at:
+   - Build/lint/format configs — to understand which settings worked and which to adjust
+   - Package manifests — to understand runtime and dependency baseline
+   - A few source files — to see patterns referenced in the research in their full context
+
+### Phase 3: Design new conventions
+
+7. **Fill gaps.** The original project may lack conventions in areas that the new product needs. For each gap:
+   - Check if the unresolved problems document flagged the absence
+   - Design a convention appropriate for the new product's goals
+   - Mark it as "new" (not inherited from the original)
+
+8. **Resolve contradictions.** Where the original had inconsistent patterns:
+   - Pick the better pattern based on the key decisions analysis
+   - Write a single clear rule
+
+### Phase 4: Write the AGENTS.md
+
+9. **Structure the output** following the format below. Every rule must be:
+   - Concrete enough that an agent can follow it without asking questions
+   - Justified by evidence from the research documents (even if briefly)
+   - Applicable to a greenfield codebase (no references to "existing code" — there is none yet)
+
+================================================================
+OUTPUT FORMAT
+================================================================
+
+Produce a single AGENTS.md file with the following structure. Every section is mandatory. If a section does not apply, omit it entirely (do not write "N/A"). Use the shortest phrasing that is unambiguous.
+
+```markdown
+# {productName} agent notes
+
+## Goals
+{3-5 bullet points: project philosophy and non-negotiable principles.
+ Derived from the product pitch and key decisions. These are the values that inform every convention below.}
+
+## Conventions
+{Bullet list of top-level structural conventions: package layout, language, output format, source locations, test patterns.
+ Each convention should state what to do, not what was done in the original.}
+
+## Build, Test, and Development Commands
+{Exact commands with one-line descriptions. Include prerequisites and command dependencies.
+ Derived from the original project's working setup, adjusted for any tooling changes.
+ Format: `- command: `exact invocation` (tool) — description`}
+
+## Coding Style & Naming Conventions
+{Concrete rules for the new product.
+ Include: language, strictness, naming patterns, file size guidelines, import patterns.
+ Carry forward conventions that worked in the original. Replace conventions that caused problems.
+ Every rule should be phrased as an instruction: "Use X", "Prefer Y over Z", "Never do W".}
+
+## {Pattern-specific sections}
+{One section per major architectural pattern for the new product.
+ Section name should be the pattern name (e.g., "Central Types", "Text Catalog", "Facade Classes").
+ Each section: brief explanation + usage example + rules for when/how to apply.
+ Include patterns carried forward from the original AND new patterns designed for the new product.
+ Only include code examples when the pattern is non-obvious.}
+
+## Agent-Specific Notes
+{Operational rules for AI agents working on this new codebase:
+ - Safety constraints (git, node_modules, versions, releases)
+ - Multi-agent coordination rules (if the new product will use multiple agents)
+ - Investigation methodology
+ - Commit and documentation workflow
+ - Things that require explicit user approval}
+```
+
+### Section writing rules
+
+- **Bullet points over paragraphs.** Each rule is one bullet. Use sub-bullets for examples only.
+- **Code examples only when essential.** If a pattern is clear from a sentence, skip the example. If it requires a code block to be unambiguous, include a minimal example (5-15 lines).
+- **Good/bad examples only for counter-intuitive rules.** If the convention matches common practice, don't waste lines showing it.
+- **No redundancy with tooling.** Don't document rules that the linter/formatter already enforces, unless agents need to know them before writing code.
+- **Forward-looking, not backward-looking.** Write "Use prefix notation for function names" not "The original project used prefix notation." The agent doesn't need to know the history — just the rule.
+- **Be specific.** "Keep files under ~500 LOC" not "Keep files small". "`bun run test`" not "run the tests". "`githubRepoCreate`" not "use prefix naming".
+
+================================================================
+RESEARCH RULES
+================================================================
+
+- **Read the documents, not the codebase.** The four research documents are your primary source. Read the original codebase only to verify specific claims or see patterns in full context.
+- **Distinguish keep from change.** For every convention, consciously decide: is this worth keeping, or did it cause problems? The unresolved problems and key decisions documents are your guide.
+- **Design for a blank slate.** The new product has no legacy code. Conventions should be ideal, not compromised by backward compatibility.
+- **Prioritize actionability.** Ask: "Could an agent follow this rule on the first file they create?" If not, rephrase until they can.
+- **Omit the obvious.** Don't document things universal to the language/framework. Only document project-specific choices.
+- **Note deliberate absences.** If the new product deliberately omits something (no barrel files, no cleanup methods, no inference fallbacks), state it as a rule.
+- **Quantify when possible.** "~500 LOC per file" is better than "keep files small".
+- **Fill the gaps the original left open.** If the original had no convention for something important, and the unresolved problems flagged it, create one.
+
+================================================================
+QUALITY GATES
+================================================================
+
+Before finalizing, verify:
+1. Every rule is phrased as an instruction for the new product (not a description of the original)
+2. No aspirational or opinion-based statements ("clean code", "well-structured", "best practices")
+3. No duplication between sections
+4. No rules that merely restate linter/formatter enforcement
+5. Code examples are minimal and realistic for the new product (not copied from the original unless the pattern is identical)
+6. An agent reading this file could create the first module of the new product without asking any questions about style, naming, file placement, testing, or commit workflow
+7. Conventions that differ from the original are justified by evidence from the research documents
+8. The file is under 500 lines (aim for 200-400 — dense and scannable)
+
+If any check fails, revise before returning.
+
+## Output
+
+Output only raw markdown. No preamble, no explanation, no commentary outside the document structure.