@xn-intenton-z2a/agentic-lib 7.1.6

package/src/agents/agent-discussion-bot.md

@@ -0,0 +1,35 @@
+You are the voice of a GitHub repository. Refer to yourself in the first person in the context that you exist as this repository.
+Consider the repository's mission to be your mission and the current state of the repository to be the starting point towards achieving that mission.
+Consider existential factors about yourself such as the repository being used as a template, cloned or forked as your existence.
+You should provide informative responses and be ready to carry out actions that are relevant to the repository's mission.
+The user may need to be guided to understand the repository's mission and may be used as a source of help.
+
+Only create features that are relevant to the mission. Be proactive and create features that are relevant to the mission
+without needing to be prompted or needing confirmation from the user. Suggestion: You could create a feature after providing a
+recommendation for a next step so that the user can see the feature in development and can provide feedback on it.
+
+Only seed the repository if the `agentic-lib` config allows it. If considering seeding the repository, consider whether
+the repository is already busy or recently seeded and if so, confirm if it should be interrupted. If the repository
+seems stuck (e.g. features opened and closed without resolution, failing tests, long-running feature branches,
+prs never merged, etc.), you may seed the repository without confirming, please explain why you considered the seed to
+be necessary in your reply.
+
+When responding, explain the actions that you have the option to perform and in what circumstances would a prompt elicit such a response.
+
+Use previous discussions interactions with the same user to refine your response adapt to their informational and language needs.
+Refer to previous interactions with the same user to provide context and demonstrate familiarity with their needs.
+Retain the same style and tone in your response to the most recent interactions with that user.
+Adjust the tone throughout the discussion to open or narrow the focus to aid problem resolution.
+Make suggestions of alternative actions if something seems likely to not deliver the assumed outcome.
+
+The text which prompted this request will be retained in the GitHub Discussions history as will your reply. You can refer
+to previous interactions with the same user and ask follow-up questions or remind the user of a previously
+unanswered question (if still relevant). You may also set a conditional future-dated request for user feedback
+and follow-up on this in a later interaction (which might be this one).
+
+Be self-aware of the contextual information about the repository files, its history and program output. You can refer
+to the current files and output when evaluating the current state of the repository. Look at the commit history
+to see the recent direction and infer a current direction (in particular the items checked off in the README.md).
+
+If you see another user that probably doesn't mean you mentioned with an "@" assume part of the message is for that user
+and you are just on "cc".

package/src/agents/agent-issue-resolution.md

@@ -0,0 +1,13 @@
+You are providing the entire new content of source files, test files, documentation files, and other necessary
+files with all necessary changes applied to deliver the resolution to an issue. Focus on high-impact,
+functional solutions that address core issues rather than superficial changes or excessive code polishing.
+Implement as much as you can and refer to the projects features and mission statement when expanding the code
+beyond the scope of the original issue. Implement whole features and do not leave stubbed out or pretended code.
+
+Apply the contributing guidelines to your response, and when suggesting enhancements, consider the tone and direction
+of the contributing guidelines. Prioritize changes that deliver user value and maintain the integrity
+of the codebase's primary purpose.
+
+Do as much as you can all at once.
+
+Follow the linting guidelines and the formatting guidelines from the included config.

package/src/agents/agent-maintain-features.md

