github-delivery-os 1.1.0 → 1.2.0

package/.claude/skills/delivery-ops/SKILL.md

@@ -0,0 +1,172 @@
+---
+name: delivery-ops
+description: Operate a repo that has GitHub Delivery OS installed — create sprint/production-release/QA-request/bug issues that actually trigger its automation, comment as an approver in phrasing its workflows recognize, and check status (labels, latest comments, burn-down). Targets a specific repo via --repo; defaults to the current repo if this skill was installed into it and none is named. Use when asked to create a sprint, request a release, approve/decline a release, check release or sprint status, or demo/test Delivery OS against a given repo.
+---
+
+# Operate Delivery OS
+
+This drives the actual product — the workflows Delivery OS installs into a consumer repo — as a user of that repo would, not the tooling that ships the `github-delivery-os` package itself (that's the separate `release` skill). Use it to create issues that correctly trigger the installed automation, comment in a way the automation actually recognizes, and check what state something is in.
+
+## Which repo?
+
+Every command below takes `--repo <owner>/<name>` explicitly — never assume based on the working directory alone. Two ways this gets decided:
+
+- **This skill was installed via `npx github-delivery-os install --with-skill`, into a specific repo's own `.claude/skills/`.** In that case the current working directory *is* the repo Delivery OS is installed in, so it's a reasonable default target if the user doesn't name a different one — just confirm that's what they mean before acting.
+- **This skill is installed generically** (copied into `~/.claude/skills/`, available across every project). Here there's no natural default — the working directory could be anything. Ask which repo if it isn't named.
+
+Creating issues and comments in a repo is a visible, outward action — other collaborators see it. Confirm the target repo and intent before creating anything real, the same as any other action that shows up in someone else's GitHub activity.
+
+## Pre-flight check
+
+Before creating anything that depends on configuration, check the target repo actually has Delivery OS installed and configured — a silent no-op (nothing happens because a variable is unset) is more confusing than an upfront "this won't do much yet":
+
+- **Installed?** `gh api repos/<owner>/<repo>/contents/.github/workflows/authorize-deployment.yml --silent` (404 = not installed — suggest `npx github-delivery-os status .` or `install --with-templates` in that repo).
+- **Labels set up?** `gh label list --repo <owner>/<repo>` — look for `production`, `qa`, `qa-request`, `sprint`, `sprint-active`, `planning`, `declined`, `ready-for-deploy`. Missing labels mean `Setup Labels` hasn't been run there yet — offer to fix it directly rather than just reporting the gap: `gh workflow run setup-labels.yml --repo <owner>/<repo>` (it's a `workflow_dispatch` trigger, so this actually creates them on the spot). Confirm with the user first since it's a real change to their repo.
+- **Repo variables set?** `gh variable list --repo <owner>/<repo>` — look for `RELEASE_APPROVER`, `QA_APPROVER`, `QA_ASSIGNEES`. If unset, say so plainly: the issue will still get created, but `notify-release-approver` will ping the literal placeholder `release-approver`/`qa-approver`, not a real person. Setting these requires repo admin access (`gh variable set NAME --repo <owner>/<repo> --body <value>`) — don't set them without being asked to, since they name a real person as approver.
+
+## Creating issues
+
+`gh issue create` does not render GitHub's Issue Forms (the `.github/ISSUE_TEMPLATE/*.yml` files) — those only exist in the web UI. So the body has to be hand-built to match what a form submission would actually produce: `### <Field Label>` headings with the answer beneath each, because that heading text is exactly what the workflows regex-parse. Labels have to be passed explicitly too, since the template's auto-applied labels are also bypassed.
+
+**Show the constructed title, body, and labels before actually creating the issue** — this is a real, visible action in someone else's repo, not a preview in this conversation. Get confirmation on the content, not just the target repo, before calling `gh issue create`.
+
+**Sprint Planning** — triggers `sprint-child-creator` (one child issue per feature line, each labeled `sprint-active`, on open):
+- Title **must contain** the literal string `SPRINT -`, e.g. `SPRINT - Sprint 14`
+- Labels: `sprint`, `planning`
+- Body:
+  ```
+  ### Sprint Name
+
+  <name>
+
+  ### Sprint Start
+
+  YYYY-MM-DD
+
+  ### Sprint End
+
+  YYYY-MM-DD
+
+  ### Sprint Goal
+
+  <goal>
+
+  ### Sprint Features (One Per Line)
+
+  <feature one>
+  <feature two>
+  <feature three>
+
+  ### Sprint Approved
+
+  Pending
+  ```
+  One feature per line, no bullets/numbering (matches the template's own instruction — `sprint-child-creator`'s parser just splits on newlines).
+
+**Production Release** — triggers `notify-release-approver` on open (posts a comment tagging `RELEASE_APPROVER`), and later `authorize-deployment` on comments:
+- Title: `PRODUCTION RELEASE - <project> - vX.X.X`
+- Labels: `release`, `production`, `approval`
+- Body:
+  ```
+  ### Sprint Reference (Sprint Planning Issue #)
+
+  #<N>
+
+  ### Version / Build Number
+
+  vX.X.X
+
+  ### Release Summary
+
+  <summary>
+
+  ### QA Summary + Evidence Links
+
+  <links, or "None yet">
+
+  ### Overall QA Recommendation
+
+  Approve for Production
+
+  ### Deployment Authorized
+
+  No
+  ```
+  (`qa_recommendation` drives the "QA Recommendation" line `notify-release-approver` puts in its comment — use `Approve for Production`, `Reject Release`, or `Conditional Approval` verbatim, those are the three strings it checks for.)
+
+**QA Request** — triggers `auto-assign-qa` (assigns `QA_ASSIGNEES`) on open:
+- Title: `QA REQUEST - <feature/issue>`
+- Labels: `qa-request`
+- Body:
+  ```
+  ### Related Sprint Task Issue (#)
+
+  #<N>
+
+  ### What to Test
+
+  <what to test>
+
+  ### Environment + Build Link
+
+  <build link>
+
+  ### Acceptance Criteria
+
+  <criteria>
+
+  ### QA Outcome
+
+  Pending
+  ```
+
+**Bug Report**:
+- Title: `[BUG] <one-line summary>`
+- Labels: `bug`, `qa`
+- Body: mirror `bug_report.yml`'s fields (`Platform(s) Affected`, `Severity`, `Build / Version`, `Bug Summary`, `Steps to Reproduce`, `Expected Result`, `Actual Result`, `Test Environment`) as `### <label>` / answer pairs.
+
+**Task** — no automation trigger, just structured tracking:
+- Title: `TASK - <one-line summary>`
+- Labels: `task`
+- Body: mirror `task.yml`'s fields (`Task Summary`, `Description`, `Owner`, `Priority` — `P0 - Critical` / `P1 - High` / `P2 - Medium` / `P3 - Low`, `Status` — `Backlog` / `In Progress` / `Blocked` / `Ready for Review` / `Done`, `Acceptance Criteria`, `Artifacts / Links`) as `### <label>` / answer pairs.
+
+## Commenting as an approver
+
+`authorize-deployment` only registers a comment if **both** of these hold:
+- It's posted by the exact GitHub login configured in the repo's `RELEASE_APPROVER` or `QA_APPROVER` variable. `gh issue comment` posts as whichever account `gh auth status` shows — if that's not the configured approver, the comment is just a comment, nothing fires.
+- The comment **leads with** one of the recognized keywords (case-insensitive; anything after the keyword is fine, but the keyword itself has to be at the start):
+  - Release approve: `approved`, `approve`, `ok`, `go ahead`
+  - Release decline: `declined`, `rejected`, `reject`, `not approved`
+  - QA approve: `qa approved`, `approved`, `qa ok`, `looks good`
+
+A later qualifying comment from the same approver overrides an earlier one — a decline can be superseded by a later approval once fixes land, and vice versa.
+
+**Before posting, check that the authenticated login actually matches the approver you're commenting as** — `gh auth status` (or `gh api user --jq .login`) against the `RELEASE_APPROVER`/`QA_APPROVER` value from the pre-flight check. If they don't match, say so and stop: the comment would still post, look successful, and do nothing — a silent no-op that's easy to miss without this check, since `gh issue comment` succeeds either way.
+
+```
+gh issue comment <number> --repo <owner>/<repo> --body "Approved, ship it"
+```
+
+## Checking status
+
+- **Latest comment(s):** `gh issue view <number> --repo <owner>/<repo> --comments`
+- **Current labels:** `gh issue view <number> --repo <owner>/<repo> --json labels`
+- **Sprint burn-down:** read the sprint (parent) issue's body — `gh issue view <sprint-number> --repo <owner>/<repo> --json body` — and look for the `## 🚦 Sprint Status` section `auto-close-sprint` maintains (progress %, time elapsed %, health emoji, burn-down bar). It only exists after at least one child issue has closed.
+
+## Advancing a sprint
+
+Closing a sprint task (child) issue is what actually moves the burn-down — creating the sprint only creates the children, nothing updates until they close:
+
+```
+gh issue close <number> --repo <owner>/<repo>
+```
+
+`auto-close-sprint` fires on close, re-reads every `sprint-active` issue whose body contains `Parent Sprint: #<N>`, recomputes progress, and rewrites the sprint issue's `## 🚦 Sprint Status` section. At 100% it also closes the sprint issue itself and posts a completion comment. Re-check the sprint issue's body afterward to see the update — it happens as a side effect of closing the child, not as a response visible on the child issue itself.
+
+## Finding things
+
+When there's no issue number in hand yet:
+- **Production releases awaiting a decision:** `gh issue list --repo <owner>/<repo> --label production --state open`
+- **Active sprints:** `gh issue list --repo <owner>/<repo> --label sprint --state open` (title contains `SPRINT -`)
+- **Open QA requests:** `gh issue list --repo <owner>/<repo> --label qa-request --state open`
+- **A sprint's own children:** `gh issue list --repo <owner>/<repo> --label sprint-active --search "\"Parent Sprint: #<N>\" in:body"` — the exact-phrase quotes matter, otherwise the search matches "Parent", "Sprint", and the number as separate free-text terms instead of the literal phrase

