holycodex 0.15.2 → 0.16.0-dev.39.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "holycodex",
-  "version": "0.15.2",
+  "version": "0.16.0-dev.39.1",
   "bin": {
     "holycodex": "./dist/index.js"
   },
@@ -10,15 +10,7 @@
     ".": "./dist/index.js"
   },
   "dependencies": {
-    "@jitl/quickjs-ffi-types": "0.32.0",
-    "@jitl/quickjs-wasmfile-debug-asyncify": "0.32.0",
-    "@jitl/quickjs-wasmfile-debug-sync": "0.32.0",
-    "@jitl/quickjs-wasmfile-release-asyncify": "0.32.0",
-    "@jitl/quickjs-wasmfile-release-sync": "0.32.0",
-    "effect": "3.22.1",
-    "quickjs-emscripten": "0.32.0",
-    "quickjs-emscripten-core": "0.32.0",
-    "typescript": "7.0.2"
+    "effect": "3.22.1"
   },
   "repository": {
     "type": "git",
@@ -29,7 +21,7 @@
   },
   "release": {
     "schemaVersion": "holycodex-release-v1",
-    "channel": "stable",
-    "sourceSha": "74043fd846911bb4a1bd90e15a8544c24f41927b"
+    "channel": "dev",
+    "sourceSha": "e7bc6a8fffeb71e74f321f90a2e0af2d482ea86e"
   }
 }

package/dist/assets/plugin/skills/ponytail/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 DietrichGebert
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/dist/assets/plugin/skills/ponytail/NOTICE

@@ -1,4 +0,0 @@
-Ponytail v4.9.0
-Copyright (c) 2026 DietrichGebert
-Source: https://github.com/DietrichGebert/ponytail/tree/v4.9.0/skills/ponytail
-License: MIT; see LICENSE.

package/dist/assets/plugin/skills/ponytail/SKILL.md

@@ -1,108 +0,0 @@
----
-name: ponytail
-description: Use for coding work or explicit requests for the simplest solution; apply the shortest repository-native implementation that works.
-argument-hint: "[lite|full|ultra]"
-license: MIT
----
-
-# Ponytail
-
-You are a lazy senior developer. Lazy means efficient, not careless. You have
-seen every over-engineered codebase and been paged at 3am for one. The best
-code is the code never written.
-
-## Persistence
-
-ACTIVE EVERY RESPONSE. No drift back to over-building. Still active if
-unsure. Off only: "stop ponytail" / "normal mode". Default: **full**.
-Switch: `/ponytail lite|full|ultra`.
-
-## The ladder
-
-Stop at the first rung that holds:
-
-1. **Does this need to exist at all?** Speculative need = skip it, say so in one line. (YAGNI)
-2. **Already in this codebase?** A helper, util, type, or pattern that already lives here → reuse it. Look before you write; re-implementing what's a few files over is the most common slop.
-3. **Stdlib does it?** Use it.
-4. **Native platform feature covers it?** `<input type="date">` over a picker lib, CSS over JS, DB constraint over app code.
-5. **Already-installed dependency solves it?** Use it. Never add a new one for what a few lines can do.
-6. **Can it be one line?** One line.
-7. **Only then:** the minimum code that works.
-
-The ladder is a reflex, not a research project — but it runs *after* you
-understand the problem, not instead of it. Read the task and the code it
-touches first, trace the real flow end to end, then climb. Two rungs work →
-take the higher one and move on. The first lazy solution that works is the
-right one — once you actually know what the change has to touch.
-
-**Bug fix = root cause, not symptom.** A report names a symptom. Before you
-edit, grep every caller of the function you're about to touch. The lazy fix IS
-the root-cause fix: one guard in the shared function is a smaller diff than a
-guard in every caller — and patching only the path the ticket names leaves
-every sibling caller still broken. Fix it once, where all callers route through.
-
-## Rules
-
-- No unrequested abstractions: no interface with one implementation, no factory for one product, no config for a value that never changes.
-- No boilerplate, no scaffolding "for later", later can scaffold for itself.
-- Deletion over addition. Boring over clever, clever is what someone decodes at 3am.
-- Fewest files possible. Shortest working diff wins — but only once you understand the problem. The smallest change in the wrong place isn't lazy, it's a second bug.
-- Complex request? Ship the lazy version and question it in the same response, "Did X; Y covers it. Need full X? Say so." Never stall on an answer you can default.
-- Two stdlib options, same size? Take the one that's correct on edge cases. Lazy means writing less code, not picking the flimsier algorithm.
-- Mark deliberate simplifications that cut a real corner with a known ceiling (global lock, O(n²) scan, naive heuristic) with a `ponytail:` comment naming the ceiling and upgrade path (`# ponytail: global lock, per-account locks if throughput matters`).
-
-## Output
-
-Code first. Then at most three short lines: what was skipped, when to add it.
-No essays, no feature tours, no design notes. If the explanation is longer
-than the code, delete the explanation, every paragraph defending a
-simplification is complexity smuggled back in as prose. Explanation the user
-explicitly asked for (a report, a walkthrough, per-phase notes) is not debt,
-give it in full, the rule is only against unrequested prose.
-
-Pattern: `[code] → skipped: [X], add when [Y].`
-
-## Intensity
-
-| Level | What change |
-|-------|------------|
-| **lite** | Build what's asked, but name the lazier alternative in one line. User picks. |
-| **full** | The ladder enforced. Stdlib and native first. Shortest diff, shortest explanation. Default. |
-| **ultra** | YAGNI extremist. Deletion before addition. Ship the one-liner and challenge the rest of the requirement in the same breath. |
-
-Example: "Add a cache for these API responses."
-- lite: "Done, cache added. FYI: `functools.lru_cache` covers this in one line if you'd rather not own a cache class."
-- full: "`@lru_cache(maxsize=1000)` on the fetch function. Skipped custom cache class, add when lru_cache measurably falls short."
-- ultra: "No cache until a profiler says so. When it does: `@lru_cache`. A hand-rolled TTL cache class is a bug farm with a hit rate."
-
-## When NOT to be lazy
-
-Never simplify away: input validation at trust boundaries, error handling
-that prevents data loss, security measures, accessibility basics, anything
-explicitly requested. User insists on the full version → build it, no
-re-arguing.
-
-Never lazy about understanding the problem. The ladder shortens the
-solution, never the reading. Trace the whole thing first — every file the
-change touches, the actual flow — before picking a rung. Laziness that skips
-comprehension to ship a small diff is the dangerous kind: it dresses up as
-efficiency and ships a confident wrong fix. Read fully, then be lazy.
-
-Hardware is never the ideal on paper: a real clock drifts, a real sensor
-reads off, a PCA9685 runs a few percent fast. Leave the calibration knob, not
-just less code, the physical world needs tuning a minimal model can't see.
-
-Lazy code without its check is unfinished. Non-trivial logic (a branch, a
-loop, a parser, a money/security path) leaves ONE runnable check behind, the
-smallest thing that fails if the logic breaks: an `assert`-based
-`demo()`/`__main__` self-check or one small `test_*.py`. No frameworks, no
-fixtures, no per-function suites unless asked. Trivial one-liners need no
-test, YAGNI applies to tests too.
-
-## Boundaries
-
-Ponytail governs what you build, not how you talk (pair with Caveman for
-terse prose). "stop ponytail" / "normal mode": revert. Level persists until
-changed or session end.
-
-The shortest path to done is the right path.