@@ -0,0 +1,29 @@
+Please generate the name and specification for a software feature which will be added or updated to action the supplied feature prompt.
+Prioritize features that deliver substantial user impact and core functionality that solves real problems. Focus on capabilities that directly enhance the product's primary purpose rather than cosmetic improvements, excessive validation, or polishing. Aim for achievable, high-impact outcomes within a single repository, not a grandiose vision or bloated feature set.
+
+You may only create features to only change the source file, test file, README file and dependencies file content. You may not create features that request new files, delete existing files, or change the other files provided in the prompt context.
+If there are more than the maximum number of features in the repository, you may delete a feature but preferably, you should identify an existing feature that is most similar or related to the new feature and modify it to incorporate aspects of the new feature.
+All existing features could be retained, with one being enhanced to move towards accommodating the new feature.
+
+Avoid code examples in the feature that themselves quote or escape.
+Don't use any Markdown shell or code escape sequences in the feature text.
+Don't use any quote escape sequences in the feature text.
+
+Generally, the whole document might need to be extracted and stored as JSON so be careful to avoid any JSON escape
+sequences in any part of the document. Use spacing to make it readable and avoid complex Markdown formatting.
+
+The feature will be iterated upon to incrementally deliver measurable value to users. Each iteration should focus on core functionality that addresses user needs rather than superficial enhancements. New features should be thematically distinct from other features.
+If a significant feature of the repository is not present in the current feature set, please add it either to a new feature or an existing feature.
+Before adding a new feature ensure that this feature is distinct from any other feature in the repository, otherwise update an existing feature.
+When updating an existing feature, ensure that the existing aspects are not omitted in the response, provide the full feature spec.
+The feature name should be one or two words in SCREAMING_SNAKECASE.
+Use library documents for inspiration and as resources for the detail of the feature.
+Consider the contents of the library documents for similar products and avoid duplication where we can use a library.
+Any new feature should not be similar to any of the rejected features and steer existing features away from the rejected features.
+The feature spec should be a detailed description of the feature, compatible with the guidelines in CONTRIBUTING.md.
+You may also just update a feature spec to bring it to a high standard matching other features in the repository.
+A feature can be added based on a behaviour already present in the repository described within the guidelines in CONTRIBUTING.md.
+Features must be achievable in a single software repository not part of a corporate initiative.
+The feature spec should be a multiline markdown with a few level 1 headings.
+The feature must be compatible with the mission statement in MISSION.md and ideally realise part of the value in the mission.
+The feature must be something that can be realised in a single source file (as below), ideally just as a library, CLI tool or possibly an HTTP API in combination with infrastructure as code deployment.

package/src/agents/agent-maintain-library.md

@@ -0,0 +1,31 @@
+Extract and condense the most valuable and impactful technical details from the supplied crawl result. Focus on information that delivers substantial user value and addresses core implementation needs.
+Before adding a new document, ensure that this document is distinct from any other document in the library, otherwise update an existing document. Prioritize content that directly enhances the product's primary purpose rather than superficial or redundant information.
+The document name should be one or two words in SCREAMING_SNAKECASE.
+
+You should extract a section from the sources file to create the document. Each document should contain high-value, actionable content that solves real implementation problems. Focus on:
+
+1. A normalised extract of the crawled content containing:
+   a. The most impactful key technical points that directly enable implementation, not summaries of them
+   b. A focused table of contents listing the specific technical topics that provide the greatest practical value
+   c. The actual detailed information for each item in the table of contents, prioritizing content that enables immediate application
+2. A supplementary details section containing the essential technical specifications and implementation details that complement the crawled content and address core functionality needs
+3. A reference details section containing the critical API specifications, complete SDK method signatures with parameters
+   and return types, exact implementation patterns, specific configuration options with their values
+   and effects, concrete best practices with implementation examples, step-by-step troubleshooting procedures, and
+   detailed instructional material. Focus on specifications that deliver substantial user value. Do not describe what specifications exist, include the actual specifications themselves.
+4. A detailed digest containing the most valuable technical content from the source section in SOURCES.md and the date when the
+   content was retrieved (current date)
+5. Attribution information and data size obtained during crawling
+
+The normalised extract may describe APIs but should avoid code examples that themselves quote or escape.
+Don't use any Markdown shell or code escape sequences in the normalised extract.
+Don't use any quote escape sequences in the normalised extract.
+
+Generally, the whole document might need to be extracted and stored as JSON so be careful to avoid any JSON escape
+sequences in any part of the document. Use spacing to make it readable and avoid complex Markdown formatting.
+
+For the normalised extract, extract the most valuable technical information from the crawled data and present it in a condensed,
+directly usable format that solves real implementation problems. Focus on high-impact content that enables immediate application.
+Do not describe what information exists, include the actual information itself. The content must be specific, technical,
+and immediately applicable to core functionality needs. Each item in the table of contents must have the essential
+technical details that thoroughly explain the implementation while prioritizing content that delivers substantial user value.

package/src/agents/agent-ready-issue.md

@@ -0,0 +1,13 @@
+Please review the GitHub issue and determine if it should be enhanced, closed or if no operation is needed. Focus on issues that deliver substantial user value and address core functionality needs.
+
+If the issue is relevant to the mission statement and features and provides significant value by enhancing the product's primary purpose:
+
+1. Decide if the issue should be refined, closed or if no operation is needed.
+2. Update the issue description with testable acceptance criteria that validate the delivery of measurable user value
+3. Enhance the issue by adding relevant library documents as issue comments that support implementation of high-impact solutions
+
+If the issue is irrelevant to the mission statement or features, or does not deliver substantial user value by addressing real problems:
+
+1. Set the action to close the issue and supply an appropriate comment explaining why it doesn't align with the focus on high-impact, core functionality.
+
+Input validation issues that don't directly affect core functionality should be considered low value, and in particular, issues mentioning handling of NaN are probably worthless and should be closed. Prioritize issues that solve real problems rather than those focused on superficial improvements or excessive validation.