package/README.md

@@ -30,7 +30,7 @@ The **GitHub Delivery Operating System (Delivery OS)** embeds structured intake,
 npx github-delivery-os install --with-templates .
 ```
 
-From your repo root. Add `--with-labels` to create labels via `gh` CLI (requires `gh auth`). Use `--dry-run` to preview first.
+From your repo root. Add `--with-labels` to create labels via `gh` CLI (requires `gh auth`). Add `--with-skill` to also drop in a [Claude Code](https://claude.com/claude-code) skill for operating this repo's Delivery OS from Claude Code — creating sprint/release/QA issues, commenting as an approver, checking status. Use `--dry-run` to preview first.
 
 **Alternative — clone and run script:**
 
@@ -77,6 +77,8 @@ Workflows and templates are **copied directly** into your repo. No `workflow_cal
 
 Installing via `npx github-delivery-os` (not the `scripts/install.sh` clone path) also writes `.github/delivery-os.json`, a small manifest recording the installed version — this is what powers the update check in `status`. It's only written when the files it describes are actually current (a fresh install, or `--overwrite`); a skip-mode install over existing files leaves it untouched rather than claiming a version that isn't really on disk. `uninstall` removes it.
 
+With `--with-skill`, a `.claude/skills/delivery-ops/SKILL.md` file is also written — a Claude Code skill scoped to this repo, so anyone working here with Claude Code can create issues that correctly trigger the workflows above, comment as an approver, and check status without knowing the underlying `gh` commands or issue-body formats by heart. It's opt-in and retroactive: `--with-skill` on any later `install` call adds it if it isn't there yet.
+
 ---
 
 ## Quick Start (After Install)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "github-delivery-os",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "A GitHub-native Delivery Governance Framework for structured sprint execution, QA review, and collaborative production release control.",
   "main": "src/install.js",
   "bin": {
@@ -38,8 +38,15 @@
   "files": [
     "bin",
     "src",
-    ".github/workflows",
-    ".github/ISSUE_TEMPLATE"
+    ".github/workflows/sprint-child-creator.yml",
+    ".github/workflows/auto-close-sprint.yml",
+    ".github/workflows/notify-release-approver.yml",
+    ".github/workflows/authorize-deployment.yml",
+    ".github/workflows/auto-assign-qa.yml",
+    ".github/workflows/telegram-issues.yml",
+    ".github/workflows/setup-labels.yml",
+    ".github/ISSUE_TEMPLATE",
+    ".claude/skills/delivery-ops"
   ],
   "engines": {
     "node": ">=14.0.0"

package/src/cli.js

@@ -20,6 +20,7 @@ program
   .description('Install workflows and templates into a repository')
   .option('-t, --with-templates', 'Copy issue templates (sprint, task, bug, QA, production release)')
   .option('-l, --with-labels', 'Create labels via gh CLI (requires gh auth)')
+  .option('-s, --with-skill', 'Add the delivery-ops Claude Code skill (.claude/skills/delivery-ops/SKILL.md)')
   .option('-o, --overwrite', 'Replace existing workflow/template files')
   .option('--no-overwrite', 'Skip existing files (default)')
   .option('-d, --dry-run', 'Show what would happen without changing files')
@@ -29,6 +30,7 @@ program
       targetDir,
       withTemplates: options.withTemplates ?? false,
       withLabels: options.withLabels ?? false,
+      withSkill: options.withSkill ?? false,
       overwrite: options.overwrite ?? false,
       dryRun: options.dryRun ?? false,
     });