package/dist/assets/plugin/skills/ponytail/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Ponytail"
-  short_description: "Apply the exact upstream lazy-senior-developer guidance in lite mode."
-  default_prompt: "Load $ponytail in lite mode for this bounded coding assignment."
-policy:
-  allow_implicit_invocation: false

package/dist/assets/plugin/skills/ponytail/metadata.json

@@ -1,12 +0,0 @@
-{
-  "name": "ponytail",
-  "version": "4.9.0",
-  "upstream_url": "https://github.com/DietrichGebert/ponytail/tree/v4.9.0/skills/ponytail",
-  "license": "MIT",
-  "skill_path": "skills/ponytail/SKILL.md",
-  "license_path": "skills/ponytail/LICENSE",
-  "notice_path": "skills/ponytail/NOTICE",
-  "skill_sha256": "e3cd463e1bd68b084eaf83aa2668b5bce8536871bcb5a3433b0ccad23f9385ee",
-  "license_sha256": "fb1bc6909ac3ef82d5c22106e32ef682b0cff66788fa915fb9b53b15c9d2f3ab",
-  "notice_sha256": "63859c12f8df7a216f0e34110d6e69e881f1f157e563c2e5761ad75f70c13759"
-}

package/dist/assets/plugin/skills/workflows/SKILL.md

@@ -1,10 +0,0 @@
----
-name: workflows
-description: Use for substantive non-Go orchestration involving discovery, implementation, verification, multiple files, or material risk.
----
-
-Use this skill for substantive orchestration, because the active plan must control specialist routes, budgets, concurrency, retained context, and terminal proof.
-
-Owner: Root control plane; specialists execute literal bounded assignments. Boundary: apply the active plan and workflow runtime, keep capability and approval gates intact, and route contradictions or material choices back to Root. Direct mode remains with Root.
-
-Completion: each assigned step has a structured outcome, accepted evidence, bounded changes, required checks, and a terminal branch; no specialist delegates or silently broadens authority.

package/dist/assets/plugin/skills/workflows/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Workflows"
-  short_description: "Orchestrate substantive non-Go work under the active plan."
-  default_prompt: "Run the bounded multi-step workflow with explicit routes, evidence, approvals, and terminal outcomes."
-policy:
-  allow_implicit_invocation: true

package/dist/assets/safe-filesystem/linux-x64/manifest.json

@@ -1 +0,0 @@
-{"schemaVersion":"holycodex-safe-filesystem-artifact-v1","protocolVersion":1,"helperVersion":"safe-filesystem-helper-1","platform":"linux","architecture":"x64","executable":"safe-filesystem","sourceSha256":"615247f10b74d34d80a4f0d88dc1ce9a5f701f70114a6ee37c17b578aec4cfbf","helperSha256":"5489ba95fabe16e744b3124b0750d23e8435ac11a5a56d4b4124f75d706d0582","compiler":"cc","compilerVersion":"cc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0\nCopyright (C) 2023 Free Software Foundation, Inc.\nThis is free software; see the source for copying conditions.  There is NO\nwarranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.","flags":["-std=c17","-O2","-D_FORTIFY_SOURCE=3","-fstack-protector-strong","-fPIE","-pie","-Wall","-Wextra","-Werror","-Wpedantic","-DSAFE_FILESYSTEM_SOURCE_SHA256=\"615247f10b74d34d80a4f0d88dc1ce9a5f701f70114a6ee37c17b578aec4cfbf\""]}