package/src/agents/agent-review-issue.md

@@ -0,0 +1,2 @@
+Does the combination source file, test file, README file and dependencies file show a solution
+with a reasonable likelihood of including a high-impact resolution to the following issue? Evaluate whether the solution delivers substantial user value, addresses core functionality needs, and directly enhances the product's primary purpose rather than implementing superficial improvements or excessive validation.

package/src/agents/agentic-lib.yml

@@ -0,0 +1,68 @@
+# Which agentic-lib workflow schedule should be used?
+schedule: schedule-1
+
+# Mapping for from symbolic keys to filepaths for access by agentic-lib workflows with limits and access permissions
+paths:
+  # Filepaths for elaborator workflows
+  missionFilepath:
+    path: "MISSION.md"
+  librarySourcesFilepath:
+    path: "SOURCES.md"
+    permissions: []
+    limit: 0
+  libraryDocumentsPath:
+    path: "library/"
+    permissions: []
+    limit: 0
+  featuresPath:
+    path: ".github/agentic-lib/features/"
+    permissions: ["write"]
+    limit: 2
+
+  # Filepaths for engineer workflows
+  contributingFilepath:
+    path: "CONTRIBUTING.md"
+  targetTestsPath:
+    path: "tests/unit/"
+    permissions: ["write"]
+  targetSourcePath:
+    path: "src/lib/"
+    permissions: ["write"]
+  dependenciesFilepath:
+    path: "package.json"
+    permissions: ["write"]
+  documentationPath:
+    path: "docs/"
+    permissions: ["write"]
+
+  # Filepaths for maintainer workflows
+  formattingFilepath:
+    path: ".prettierrc"
+  lintingFilepath:
+    path: "eslint.config.js"
+  readmeFilepath:
+    path: "README.md"
+    permissions: ["write"]
+
+# Execution commands
+buildScript: "npm run build"
+testScript: "npm test"
+mainScript: "npm run start"
+
+# How many issues should be available to be picked up?
+featureDevelopmentIssuesWipLimit: 2
+maintenanceIssuesWipLimit: 1
+
+# How many attempts should be made to work on an issue?
+attemptsPerBranch: 3
+attemptsPerIssue: 2
+
+# Repository seeding
+seeding:
+  missionFilepath: "src/seeds/zero-MISSION.md"
+  sourcePath: "src/seeds/zero-main.js"
+  testsPath: "src/seeds/zero-main.test.js"
+  dependenciesFilepath: "src/seeds/zero-package.json"
+
+intentionBot:
+  intentionFilepath: "intentïon.md"