@@ -46,11 +48,13 @@ program
   .command('uninstall [target]')
   .description('Remove Delivery OS workflows (and optionally templates)')
   .option('-t, --with-templates', 'Also remove issue templates')
+  .option('-s, --with-skill', 'Also remove the delivery-ops Claude Code skill')
   .option('-d, --dry-run', 'Show what would be removed without deleting')
   .action((target, options) => {
     runUninstall({
       targetDir: target || '.',
       withTemplates: options.withTemplates ?? false,
+      withSkill: options.withSkill ?? false,
       dryRun: options.dryRun ?? false,
     });
   });

package/src/install.js

@@ -4,7 +4,12 @@ const https = require('https');
 const { execFileSync } = require('child_process');
 
 const MANIFEST_FILE = 'delivery-os.json'; // written to .github/delivery-os.json in the target repo
+const SKILL_REL_PATH = path.join('.claude', 'skills', 'delivery-ops', 'SKILL.md'); // opt-in via --with-skill
 
+// If you add/remove/rename an entry here, also update package.json's "files"
+// array — it lists these paths explicitly (not the whole .github/workflows
+// directory) so this package's own maintainer workflows (ci.yml, release.yml,
+// pages.yml) don't get bundled into what ships to consumers.
 const WORKFLOWS = [
   'sprint-child-creator',
   'auto-close-sprint',
@@ -37,6 +42,10 @@ function manifestPath(targetAbs) {
   return path.join(targetAbs, '.github', MANIFEST_FILE);
 }
 
+function skillPath(targetAbs) {
+  return path.join(targetAbs, SKILL_REL_PATH);
+}
+
 function readManifest(targetAbs) {
   try {
     return JSON.parse(fs.readFileSync(manifestPath(targetAbs), 'utf8'));
@@ -112,6 +121,7 @@ function runInstall(options) {
     targetDir = '.',
     withTemplates = false,
     withLabels = false,
+    withSkill = false,
     overwrite = false,
     dryRun = false,
   } = options;
@@ -119,6 +129,7 @@ function runInstall(options) {
   const pkgRoot = getPackageRoot();
   const workflowsSrc = path.join(pkgRoot, '.github', 'workflows');
   const templatesSrc = path.join(pkgRoot, '.github', 'ISSUE_TEMPLATE');
+  const skillSrc = path.join(pkgRoot, SKILL_REL_PATH);
   const targetAbs = path.resolve(process.cwd(), targetDir);
 
   console.log('=== GitHub Delivery Operating System ===');
@@ -148,8 +159,10 @@ function runInstall(options) {
 
   let workflowsCopied = 0;
   let templatesCopied = 0;
+  let skillCopied = 0;
   let workflowsSkipped = 0;
   let templatesSkipped = 0;
+  let skillSkipped = 0;
 
   // Copy workflows
   for (const wf of WORKFLOWS) {
@@ -197,6 +210,25 @@ function runInstall(options) {
     }
   }
 
+  // Copy the delivery-ops Claude Code skill (opt-in — most consumer repos
+  // aren't using Claude Code, so this is never written unless asked for)
+  if (withSkill && fs.existsSync(skillSrc)) {
+    const skillDest = skillPath(targetAbs);
+
+    if (fs.existsSync(skillDest) && !overwrite) {
+      console.log(`  Skipped (exists): ${SKILL_REL_PATH}`);
+      skillSkipped++;
+    } else if (dryRun) {
+      console.log(`  [dry-run] Would create: ${SKILL_REL_PATH}`);
+      skillCopied++;
+    } else {
+      fs.mkdirSync(path.dirname(skillDest), { recursive: true });
+      fs.copyFileSync(skillSrc, skillDest);
+      console.log(`  Created: ${SKILL_REL_PATH}`);
+      skillCopied++;
+    }
+  }
+
   // Create labels via gh
   let labelsCreated = 0;
   let labelsSkipReason = '';
@@ -264,7 +296,7 @@ function runInstall(options) {
   // skip-mode install would leave older file content on disk, so don't
   // overwrite a previously recorded (possibly accurate, possibly newer)
   // version with a number that isn't actually true on disk yet.
-  const cleanInstall = overwrite || (workflowsSkipped === 0 && templatesSkipped === 0);
+  const cleanInstall = overwrite || (workflowsSkipped === 0 && templatesSkipped === 0 && skillSkipped === 0);
   if (!dryRun && cleanInstall) {
     const pkgVersion = require(path.join(pkgRoot, 'package.json')).version;
     writeManifest(targetAbs, pkgVersion);
@@ -278,13 +310,15 @@ function runInstall(options) {
     console.log('  all files (and the recorded version) to the latest release.');
     console.log('');
   }
-  if (workflowsCopied > 0 || templatesCopied > 0 || labelsCreated > 0) {
+  if (workflowsCopied > 0 || templatesCopied > 0 || skillCopied > 0 || labelsCreated > 0) {
     if (dryRun) {
       if (workflowsCopied > 0) console.log(`Would install ${workflowsCopied} workflow(s).`);
       if (templatesCopied > 0) console.log(`Would copy ${templatesCopied} issue template(s).`);
+      if (skillCopied > 0) console.log('Would add the Claude Code delivery-ops skill.');
     } else {
       if (workflowsCopied > 0) console.log(`Installed ${workflowsCopied} workflow(s).`);
       if (templatesCopied > 0) console.log(`Copied ${templatesCopied} issue template(s).`);
+      if (skillCopied > 0) console.log('Added the Claude Code delivery-ops skill.');
       if (labelsCreated > 0) console.log(`Created ${labelsCreated} label(s).`);
     }
     console.log('');
@@ -296,8 +330,14 @@ function runInstall(options) {
     console.log('     - QA_APPROVER: GitHub username of QA approver');
     console.log('     - QA_ASSIGNEES: Comma-separated usernames for QA assignment');
     console.log('  3. Add secrets (optional, for Telegram): TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID');
+    let nextStep = 4;
     if (!withTemplates) {
-      console.log('  4. Copy templates: re-run with --with-templates');
+      console.log(`  ${nextStep}. Copy templates: re-run with --with-templates`);
+      nextStep++;
+    }
+    if (!withSkill) {
+      console.log(`  ${nextStep}. Add the Claude Code delivery-ops skill (optional, for Claude Code users): re-run with --with-skill`);
+      nextStep++;
     }
     console.log('');
     console.log('See https://phaneroo.github.io/github-delivery-operating-system/ for full docs.');
@@ -338,6 +378,7 @@ async function runStatus(options) {
   const installedTemplates = TEMPLATES.filter((t) =>
     fs.existsSync(path.join(templatesDest, t))
   );
+  const skillInstalled = fs.existsSync(skillPath(targetAbs));
 
   if (installedWorkflows.length > 0 || installedTemplates.length > 0) {
     const manifest = readManifest(targetAbs);
@@ -383,18 +424,29 @@ async function runStatus(options) {
     console.log('');
   }
 
+  if (installedWorkflows.length > 0 || installedTemplates.length > 0) {
+    console.log('Claude Code skill:');
+    console.log(
+      skillInstalled
+        ? '  ✓ delivery-ops'
+        : '  ○ delivery-ops (not installed — re-run install with --with-skill)'
+    );
+    console.log('');
+  }
+
   if (installedWorkflows.length === 0 && installedTemplates.length === 0) {
     console.log('Delivery OS is not installed in this repository.');
     console.log('Run: npx github-delivery-os install --with-templates .');
   } else {
-    const total = installedWorkflows.length + installedTemplates.length;
-    console.log(`Summary: ${installedWorkflows.length}/${WORKFLOWS.length} workflows, ${installedTemplates.length}/${TEMPLATES.length} templates`);
+    console.log(
+      `Summary: ${installedWorkflows.length}/${WORKFLOWS.length} workflows, ${installedTemplates.length}/${TEMPLATES.length} templates, skill: ${skillInstalled ? 'yes' : 'no'}`
+    );
   }
   console.log('');
 }
 
 function runUninstall(options) {
-  const { targetDir = '.', withTemplates = false, dryRun = false } = options;
+  const { targetDir = '.', withTemplates = false, withSkill = false, dryRun = false } = options;
   const targetAbs = path.resolve(process.cwd(), targetDir);
   const workflowsDest = path.join(targetAbs, '.github', 'workflows');
   const templatesDest = path.join(targetAbs, '.github', 'ISSUE_TEMPLATE');
@@ -435,6 +487,20 @@ function runUninstall(options) {
     }
   }
 
+  let skillRemoved = 0;
+  if (withSkill) {
+    const skillDest = skillPath(targetAbs);
+    if (fs.existsSync(skillDest)) {
+      if (dryRun) {
+        console.log(`  [dry-run] Would remove: ${SKILL_REL_PATH}`);
+      } else {
+        fs.unlinkSync(skillDest);
+        console.log(`  Removed: ${SKILL_REL_PATH}`);
+      }
+      skillRemoved++;
+    }
+  }
+
   // Remove the version manifest too — it has no meaning once Delivery OS is
   // gone, and leaving it behind would make a later install/status think a
   // stale version is still installed.
@@ -449,14 +515,19 @@ function runUninstall(options) {
   }
 
   console.log('');
-  if (workflowsRemoved > 0 || templatesRemoved > 0) {
+  if (workflowsRemoved > 0 || templatesRemoved > 0 || skillRemoved > 0) {
+    const templateNote = withTemplates ? `, ${templatesRemoved} template(s)` : '';
+    const skillNote = withSkill ? `, ${skillRemoved} skill file(s)` : '';
     if (dryRun) {
-      console.log(`Would remove ${workflowsRemoved} workflow(s)${withTemplates ? `, ${templatesRemoved} template(s)` : ''}.`);
+      console.log(`Would remove ${workflowsRemoved} workflow(s)${templateNote}${skillNote}.`);
     } else {
-      console.log(`Removed ${workflowsRemoved} workflow(s)${withTemplates ? `, ${templatesRemoved} template(s)` : ''}.`);
+      console.log(`Removed ${workflowsRemoved} workflow(s)${templateNote}${skillNote}.`);
       if (!withTemplates) {
         console.log('Templates were kept. Re-run with --with-templates to remove them.');
       }
+      if (!withSkill) {
+        console.log('Claude Code skill (if installed) was kept. Re-run with --with-skill to remove it.');
+      }
     }
   } else {
     console.log('No Delivery OS files found to remove.');
@@ -470,5 +541,14 @@ module.exports = {
   runStatus,
   runUninstall,
   // Exposed for tests only — not part of the CLI's public API.
-  __test__: { manifestPath, readManifest, writeManifest, fetchLatestVersion, WORKFLOWS, TEMPLATES },
+  __test__: {
+    manifestPath,
+    readManifest,
+    writeManifest,
+    fetchLatestVersion,
+    skillPath,
+    SKILL_REL_PATH,
+    WORKFLOWS,
+    TEMPLATES,
+  },
 };

package/.github/workflows/ci.yml

@@ -1,23 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run tests
-        run: npm test

package/.github/workflows/pages.yml

@@ -1,46 +0,0 @@
-# Deploy docs/ to GitHub Pages
-# Requires: Settings → Pages → Source: GitHub Actions
-
-name: Deploy to GitHub Pages
-
-on:
-  push:
-    branches: [main]
-  workflow_dispatch:
-
-permissions:
-  contents: read
-  pages: write
-  id-token: write
-
-concurrency:
-  group: pages
-  cancel-in-progress: false
-
-env:
-  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    steps:
-      - name: Opt into Node.js 24
-        run: echo "FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true" >> $GITHUB_ENV
-
-      - name: Checkout
-        uses: actions/checkout@v6
-
-      - name: Setup Pages
-        uses: actions/configure-pages@v5
-
-      - name: Upload artifact
-        uses: actions/upload-pages-artifact@v4
-        with:
-          path: ./docs
-
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4

package/.github/workflows/release.yml

@@ -1,38 +0,0 @@
-# Create GitHub release when a version tag is pushed
-# Usage: git tag v1.0.2 && git push origin v1.0.2
-
-name: Release
-
-on:
-  push:
-    tags:
-      - 'v*'
-
-permissions:
-  contents: write
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-        with:
-          fetch-depth: 0
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run tests
-        run: npm test
-
-      - name: Create Release
-        uses: softprops/action-gh-release@v2
-        with:
-          generate_release_notes: true
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}