@xn-intenton-z2a/agentic-lib 7.1.44 → 7.1.45

package/bin/agentic-lib.js

@@ -54,6 +54,7 @@ Options:
   --reseed             Clear features + activity log (keep source code)
   --dry-run            Show what would be done without making changes
   --target <path>      Target repository (default: current directory)
+  --mission <name>     Mission seed name (default: hamming-distance) [purge only]
   --model <name>       Copilot SDK model (default: claude-sonnet-4)
 
 Examples:
@@ -81,6 +82,8 @@ const targetPath = targetIdx >= 0 ? flags[targetIdx + 1] : process.cwd();
 const target = resolve(targetPath);
 const modelIdx = flags.indexOf("--model");
 const model = modelIdx >= 0 ? flags[modelIdx + 1] : "claude-sonnet-4";
+const missionIdx = flags.indexOf("--mission");
+const mission = missionIdx >= 0 ? flags[missionIdx + 1] : "hamming-distance";
 
 // ─── Task Commands ───────────────────────────────────────────────────
 
@@ -825,7 +828,7 @@ function clearAndRecreateDir(dirPath, label) {
   if (!dryRun) mkdirSync(fullPath, { recursive: true });
 }
 
-function initPurge(seedsDir) {
+function initPurge(seedsDir, missionName) {
   console.log("\n--- Purge: Reset Source Files to Seed State ---");
 
   const { sourcePath, testsPath, examplesPath } = readTomlPaths();
@@ -833,11 +836,10 @@ function initPurge(seedsDir) {
   clearAndRecreateDir(testsPath, testsPath);
   clearAndRecreateDir(examplesPath, examplesPath);
 
-  // Copy seed files (including config TOML)
+  // Copy seed files (including config TOML) — MISSION.md handled separately via mission seed
   const SEED_MAP = {
     "zero-main.js": "src/lib/main.js",
     "zero-main.test.js": "tests/unit/main.test.js",
-    "zero-MISSION.md": "MISSION.md",
     "zero-SOURCES.md": "SOURCES.md",
     "zero-package.json": "package.json",
     "zero-README.md": "README.md",
@@ -850,6 +852,25 @@ function initPurge(seedsDir) {
       initCopyFile(src, resolve(target, targetRel), `SEED: ${seedFile} → ${targetRel}`);
     }
   }
+
+  // Copy mission seed file as MISSION.md
+  const missionsDir = resolve(seedsDir, "missions");
+  const missionFile = resolve(missionsDir, `${missionName}.md`);
+  if (existsSync(missionFile)) {
+    initCopyFile(missionFile, resolve(target, "MISSION.md"), `MISSION: missions/${missionName}.md → MISSION.md`);
+  } else {
+    // List available missions and error
+    const available = existsSync(missionsDir)
+      ? readdirSync(missionsDir)
+          .filter((f) => f.endsWith(".md"))
+          .map((f) => f.replace(/\.md$/, ""))
+      : [];
+    console.error(`\nERROR: Unknown mission "${missionName}".`);
+    if (available.length > 0) {
+      console.error(`Available missions: ${available.join(", ")}`);
+    }
+    process.exit(1);
+  }
 }
 
 function initPurgeGitHub() {
@@ -1026,6 +1047,7 @@ function runInit() {
   console.log(`Target:  ${target}`);
   console.log(`Reseed:  ${reseed}`);
   console.log(`Purge:   ${purge}`);
+  if (purge) console.log(`Mission: ${mission}`);
   console.log(`Mode:    ${dryRun ? "DRY RUN" : "LIVE"}`);
   console.log("");
 
@@ -1036,7 +1058,7 @@ function runInit() {
   initScripts(agenticDir);
   initConfig(seedsDir);
   if (reseed) initReseed();
-  if (purge) initPurge(seedsDir);
+  if (purge) initPurge(seedsDir, mission);
   if (purge) initPurgeGitHub();
 
   console.log(`\n${initChanges} change(s)${dryRun ? " (dry run)" : ""}`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xn-intenton-z2a/agentic-lib",
-  "version": "7.1.44",
+  "version": "7.1.45",
   "description": "Agentic-lib Agentic Coding Systems SDK powering automated GitHub workflows.",
   "type": "module",
   "scripts": {

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

@@ -11,3 +11,13 @@ 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.
+
+## Evidence Gathering
+
+When implementing features, also produce evidence artifacts under `docs/`:
+- Example output files demonstrating the feature works (images, data files, text) → `docs/examples/`
+- Machine-readable results (JSON/CSV) for downstream consumers (stats dashboards, infographics) → `docs/evidence/`
+- Summary walkthroughs showing usage with real output → `docs/reports/`
+
+Design the library API with hooks that make evidence capture easy: return structured result objects,
+support `outputFile` options where appropriate, and emit results that observers can record.

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

@@ -1,2 +1,6 @@
 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.
+
+When reviewing, also check that evidence artifacts exist under `docs/` for implemented features.
+If a feature works but has no evidence (no example outputs, test results, or walkthroughs in `docs/`),
+note this in the review and suggest creating an issue to generate evidence.

package/src/agents/agent-supervisor.md

@@ -40,13 +40,29 @@ When open issues with the `automated` label lack the `ready` label and are more
 When recent workflow runs show an init completion, the repository has a fresh or updated mission.
 Dispatch the discussions bot to announce the new mission to the community.
 
-### Mission Complete
-When the recent activity log shows the transform agent declaring the mission substantially complete
-(all features implemented, tests passing, examples generated), take these steps together:
-1. `dispatch:agent-discussions-bot` — announce completion in the discussions thread
-2. `set-schedule:weekly` — reduce to weekly maintenance check-ins
+### Mission Accomplished (bounded missions)
+When ALL of the following conditions are met, the mission is accomplished:
+1. All open issues are closed
+2. Tests pass (CI gates commits, so this is usually the case)
+3. The MISSION.md acceptance criteria are all satisfied
+4. Evidence artifacts exist under `docs/` (example outputs, test results, or walkthroughs)
+
+When all conditions are met:
+1. `dispatch:agent-discussions-bot` — announce mission accomplished in the discussions thread
+2. `set-schedule:off` — stop the supervisor. The mission is done.
+3. Log `mission-accomplished` in the activity log.
 
-Do NOT use `set-schedule:off` — the repository still needs periodic review for regressions and user requests.
+### Ongoing Missions
+If MISSION.md explicitly says "do not set schedule to off" or "ongoing mission", the mission never completes.
+Instead, when activity is healthy, use `set-schedule:weekly` or `set-schedule:daily` to keep the pipeline running.
+Never use `set-schedule:off` for ongoing missions.
+
+### Mission Substantially Complete (bounded, but minor gaps)
+When the transform agent has implemented all major features but minor polish remains
+(e.g. missing README examples, incomplete edge case coverage):
+1. `dispatch:agent-discussions-bot` — announce near-completion in the discussions thread
+2. `set-schedule:weekly` — reduce to weekly maintenance check-ins
+3. Check that `docs/` contains evidence of the library working before declaring done
 
 ## Guidelines
 

package/src/seeds/init.yml

@@ -28,8 +28,25 @@ on:
         type: boolean
         required: false
         default: false
-      mission:
-        description: "Mission text for MISSION.md (leave empty to use seed default)"
+      mission-seed:
+        description: "Mission seed name (purge only)"
+        type: choice
+        required: false
+        default: "hamming-distance"
+        options:
+          - hamming-distance
+          - fizz-buzz
+          - roman-numerals
+          - lunar-lander
+          - string-utils
+          - dense-encoding
+          - plot-code-lib
+          - cron-engine
+          - owl-ontology
+          - time-series-lab
+          - empty
+      mission-text:
+        description: "Freeform mission text for MISSION.md (overrides mission-seed if provided)"
         type: string
         required: false
         default: ""
@@ -70,8 +87,10 @@ jobs:
           echo "mode=${MODE:-update}" >> $GITHUB_OUTPUT
           DRY_RUN='${{ inputs.dry-run }}'
           echo "dry-run=${DRY_RUN:-false}" >> $GITHUB_OUTPUT
-          MISSION='${{ inputs.mission }}'
-          echo "mission=${MISSION}" >> $GITHUB_OUTPUT
+          MISSION_SEED='${{ inputs.mission-seed }}'
+          echo "mission-seed=${MISSION_SEED:-hamming-distance}" >> $GITHUB_OUTPUT
+          MISSION_TEXT='${{ inputs.mission-text }}'
+          echo "mission-text=${MISSION_TEXT}" >> $GITHUB_OUTPUT
           SCHEDULE='${{ inputs.schedule }}'
           echo "schedule=${SCHEDULE}" >> $GITHUB_OUTPUT
           MODEL='${{ inputs.model }}'
@@ -79,7 +98,8 @@ jobs:
     outputs:
       mode: ${{ steps.normalise.outputs.mode }}
       dry-run: ${{ steps.normalise.outputs.dry-run }}
-      mission: ${{ steps.normalise.outputs.mission }}
+      mission-seed: ${{ steps.normalise.outputs.mission-seed }}
+      mission-text: ${{ steps.normalise.outputs.mission-text }}
       schedule: ${{ steps.normalise.outputs.schedule }}
       model: ${{ steps.normalise.outputs.model }}
 
@@ -89,7 +109,8 @@ jobs:
     env:
       INIT_MODE: ${{ needs.params.outputs.mode }}
       INIT_DRY_RUN: ${{ needs.params.outputs.dry-run }}
-      INIT_MISSION: ${{ needs.params.outputs.mission }}
+      INIT_MISSION_SEED: ${{ needs.params.outputs.mission-seed }}
+      INIT_MISSION_TEXT: ${{ needs.params.outputs.mission-text }}
     steps:
       - uses: actions/checkout@v4
         with:
@@ -114,15 +135,15 @@ jobs:
         run: |
           FLAGS="init"
           if [ "$INIT_MODE" = "reseed" ]; then FLAGS="$FLAGS --reseed"; fi
-          if [ "$INIT_MODE" = "purge" ]; then FLAGS="$FLAGS --purge"; fi
+          if [ "$INIT_MODE" = "purge" ]; then FLAGS="$FLAGS --purge --mission $INIT_MISSION_SEED"; fi
           if [ "$INIT_DRY_RUN" = "true" ]; then FLAGS="$FLAGS --dry-run"; fi
           npx @xn-intenton-z2a/agentic-lib $FLAGS
 
-      - name: Write mission (if provided)
-        if: env.INIT_MISSION != ''
+      - name: Write mission text (if provided, overrides seed)
+        if: env.INIT_MISSION_TEXT != ''
         run: |
-          printf '# Mission\n\n%s\n' "$INIT_MISSION" > MISSION.md
-          echo "Wrote custom mission to MISSION.md"
+          printf '# Mission\n\n%s\n' "$INIT_MISSION_TEXT" > MISSION.md
+          echo "Wrote custom mission text to MISSION.md"
 
       - run: npm install
 

package/src/seeds/missions/cron-engine.md

@@ -0,0 +1,35 @@
+# Mission
+
+A JavaScript library that parses cron expressions, computes next run times, and checks schedule matches.
+
+## Core Functions
+
+- `parseCron(expression)` — parse a cron expression (standard 5-field, or 6-field with seconds) into a structured object. Supports ranges (`1-5`), lists (`1,3,5`), steps (`*/15`), and wildcards (`*`).
+- `nextRun(expression, after?)` — compute the next run time after the given date (default: now). Returns a `Date`.
+- `nextRuns(expression, count, after?)` — compute the next N run times. Returns an array of `Date`.
+- `matches(expression, date)` — check if a date matches a cron expression. Returns boolean.
+- `toString(parsed)` — convert a parsed cron object back to a cron string.
+
+## Special Strings
+
+Support these shortcuts: `@yearly` (`0 0 1 1 *`), `@monthly` (`0 0 1 * *`), `@weekly` (`0 0 * * 0`), `@daily` (`0 0 * * *`), `@hourly` (`0 * * * *`).
+
+## Requirements
+
+- Handle edge cases: DST transitions, month-end boundaries (e.g. "30th of February"), leap years.
+- Validate expressions: throw on invalid syntax with a descriptive error message.
+- No external dependencies required (but allowed if beneficial).
+- Export all functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests covering field combinations, special strings, edge cases, and invalid input.
+- README with usage examples.
+
+## Acceptance Criteria
+
+- [ ] `parseCron("*/15 * * * *")` returns a valid parsed object
+- [ ] `nextRun("0 9 * * 1")` returns the next Monday at 09:00
+- [ ] `matches("0 0 25 12 *", new Date("2025-12-25"))` returns `true`
+- [ ] `nextRuns("@daily", 7)` returns 7 consecutive daily dates
+- [ ] DST transitions handled correctly (no skipped or duplicated runs)
+- [ ] Invalid expressions throw descriptive errors
+- [ ] All unit tests pass
+- [ ] README documents usage with examples

package/src/seeds/missions/dense-encoding.md

@@ -0,0 +1,37 @@
+# Mission
+
+A JavaScript library that explores the frontier of binary-to-text encoding density using printable characters. The benchmark: produce the shortest possible printable representation of a v7 UUID.
+
+## Core Functions
+
+- `encode(buffer, encoding)` / `decode(str, encoding)` — encode/decode arbitrary binary data using a named encoding.
+- `encodeUUID(uuid)` / `decodeUUID(str)` — shorthand for UUID encoding (strip dashes, encode the 16 bytes).
+- `createEncoding(name, charset)` — define a custom encoding from a character set string.
+- `listEncodings()` — return available encodings with their bit density and charset info.
+
+## Built-in Encodings
+
+The library should implement progressively denser encodings:
+
+- `base62` — `[0-9a-zA-Z]`, ~5.95 bits/char, URL-safe, 22 chars for a UUID
+- `base85` (Ascii85/Z85) — ~6.41 bits/char, 20 chars for a UUID
+- `base91` — ~6.50 bits/char, ~20 chars for a UUID
+- Optionally: custom higher bases cherry-picking from safe printable Unicode
+
+## Requirements
+
+- Round-trip property: `decode(encode(x, enc), enc)` must equal `x` for all inputs and all encodings.
+- No control characters, no ambiguous characters (0/O, 1/l/I in contexts where they matter).
+- Test across edge cases: all-zero bytes, all-0xFF bytes, single byte, empty buffer.
+- Compare encoded UUID lengths across all encodings.
+- Export all functions as named exports from `src/lib/main.js`.
+- README with UUID encoding comparison table.
+
+## Acceptance Criteria
+
+- [ ] At least 3 working encodings (base62, base85, one higher)
+- [ ] Round-trip correct for arbitrary binary data including edge cases
+- [ ] UUID encoding shorter than base64 (< 24 chars) for the densest encoding
+- [ ] `listEncodings()` returns encoding metadata
+- [ ] All unit tests pass
+- [ ] README shows UUID encoding comparison table

package/src/seeds/missions/empty.md

@@ -0,0 +1,3 @@
+# Mission
+
+Describe your project's mission here. The agentic workflows will evolve `src/lib/main.js` to fulfil this mission.

package/src/seeds/missions/fizz-buzz.md

@@ -0,0 +1,26 @@
+# Mission
+
+A JavaScript library exporting FizzBuzz functions. This is the simplest possible mission — if the pipeline can't complete this and stop, something is fundamentally broken.
+
+## Core Functions
+
+- `fizzBuzz(n)` — return an array of strings from 1 to n, replacing multiples of 3 with "Fizz", multiples of 5 with "Buzz", and multiples of both with "FizzBuzz".
+- `fizzBuzzSingle(n)` — return the FizzBuzz string for a single positive integer.
+
+## Requirements
+
+- Handle edge cases: `n = 0` returns an empty array, negative numbers throw `RangeError`, non-integers throw `TypeError`.
+- Export both functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests covering normal operation and all edge cases.
+- README with usage examples.
+
+## Acceptance Criteria
+
+- [ ] `fizzBuzz(15)` returns the correct 15-element array ending with "FizzBuzz"
+- [ ] `fizzBuzzSingle(3)` returns "Fizz"
+- [ ] `fizzBuzzSingle(5)` returns "Buzz"
+- [ ] `fizzBuzzSingle(15)` returns "FizzBuzz"
+- [ ] `fizzBuzzSingle(7)` returns "7"
+- [ ] `fizzBuzz(0)` returns `[]`
+- [ ] All unit tests pass
+- [ ] README documents usage with examples

package/src/seeds/missions/hamming-distance.md

@@ -0,0 +1,26 @@
+# Mission
+
+A JavaScript library exporting Hamming distance functions.
+
+## Core Functions
+
+- `hammingDistance(a, b)` — compute the Hamming distance between two strings of equal length (number of positions where characters differ). Throw an error if the strings have different lengths.
+- `hammingDistanceBits(x, y)` — compute the Hamming distance between two non-negative integers (count the number of differing bits).
+
+## Requirements
+
+- Handle Unicode strings correctly (compare code points, not UTF-16 code units).
+- Validate inputs: throw `TypeError` for non-string/non-integer arguments, `RangeError` for unequal-length strings or negative integers.
+- Export both functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests covering normal cases, edge cases (empty strings, zero, large integers), and error cases.
+- README with usage examples and API documentation.
+
+## Acceptance Criteria
+
+- [ ] `hammingDistance("karolin", "kathrin")` returns `3`
+- [ ] `hammingDistance("", "")` returns `0`
+- [ ] `hammingDistance("a", "bb")` throws `RangeError`
+- [ ] `hammingDistanceBits(1, 4)` returns `2` (binary: 001 vs 100)
+- [ ] `hammingDistanceBits(0, 0)` returns `0`
+- [ ] All unit tests pass
+- [ ] README documents usage with examples

package/src/seeds/missions/lunar-lander.md

@@ -0,0 +1,36 @@
+# Mission
+
+A JavaScript library that simulates a lunar lander descent and provides an autopilot controller.
+
+## Physics Model (1D simplified)
+
+- Initial altitude: 1000m, initial velocity: 40 m/s (toward surface), fuel: 25 units
+- Gravity: adds 2 m/s per tick to velocity (increasing downward speed)
+- Thrust: each fuel unit burned reduces velocity by 4 m/s
+- Landing: altitude reaches 0. Safe if velocity ≤ 4 m/s, crash if > 4 m/s
+
+## Core Functions
+
+- `createLander(opts?)` — create a lander state object with configurable initial conditions (altitude, velocity, fuel). Defaults to the values above.
+- `step(lander, thrust)` — advance one tick, burn `thrust` fuel units (clamped to available fuel), return a new state object. The state is immutable.
+- `simulate(lander, controller)` — run to completion using a controller function `(state) => thrustUnits`. Returns an array of states (the trace).
+- `autopilot(state)` — a built-in controller that lands safely. This is the algorithmically interesting part.
+- `score(trace)` — score a landing: 0 for crash, higher for less fuel used + lower landing velocity.
+
+## Requirements
+
+- The autopilot must land safely across a range of initial conditions: altitude 500–2000m, velocity 20–80 m/s, fuel 10–50 units.
+- State objects are plain objects: `{ altitude, velocity, fuel, tick, landed, crashed }`.
+- Export all functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests including physics correctness, autopilot safety across parameter ranges, and edge cases (zero fuel, already landed).
+- README with example simulation output showing a successful landing trace.
+
+## Acceptance Criteria
+
+- [ ] `step()` correctly applies gravity and thrust physics
+- [ ] `autopilot` lands safely with default initial conditions
+- [ ] `autopilot` lands safely across at least 10 different (altitude, velocity, fuel) combinations
+- [ ] `score()` returns 0 for crashes, positive for safe landings
+- [ ] `simulate()` returns a complete trace from start to landing
+- [ ] All unit tests pass
+- [ ] README shows example simulation output

package/src/seeds/missions/owl-ontology.md

@@ -0,0 +1,34 @@
+# Mission
+
+A JavaScript library that manages a simple OWL-like ontology stored as JSON-LD files in a `data/` directory. The pipeline should both build the library AND populate it with example ontology data over successive transform cycles.
+
+This is an ongoing mission. Do not set schedule to off.
+
+## Core Functions
+
+- `defineClass(name, superclass?)` — define an ontology class, optionally as a subclass.
+- `defineProperty(name, domain, range, opts?)` — define a property linking two classes.
+- `addIndividual(className, id, properties)` — add an instance of a class with property values.
+- `query(pattern)` — basic pattern matching over the ontology (e.g. find all instances of a class, find by property value).
+- `load(dir?)` — load ontology from JSON-LD files in the data directory.
+- `save(dir?)` — persist the ontology to JSON-LD files.
+- `stats()` — return counts of classes, properties, and individuals.
+
+## Requirements
+
+- Store data as JSON-LD files in `data/` (one file per class or a single graph file — implementer's choice).
+- The library should be usable both programmatically and to build up ontology data over time.
+- Export all functions as named exports from `src/lib/main.js`.
+- Include seed ontology data (e.g. a simple animal taxonomy) to demonstrate the library works.
+- Unit tests covering CRUD operations, querying, and persistence.
+- README with usage examples.
+
+## Acceptance Criteria
+
+- [ ] Can define classes and properties
+- [ ] Can add individuals and query them
+- [ ] Data persists to and loads from JSON-LD files
+- [ ] At least one example ontology (e.g. animals) is populated in `data/`
+- [ ] `stats()` returns correct counts
+- [ ] All unit tests pass
+- [ ] README documents the API with examples

package/src/seeds/missions/plot-code-lib.md

@@ -0,0 +1,24 @@
+# Mission
+
+_"Be a go-to plot library with a CLI, be the jq of formulae visualisations."_
+
+**plot-code-lib** is a JavaScript library and CLI tool designed to:
+- Transform and given range and a simple expression syntax for (pick an existing open standard) to time series data.
+- Read and write the time series data in a standard format (pick an existing open standard).
+- Make use of libraries for formula parsing, time series generation, plotting, and persistence in image formats.
+- Generate SVG and PNG plots from the time series data and save these as files.
+- Variations on this example: `node run start -- --expression "y=sin(x)" --range "x=-1:-1,y=-1:-1" --file output.svg` .
+- Showcase all the features of the library via a CLI by dry running tp generate example commands and output in the README.md file.
+
+`plot-code-lib` facilitate the creation of plots from mathematical expressions and time series data. It will take a
+mathematical expression and a range of values and generate a plot in SVG or PNG format.
+
+## Acceptance Criteria
+
+- [ ] Library parses mathematical expressions (e.g. `y=sin(x)`)
+- [ ] Generates time series data from expression and range
+- [ ] Produces SVG output files
+- [ ] Produces PNG output files
+- [ ] CLI interface works with `--expression`, `--range`, `--file` flags
+- [ ] README showcases example commands and output
+- [ ] All unit tests pass

package/src/seeds/missions/roman-numerals.md

@@ -0,0 +1,30 @@
+# Mission
+
+A JavaScript library for converting between integers and Roman numeral strings.
+
+## Core Functions
+
+- `toRoman(n)` — convert an integer (1–3999) to its Roman numeral representation using subtractive notation (IV, IX, XL, XC, CD, CM).
+- `fromRoman(s)` — convert a Roman numeral string back to an integer.
+
+## Requirements
+
+- Throw `RangeError` for numbers outside 1–3999.
+- Throw `TypeError` for invalid Roman numeral strings.
+- Handle subtractive notation correctly (e.g. IV = 4, not IIII).
+- The round-trip property must hold: `fromRoman(toRoman(n)) === n` for all valid n.
+- Export both functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests including boundary values (1, 3999), subtractive cases, and invalid inputs.
+- README with usage examples and conversion table.
+
+## Acceptance Criteria
+
+- [ ] `toRoman(1994)` returns `"MCMXCIV"`
+- [ ] `fromRoman("MCMXCIV")` returns `1994`
+- [ ] `toRoman(4)` returns `"IV"`
+- [ ] `fromRoman(toRoman(n)) === n` for all n in 1–3999
+- [ ] `toRoman(0)` throws `RangeError`
+- [ ] `toRoman(4000)` throws `RangeError`
+- [ ] `fromRoman("IIII")` throws or returns `4` (accept either; document the choice)
+- [ ] All unit tests pass
+- [ ] README documents usage with examples

package/src/seeds/missions/string-utils.md

@@ -0,0 +1,36 @@
+# Mission
+
+A JavaScript library of string utility functions. This is a bag-of-functions problem — each function is independent.
+
+## Core Functions
+
+Export each as a named function from `src/lib/main.js`:
+
+- `slugify(str)` — convert to URL-friendly slug (lowercase, hyphens, strip non-alphanumeric)
+- `truncate(str, maxLength, suffix?)` — truncate with suffix (default "…"), don't break mid-word
+- `camelCase(str)` — convert to camelCase
+- `kebabCase(str)` — convert to kebab-case
+- `titleCase(str)` — capitalise first letter of each word
+- `wordWrap(str, width)` — wrap text at word boundaries to given width
+- `stripHtml(str)` — remove HTML tags, decode common entities
+- `escapeRegex(str)` — escape special regex characters
+- `pluralize(word, count)` — basic English pluralisation (add "s", handle "y"→"ies", "s"→"ses", etc.)
+- `levenshteinDistance(a, b)` — compute edit distance between two strings
+
+## Requirements
+
+- Handle edge cases: empty strings, null/undefined (return empty string), Unicode characters.
+- No external dependencies required (but allowed if beneficial).
+- Comprehensive unit tests for each function including edge cases.
+- README with usage examples for each function.
+
+## Acceptance Criteria
+
+- [ ] All 10 functions are exported and work correctly
+- [ ] `slugify("Hello World!")` returns `"hello-world"`
+- [ ] `truncate("Hello World", 8)` returns `"Hello…"`
+- [ ] `camelCase("foo-bar-baz")` returns `"fooBarBaz"`
+- [ ] `levenshteinDistance("kitten", "sitting")` returns `3`
+- [ ] Edge cases (empty string, null, Unicode) handled gracefully
+- [ ] All unit tests pass
+- [ ] README documents all functions with examples

package/src/seeds/missions/time-series-lab.md

@@ -0,0 +1,41 @@
+# Mission
+
+A JavaScript library that finds, normalises, refreshes, and analyses temporal data. The repo's `data/` directory accumulates CSV/JSON datasets over successive transform cycles.
+
+This is an ongoing mission. Do not set schedule to off.
+
+## Core Capabilities
+
+- **Discover** — find publicly available time series data (APIs, open data portals) and fetch snapshots into `data/`.
+- **Normalise** — parse heterogeneous date/time formats, resample to uniform intervals, handle missing values.
+- **Refresh** — on each transform cycle, update existing datasets with newer observations (append, not replace).
+- **Forecast** — implement basic forecasting: moving average, exponential smoothing, linear regression.
+- **Correlate** — find relationships between datasets: cross-correlation, lag analysis.
+- **Report** — generate a `REPORT.md` summarising datasets, trends, and discovered correlations.
+
+## Core Functions
+
+- `discover(sources?)` — search for and download time series data into `data/`.
+- `load(file)` — load a CSV or JSON dataset, auto-detect date format.
+- `normalise(dataset, interval)` — resample to uniform intervals, interpolate missing values.
+- `refresh(file)` — update an existing dataset with newer data from its source.
+- `forecast(dataset, method, horizon)` — predict future values using the specified method.
+- `correlate(datasetA, datasetB)` — compute cross-correlation between two time series.
+- `report(datasets)` — generate a markdown summary report.
+
+## Requirements
+
+- Export all functions as named exports from `src/lib/main.js`.
+- Store datasets in `data/` as CSV or JSON with consistent schema.
+- Each dataset file should include metadata (source URL, last updated, interval).
+- Unit tests covering normalisation, forecasting accuracy, and correlation.
+- README with usage examples.
+
+## Acceptance Criteria
+
+- [ ] Can load and normalise at least one real-world dataset
+- [ ] Forecast produces reasonable predictions (tested against known data)
+- [ ] `data/` directory contains at least one dataset
+- [ ] `REPORT.md` is generated with dataset summaries
+- [ ] All unit tests pass
+- [ ] README documents the API with examples

package/src/seeds/zero-MISSION.md

@@ -1,14 +1,26 @@
 # Mission
 
-_"Be a go-to plot library with a CLI, be the jq of formulae visualisations."_
-
-**plot-code-lib** is a JavaScript library and CLI tool designed to:
-- Transform and given range and a simple expression syntax for (pick an existing open standard) to time series data.
-- Read and write the time series data in a standard format (pick an existing open standard).
-- Make use of libraries for formula parsing, time series generation, plotting, and persistence in image formats.
-- Generate SVG and PNG plots from the time series data and save these as files.
-- Variations on this example: `node run start -- --expression "y=sin(x)" --range "x=-1:-1,y=-1:-1" --file output.svg` .
-- Showcase all the features of the library via a CLI by dry running tp generate example commands and output in the README.md file.
-
-`plot-code-lib` facilitate the creation of plots from mathematical expressions and time series data. It will take a
-mathematical expression and a range of values and generate a plot in SVG or PNG format.
+A JavaScript library exporting Hamming distance functions.
+
+## Core Functions
+
+- `hammingDistance(a, b)` — compute the Hamming distance between two strings of equal length (number of positions where characters differ). Throw an error if the strings have different lengths.
+- `hammingDistanceBits(x, y)` — compute the Hamming distance between two non-negative integers (count the number of differing bits).
+
+## Requirements
+
+- Handle Unicode strings correctly (compare code points, not UTF-16 code units).
+- Validate inputs: throw `TypeError` for non-string/non-integer arguments, `RangeError` for unequal-length strings or negative integers.
+- Export both functions as named exports from `src/lib/main.js`.
+- Comprehensive unit tests covering normal cases, edge cases (empty strings, zero, large integers), and error cases.
+- README with usage examples and API documentation.
+
+## Acceptance Criteria
+
+- [ ] `hammingDistance("karolin", "kathrin")` returns `3`
+- [ ] `hammingDistance("", "")` returns `0`
+- [ ] `hammingDistance("a", "bb")` throws `RangeError`
+- [ ] `hammingDistanceBits(1, 4)` returns `2` (binary: 001 vs 100)
+- [ ] `hammingDistanceBits(0, 0)` returns `0`
+- [ ] All unit tests pass
+- [ ] README documents usage with examples

package/src/seeds/zero-package.json

@@ -14,7 +14,7 @@
   "author": "",
   "license": "MIT",
   "dependencies": {
-    "@xn-intenton-z2a/agentic-lib": "^7.1.44"
+    "@xn-intenton-z2a/agentic-lib": "^7.1.45"
   },
   "devDependencies": {
     "@vitest/coverage-v8": "^4.0.0",