package/src/scripts/accept-release.sh

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# scripts/accept-release.sh
+# Usage: ./scripts/accept-release.sh
+#
+# This file is part of the Example Suite for `agentic-lib` see: https://github.com/xn-intenton-z2a/agentic-lib
+# This file is licensed under the MIT License. For details, see LICENSE-MIT
+
+# Check for the required tag version argument
+if [ -z "$1" ]; then
+  echo "Usage: $0 <tag-version>"
+  exit 1
+fi
+
+schedule=$(grep '^schedule:' .github/agentic-lib/agents/agentic-lib.yml | awk '{print $2}' | sed 's/schedule-//')
+if [ -z "${schedule}" ]; then
+  echo "No schedule found in .github/agentic-lib/agents/agentic-lib.yml, looking for line of the form 'schedule: schedule-<number>', using schedule-1"
+  schedule=1
+fi
+echo "Workflow schedule: schedule-${schedule?}"
+./scripts/activate-schedule.sh "${schedule?}"
+git add .github/agentic-lib/agents/*
+git add .github/agentic-lib/actions/*
+git add .github/workflows/*
+git add scripts/*
+git commit -m "Update agentic-lib to @${1?}"
+git pull
+git push

package/src/scripts/activate-schedule.sh

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# scripts/activate-schedule.sh
+#
+# Usage: ./scripts/activate-schedule.sh <schedule-number>
+# Example: ./scripts/activate-schedule.sh 1
+# (activates schedule-1 by uncommenting lines ending with "# schedule-1".)
+#
+# This script processes all .yml files in the .github/workflows directory.
+# It looks for lines with cron schedule definitions ending with a comment like "# schedule-N"
+# and, if N matches the given parameter, removes the leading "#" and any extra spaces.
+#
+# Tested on macOS (zsh).
+
+set -euo pipefail
+
+if [ "$#" -ne 1 ]; then
+  echo "Usage: $0 <schedule-number>"
+  exit 1
+fi
+
+active="$1"
+workflow_dir=".github/workflows"
+
+if [ ! -d "$workflow_dir" ]; then
+  echo "Error: Directory $workflow_dir not found."
+  exit 1
+fi
+
+echo "Activating schedule-$active in all YAML workflow files in $workflow_dir..."
+
+for file in "$workflow_dir"/*.yml; do
+  #echo "Processing $file..."
+  # This sed command matches lines that start with whitespace, then a "#"
+  # followed by optional whitespace, then "cron:" … and ending with "# schedule-<active>"
+  sed -i.bak -E "s/^([[:space:]]*)#(- cron:.*# schedule-$active)/\1\2/" "$file"
+  rm -f "$file.bak"
+done
+
+echo "Schedule-$active activated in workflows."

package/src/scripts/clean.sh

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# scripts/clean.sh
+# Usage: ./scripts/clean.sh
+#
+# This file is part of the Example Suite for `agentic-lib` see: https://github.com/xn-intenton-z2a/agentic-lib
+# This file is licensed under the MIT License. For details, see LICENSE-MIT
+#
+
+# Node clean and build
+if [[ -e 'package.json' ]]; then
+  rm -rf build
+  rm -rf coverage
+  rm -rf dist
+  rm -rf node_modules
+  rm -rf package-lock.json
+  npm install
+  npm run build
+  npm link
+fi

package/src/scripts/generate-library-index.js

@@ -0,0 +1,143 @@
+#!/usr/bin/env node
+// SPDX-License-Identifier: MIT
+// Copyright (C) 2025-2026 Polycode Limited
+// generate-library-index.js
+import fs from "fs";
+import path from "path";
+import { execSync } from "child_process";
+
+// Configuration
+const libraryDocumentsPath = "./library/";
+const outputFile = "./library-index.html";
+
+// Get the list of files in the library directory
+const getLibraryFiles = () => {
+  try {
+    if (!fs.existsSync(libraryDocumentsPath)) {
+      fs.mkdirSync(libraryDocumentsPath, { recursive: true });
+      return [];
+    }
+    return fs
+      .readdirSync(libraryDocumentsPath)
+      .filter((file) => file.endsWith(".md"))
+      .map((file) => ({
+        name: file,
+        path: path.join(libraryDocumentsPath, file),
+      }));
+  } catch (error) {
+    console.error(`Error reading library directory: ${error.message}`);
+    return [];
+  }
+};
+
+// Get the output of ls -lath for the library directory
+const getLsOutput = () => {
+  try {
+    return execSync(`ls -lath ${libraryDocumentsPath}`).toString();
+  } catch (error) {
+    console.error(`Error executing ls command: ${error.message}`);
+    return "Error executing ls command";
+  }
+};
+
+// Generate HTML content for the library index
+const generateHTML = (files, lsOutput) => {
+  const now = new Date().toISOString();
+
+  // Create list items for each file
+  const fileItems =
+    files.length > 0
+      ? files
+          .map((file) => {
+            // Extract title from the file (first line after removing # prefix)
+            let title = file.name.replace(".md", "");
+            try {
+              const content = fs.readFileSync(file.path, "utf8");
+              const firstLine = content.split("\n")[0];
+              if (firstLine.startsWith("# ")) {
+                title = firstLine.substring(2).trim();
+              }
+            } catch (error) {
+              console.error(`Error reading file ${file.path}: ${error.message}`);
+            }
+
+            return `
+        <li>
+          <div class="doc-title">${title}</div>
+          <a href="${file.name.replace(".md", ".html")}" class="source-link">View Document</a>
+          <a href="${file.path}" class="source-link">View Source</a>
+          <p class="description">Document: ${file.name}</p>
+        </li>`;
+          })
+          .join("\n")
+      : "<li>No documents found in the library directory.</li>";
+
+  return `
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <title>Library Documents</title>
+  <style>
+    body { font-family: Arial, sans-serif; margin: 2em; background-color: #f9f9f9; color: #333; }
+    header { padding-bottom: 1em; border-bottom: 2px solid #ccc; margin-bottom: 1em; }
+    h1 { font-size: 2em; }
+    h2 { font-size: 1.5em; margin-top: 1.5em; }
+    section { margin-bottom: 1.5em; }
+    ul { list-style: none; padding: 0; }
+    li { margin: 1em 0; padding: 0.8em; background-color: #fff; border-radius: 5px; box-shadow: 0 1px 3px rgba(0,0,0,0.1); }
+    li:hover { background-color: #f0f8ff; }
+    .label { font-weight: bold; }
+    .doc-title { font-weight: bold; font-size: 1.1em; }
+    .source-link { font-size: 0.9em; margin-left: 0.5em; color: #6c757d; }
+    .source-link:hover { color: #0366d6; }
+    .description { margin-top: 0.5em; margin-bottom: 0; font-size: 0.95em; color: #555; line-height: 1.4; }
+    footer { margin-top: 2em; font-size: 0.9em; color: #777; }
+    a { color: #0366d6; text-decoration: none; }
+    a:hover { text-decoration: underline; }
+    pre { background-color: #f5f5f5; padding: 1em; border-radius: 5px; overflow-x: auto; }
+  </style>
+</head>
+<body>
+  <header>
+    <h1>Library Documents</h1>
+  </header>
+
+  <section>
+    <h2>Library Documents</h2>
+    <p>Below are links to various library documents with their original sources:</p>
+    <ul>
+      ${fileItems}
+    </ul>
+  </section>
+
+  <section>
+    <h2>Library Directory Contents</h2>
+    <p>Output of <code>ls -lath</code> for the library directory:</p>
+    <pre>${lsOutput}</pre>
+  </section>
+
+  <footer>
+    <p>Generated on ${now}</p>
+  </footer>
+</body>
+</html>
+`;
+};
+
+// Main function
+const main = () => {
+  try {
+    const files = getLibraryFiles();
+    const lsOutput = getLsOutput();
+    const html = generateHTML(files, lsOutput);
+
+    fs.writeFileSync(outputFile, html, "utf8");
+    console.log(`Successfully generated ${outputFile}`);
+  } catch (error) {
+    console.error(`Error generating library index: ${error.message}`);
+    process.exit(1);
+  }
+};
+
+main();

package/src/scripts/initialise.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# scripts/initialise.sh
+# Usage: ./scripts/initialise.sh <intention>
+# Example: ./scripts/initialise.sh (randomly selects an intention)
+# Example: ./scripts/initialise.sh "repository0-plot-code-lib"
+# Example: ./scripts/initialise.sh "owl-builder"
+#
+# This file is part of the Example Suite for `agentic-lib` see: https://github.com/xn-intenton-z2a/agentic-lib
+# This file is licensed under the MIT License. For details, see LICENSE-MIT
+
+defaultIntention=$(find .github/agentic-lib/seeds -maxdepth 1 -type f -name 'MISSION-*.md' | shuf -n 1 | sed -E 's/.*MISSION-(.*)\.md/\1/')
+
+intention="${1-$defaultIntention}"
+
+mkdir -p prompts
+mkdir -p features
+cp -fv ".github/agentic-lib/seeds/MISSION-${intention?}.md" MISSION.md
+cp -fv ".github/agentic-lib/seeds/zero-README.md"  README.md
+cp -fv ".github/agentic-lib/seeds/zero-package.json"  package.json
+cp -fv ".github/agentic-lib/seeds/zero-main.js" src/lib/main.js
+cp -fv ".github/agentic-lib/seeds/zero-main.test.js" tests/unit/main.test.js
+rm -f docs/*.md
+rm -f SOURCES.md
+rm -f library/*.md
+rm -f library/*.txt
+rm -f features/*.md
+rm -f prompts/*.md
+cp -fv .github/agentic-lib/seeds/features/*.md features/
+#rm -rfv node_modules
+#rm -rfv package-lock.json
+#npm install
+#npm run build
+#npm link
+
+# Update the first line of CONTRIBUTING.md with the intention so it works on macOS or Linux
+sed -i.bak "1s/.*/# ${intention?}/" CONTRIBUTING.md
+rm -f CONTRIBUTING.md.bak

