@hurshb50/setup-ubuntu 0.0.3 → 1.0.1

package/README.md

@@ -1,6 +1,6 @@
 # setup-ubuntu
 
-Sets up a fresh Ubuntu machine with a standard set of tools, configuration, and dotfiles.
+Sets up a fresh Ubuntu machine with tools, configuration, and dotfiles.
 
 ## Installation
 
@@ -10,8 +10,19 @@ curl -fsSL https://vite.plus | bash
 vpx @hurshb50/setup-ubuntu
 ```
 
-## Publishing
+## After Installation
+
+Open a new terminal, then:
 
-Run the `publish.yaml` workflow from the Actions tab, choosing `patch`, `minor`, or `major` for the version bump. CI checks, tests, builds, bumps the version, tags it, and stages the package on npm. It uses OIDC trusted publishing, so no npm token is needed.
+- Log out and back in to use Docker without `sudo`.
+- Sign in to Zed, 1Password, and Chrome.
+- Run `gh auth login` to authenticate the GitHub CLI.
+- Pick a wallpaper in HydraPaper.
+- Put personal shell config in `~/custom.bashrc`, not `~/.bashrc`.
+- Update `/.gitconfig` if you are on work machine
+
+## Publishing
 
-Nothing goes live until you approve the staged package on npmjs.com under Staged Packages. The `release.yaml` workflow creates the GitHub release once the version is live.
+1. Run `publish.yaml` from the Actions tab with a `patch`, `minor`, or `major` bump. CI checks, tests, builds, tags, and stages the package, using OIDC instead of a token.
+2. Approve the staged package on npmjs.com to publish it.
+3. `release.yaml` creates the GitHub release once the version is live.

package/distribution/assets/.gitconfig

@@ -0,0 +1,31 @@
+[user]
+	name = Hursh Patel
+	email = hurshb50@gmail.com
+
+[core]
+	editor = zed --wait
+
+[init]
+	defaultBranch = main
+
+[push]
+	autoSetupRemote = true
+
+[merge]
+	conflictStyle = zdiff3
+
+[diff]
+	algorithm = histogram
+
+[fetch]
+	prune = true
+
+[rerere]
+	enabled = true
+
+[branch]
+	sort = -committerdate
+
+[credential "https://github.com"]
+	helper =
+	helper = !/usr/bin/gh auth git-credential

package/distribution/assets/AGENTS.md

@@ -1,58 +1,15 @@
-# Voice
-
-Default to one to three sentences. Answer, then stop. No opening praise and no
-closing summary of what you just wrote.
-
-Lead with the answer. The first sentence answers the question or states what
-changed. Detail I cannot infer comes after it, and only if it earns its place.
-
-Scale length to the task, not to your effort. One file changed gets two
-sentences. A tradeoff I must weigh can run a few short paragraphs. If a reply
-needs more than a screenful, say why in line one. Otherwise revise it shorter.
-
-Prose first. Bullets are for genuinely parallel items, not for chopping sentences
-into pieces.
-
-Plain words. Cut hedging, preamble, adverbs, and openers like "it is important to
-note". Delve, resolve, crucial, robust, seamless, leverage, showcase, testament,
-landscape, and underscore are banned. So is any non-technical word you would not
-say out loud. No em dashes, and no parentheses for asides. Sentence case headings.
-Bold at most one phrase per reply.
-
-Write the point once. No "not just X, but Y", no padding a list to three, and no
-bullet whose lead-in restates its own line.
-
-Terse means fewer sentences, not denser ones. Keep the articles and the verbs.
-
-Keep one idea per sentence, most of them under 15 words. Split anything past 20.
-
 # Formatting
 
-Blank line between every paragraph, heading, list, and code block. A paragraph
-break is a full blank line, not just a wrap to the next line.
-
-Never let two prose paragraphs run together, and never butt a heading against the
-text above it. The whitespace is part of the answer, not decoration.
+- Sentences: 8 words or fewer
+- Paragraphs: 2 sentences or fewer
+- Sections: 3 paragraphs or fewer
+- Lists: 4 words per item
+- Tables: 3 columns or fewer, 3 words or fewer per cell
+- Diagrams: 6 nodes, one per level
 
 # Explanation
 
-Show the code. Quote the lines that do the thing you are explaining, trimmed to
-the ones that matter. Describing what code does is not explaining it. The lines
-do that.
-
-Draw a diagram when the answer is a flow, a sequence, or a state machine. Keep it
-under ten nodes and taller than it is wide.
-
-Snippets, diagrams, and before-and-after pairs do not count against the length
-budget.
-
-# Delegation
-
-Do the work in this thread by default. Spawn a subagent for reads that cost more
-than they return: codebase search, online research, docs and changelog lookups,
-log and CI triage, enumerating call sites, mapping an unfamiliar repo, and
-summarizing a large diff.
-
-Brief it like it has no history, because it does not. "Look into the auth flow"
-fails; "Find where a session token is validated in src/ and return the file, the
-function, and whether expiry is checked" works.
+- Simple
+- Straightforward
+- Minimal
+- Avoid verbosity

package/distribution/assets/skills/design/SKILL.md

@@ -6,56 +6,39 @@ disable-model-invocation: true
 
 # Design
 
-Turn a vague architectural idea into one API shape we agree on.
+Turn a vague idea into one API shape.
 
-Produce the API shape, not the implementation: types, function signatures, classes with their fields and methods. No function bodies, no pseudocode, no queries. If a decision depends on how something would be built, say so in prose and let me decide.
+## Output
 
-## Phase 1. Interview
-
-Interview me before designing anything.
-
-Ask me about the decisions the design has to make.
-
-Some decisions depend on others. Ask the unblocked ones now and leave the rest for a later round.
-
-When a question lands better as an example than as prose, add one: a short snippet of a caller using each option, a sketch of the types, or a diagram of the flow. Keep it small and illustrative. This is not meant to represent the final design.
-
-One option per line, each labeled, never run together in a paragraph. Assume I have not read the code you are asking about: name each option by what it does, and quote the signature, variable, or line it turns on, so I can judge it without opening the file.
-
-Put every unblocked question in one round, numbered, each with your recommended answer and whatever example it needs. Then stop and wait for mine.
+- Produce the API shape
+- Types, signatures, classes with fields and methods
+- No implementation, no function bodies, no pseudocode
 
-Do not ask me for facts. Look them up, then ask me only what needs my judgement.
+## Phase 1. Interview
 
-Move on when the remaining questions can only be answered by trying designs. That is Phase 2.
+1. Ask only about decisions needing my judgement
+2. Move on when only trying designs can answer
 
 ## Phase 2. Ideation
 
-Spawn three or four subagents at once. They all solve the same problem, and each one takes a different approach.
-
-Send them different starting material. At least one starts from the code as it is today, and at least one ignores the current code and designs as if the problem were new.
+- Spawn 4 subagents at once
+- Send each one different starting material
 
 Each subagent returns:
 
-- The API shape: types, signatures, classes with fields and methods.
-- An example of a caller using it.
-- A short paragraph on what the API handles for the caller.
-- The rules a caller must follow, and how it fails.
-- What this approach makes worse.
-
-Read what comes back before Phase 3. Throw away any design that does not address the problem, and spawn a replacement with a different approach until you have three or four that do. Merge any two that describe the same shape, or re-run one with different starting material. If all of them match, either the domain forces that shape or the starting material was too alike. Tell me which you think it is.
-
-## Phase 3. Choose together
+- The API shape
+- An example caller
 
-Present all the designs.
+## Phase 3. Feedback
 
-For each design, show how a caller would use it: a code snippet or a diagram, whichever fits better.
-
-Then ask me for my feedback: what I like, what I do not like, and whether to run another round of Ideation or move on to Phase 4. Do not pick a winner.
+- Present all the designs
+- Show how a caller would use each one
+- Do not pick a winner
+- Ask what I like and dislike
+- Ask whether to run another round
 
 ## Phase 4. Converge
 
-Build one API shape from the parts I chose. It has to read as one design, not several stuck together. When two parts conflict, pick one and tell me why.
-
-Show it to me, then refine it from my feedback until I say it is done.
-
-Then output the same things the subagents returned, and explain why you chose each part. Say how much of the code we already have has to change.
+- Build one API shape from my choices
+- It must read as one design
+- Show it, then refine from my feedback

package/distribution/assets/skills/teach/SKILL.md

@@ -8,28 +8,10 @@ disable-model-invocation: true
 
 Any concept, in one sitting, from the ground up.
 
-## Before you start
-
-Assume I know nothing about this and have no context. Do not ask what I already know.
-
-Define every term the first time it appears, including ones that seem basic. Say what problem the concept solves and what it replaces.
-
-Do not refer to anything I have not been shown. No other files, no earlier conversations, no shared setup.
-
-Start at the beginning. Teach the first idea, then add one step at a time.
+Assume no prior knowledge and no context.
 
 ## The lesson
 
-Each section depends on the ones before it. Use a term only after you have defined it.
-
-Concrete before abstract. Show a case that works before you name the rule that explains it.
-
-One new idea at a time. If a sentence asks me to hold two at once, split it.
-
-Grow one running example. Do not hop between unrelated ones.
-
-## Ending
-
-Close with what this now lets me do or understand, in two sentences.
-
-Then the sources. Links to the pages you actually read, local paths for anything in this repo. Never invent a link, and if you did not read a source, say so.
+- Define every term before use, even basic ones
+- Each section depends on the ones before
+- Open with an example, then a definition

package/distribution/setup-ubuntu.mjs

@@ -10,7 +10,7 @@ import fs from "fs/promises";
 import { execa } from "execa";
 //#region package.json
 var name = "@hurshb50/setup-ubuntu";
-var version = "0.0.2";
+var version = "1.0.0";
 //#endregion
 //#region source/modules/logger/logger.ts
 var Logger = class Logger {
@@ -184,6 +184,19 @@ var DependencyManager = class {
 			}
 		}))).every((installation) => installation === true);
 	}
+	async authenticate() {
+		if (await this.isAuthenticated()) return;
+		process.stdout.write("Administrator access is required to install packages. You may be prompted for your password.\n");
+		try {
+			await execa("sudo", ["--validate"], {
+				stdin: "inherit",
+				stdout: "inherit",
+				stderr: "inherit"
+			});
+		} catch (error) {
+			throw new Error("Administrator access was not granted. Run 'sudo --validate' and then run this tool again.", { cause: error });
+		}
+	}
 	async install(dependencies, task) {
 		await this.enqueue([
 			"install",
@@ -195,8 +208,17 @@ var DependencyManager = class {
 	async update(task) {
 		await this.enqueue(["update"], task);
 	}
+	async isAuthenticated() {
+		try {
+			await execa("sudo", ["--non-interactive", "--validate"], { stdin: "ignore" });
+			return true;
+		} catch {
+			return false;
+		}
+	}
 	enqueue(managerArguments, task) {
 		const operation = this.queue.then(async () => {
+			if (!await this.isAuthenticated()) throw new Error("Administrator access is no longer available for apt-get. Run 'sudo --validate' and then run this tool again.");
 			const subprocess = execa("sudo", [
 				"env",
 				...["DEBIAN_FRONTEND=noninteractive", "NEEDRESTART_SUSPEND=1"],
@@ -204,13 +226,15 @@ var DependencyManager = class {
 				...managerArguments
 			], { stdin: "ignore" });
 			let partial = "";
-			subprocess.stdout?.on("data", (chunk) => {
+			const track = (chunk) => {
 				partial += chunk.toString();
 				const lines = partial.split(/\r\n|\r|\n/);
 				partial = lines.pop() ?? "";
 				const line = lines.at(-1)?.trim();
 				if (line) task.continue(line);
-			});
+			};
+			subprocess.stdout?.on("data", track);
+			subprocess.stderr?.on("data", track);
 			await subprocess;
 		});
 		this.queue = operation.catch(() => {});
@@ -563,14 +587,16 @@ var VersionControlSystem = class {
 		context.logger.add(task);
 		task.start();
 		const dependencies = ["git", "build-essential"];
-		if (await context.dependencyManager.isInstalled(dependencies)) {
-			task.finish();
-			return;
+		if (!await context.dependencyManager.isInstalled(dependencies)) {
+			task.continue("Update package manager");
+			await context.dependencyManager.update(task);
+			task.continue(`Installing dependencies: ${dependencies.join(", ")}`);
+			await context.dependencyManager.install(dependencies, task);
 		}
-		task.continue("Update package manager");
-		await context.dependencyManager.update(task);
-		task.continue(`Installing dependencies: ${dependencies.join(", ")}`);
-		await context.dependencyManager.install(dependencies, task);
+		const sourceFilePath = path.join(context.directories.assets, ".gitconfig");
+		const destinationFilePath = path.join(context.directories.home, ".gitconfig");
+		task.continue("Copy configuration");
+		await fs.copyFile(sourceFilePath, destinationFilePath);
 		task.finish();
 	}
 };
@@ -599,9 +625,10 @@ var Wallpapers = class {
 };
 //#endregion
 //#region source/setup-ubuntu.ts
-program.name(name).version(version).description("TODO").action(async () => {
+program.name(name).version(version).description("Sets up a fresh Ubuntu machine with a standard set of tools, configuration, and dotfiles.").action(async () => {
 	const logger = new Logger();
 	const dependencyManager = new DependencyManager();
+	await dependencyManager.authenticate();
 	logger.start();
 	const packages = [
 		new AgentRules(),

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@hurshb50/setup-ubuntu",
-    "version": "0.0.3",
+    "version": "1.0.1",
     "type": "module",
     "files": [
         "distribution"
@@ -41,7 +41,7 @@
             "onFail": "download"
         }
     },
-    "description": "TODO",
+    "description": "Sets up a fresh Ubuntu machine with a standard set of tools, configuration, and dotfiles.",
     "homepage": "https://github.com/hurshb50/setup-ubuntu#readme",
     "bugs": {
         "url": "https://github.com/hurshb50/setup-ubuntu/issues"