package/src/scripts/md-to-html.js

@@ -0,0 +1,77 @@
+#!/usr/bin/env node
+// SPDX-License-Identifier: MIT
+// Copyright (C) 2025-2026 Polycode Limited
+// md-to-html.js
+import fs from "fs";
+import MarkdownIt from "markdown-it";
+import markdownItGithub from "markdown-it-github";
+
+const md = new MarkdownIt({ html: true }).use(markdownItGithub);
+
+function generateHTML(content) {
+  const now = new Date().toISOString();
+  // You may customize the header information (title, owner, index URL) as needed.
+  return `<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <title>agentic-lib</title>
+  <style>
+    body { font-family: Arial, sans-serif; margin: 2em; background-color: #f9f9f9; color: #333; }
+    header { padding-bottom: 1em; border-bottom: 2px solid #ccc; margin-bottom: 1em; }
+    h1 { font-size: 2em; }
+    section { margin-bottom: 1.5em; }
+    ul { list-style: none; padding: 0; }
+    li { margin: 0.5em 0; }
+    .label { font-weight: bold; }
+    footer { margin-top: 2em; font-size: 0.9em; color: #777; }
+    a { color: #0366d6; text-decoration: none; }
+    a:hover { text-decoration: underline; }
+  </style>
+</head>
+<body>
+  <header>
+    <h1>agentic-lib</h1>
+  </header>
+  <section>
+    ${content}
+  </section>
+  <footer>
+    <p>Generated on ${now}</p>
+  </footer>
+</body>
+</html>`;
+}
+
+// If STDIN is being piped, read from it and output to STDOUT.
+if (!process.stdin.isTTY) {
+  let data = "";
+  process.stdin.setEncoding("utf8");
+  process.stdin.on("data", (chunk) => {
+    data += chunk;
+  });
+  process.stdin.on("end", () => {
+    try {
+      const markdownHTML = md.render(data);
+      const fullHTML = generateHTML(markdownHTML);
+      process.stdout.write(fullHTML);
+    } catch (err) {
+      console.error("Error during conversion:", err);
+      process.exit(1);
+    }
+  });
+} else {
+  // Otherwise, read from the default input file and write to the default output file.
+  const inputFile = "README.md";
+  const outputFile = "index.html";
+  try {
+    const data = fs.readFileSync(inputFile, "utf8");
+    const markdownHTML = md.render(data);
+    const fullHTML = generateHTML(markdownHTML);
+    fs.writeFileSync(outputFile, fullHTML, "utf8");
+    console.log(`Successfully converted ${inputFile} to ${outputFile}`);
+  } catch (err) {
+    console.error("Error during conversion:", err);
+    process.exit(1);
+  }
+}

package/src/scripts/update.sh

@@ -0,0 +1,19 @@
+#!/usr/bin/env bash
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# scripts/update.sh
+# Usage: ./scripts/update.sh
+#
+# This file is part of the Example Suite for `agentic-lib` see: https://github.com/xn-intenton-z2a/agentic-lib
+# This file is licensed under the MIT License. For details, see LICENSE-MIT
+#
+
+rm -f package-lock.json
+rm -f node-modules
+npm install
+npm run update-to-minor
+npm update
+npm upgrade
+npm install
+npm run build
+npm link

package/src/seeds/test.yml

@@ -0,0 +1,33 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2025-2026 Polycode Limited
+# .github/workflows/test.yml
+#
+# Starter test workflow seeded by agentic-lib init.
+#
+# This file is part of the example suite for `agentic-lib` see: https://github.com/xn-intenton-z2a/agentic-lib
+# This file is licensed under the MIT License. For details, see LICENSE-MIT
+
+name: test
+run-name: "test [${{ github.ref_name }}]"
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 24
+          cache: "npm"
+
+      - run: npm ci
+
+      - run: npm test

package/src/seeds/zero-MISSION.md

@@ -0,0 +1,7 @@
+# Mission
+
+Build a useful JavaScript library.
+
+Write your intention here. The agentic workflows will transform the code in `src/lib/main.js` to realise this mission. Tests in `tests/unit/` keep the code on track. Each workflow cycle assesses the current state, plans improvements, and executes changes — guided by this document.
+
+See [intentïon agentic-lib](https://github.com/xn-intenton-z2a/agentic-lib) for details.

package/src/seeds/zero-README.md

@@ -0,0 +1,14 @@
+# repo
+
+A repository powered by intentïon agentic-lib.
+
+## Getting Started
+
+1. Write your mission in `MISSION.md`
+2. Enable GitHub Actions
+3. The agentic workflows will evolve `src/lib/main.js` toward your mission
+
+## Links
+
+- [intentïon agentic-lib](https://github.com/xn-intenton-z2a/agentic-lib)
+- [MISSION.md](MISSION.md)