codexloop 0.3.1__tar.gz → 0.4.0__tar.gz

codexloop-0.4.0/.gitattributes

@@ -0,0 +1,2 @@
+# vibey-gh: append-only files merge instead of conflicting
+CHANGELOG.md merge=union

codexloop-0.4.0/.githooks/commit-msg

@@ -0,0 +1,67 @@
+#!/bin/sh
+# Installed by `vibey-gh install` — do not edit; edit the template in vibey-gh.
+#
+# Appends the provenance trailer to any commit message that lacks it, so the rule holds
+# locally without anyone having to remember it. CI enforces the same trailer, so a commit
+# made without this hook fails the pull request rather than slipping through.
+
+
+# Resolve the CLI. `vibey-gh` on PATH is the normal case, but a project virtualenv that
+# has not been activated is just as normal — and a gate that reports "not installed"
+# when the tool IS installed is a gate people learn to bypass. Look where it actually
+# lives before giving up. Hooks run from the top of the working tree.
+vibey_gh() {
+  # A repository that IS vibey-gh must run its own working tree, never an installed copy.
+  # Its `develop` is ahead of the last release nearly always, so a globally installed
+  # vibey-gh compares the repository's managed assets against the older ones it bundles,
+  # reports them out of date, and refuses every push — a contributor who installed the
+  # tool the obvious way cannot commit to it. The package is dependency-free stdlib, so
+  # `python3 -m` against the checkout needs no install and no virtualenv at all.
+  if [ -f pyproject.toml ] && grep -qE '^name = "vibey-gh"' pyproject.toml \
+    && [ -d vibey_gh ] && python3 -c "import vibey_gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_gh.cli "$@"
+  elif command -v vibey-gh >/dev/null 2>&1; then
+    vibey-gh "$@"
+  elif [ -n "${VIRTUAL_ENV:-}" ] && [ -x "${VIRTUAL_ENV}/bin/vibey-gh" ]; then
+    "${VIRTUAL_ENV}/bin/vibey-gh" "$@"
+  elif [ -x ".venv/bin/vibey-gh" ]; then
+    ./.venv/bin/vibey-gh "$@"
+  elif [ -x "venv/bin/vibey-gh" ]; then
+    ./venv/bin/vibey-gh "$@"
+  elif python3 -c "import vibey_gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_gh.cli "$@"
+  elif python3 -c "import vibey_bootstrap.gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_bootstrap.gh.cli "$@"   # pre-split layout
+  else
+    return 127
+  fi
+}
+
+
+msg_file="$1"
+key=$(vibey_gh trailer-key 2>/dev/null || echo "Made-With")
+trailer=$(vibey_gh trailer 2>/dev/null || echo "Made-With: Made with ❤️ by [Vibey](https://adammatthewsteinberger.github.io/vibey/), Developed by [Adam Matthew Steinberger](https://hire.adam.matthewsteinberger.com/) ([@adammatthewsteinberger](https://github.com/adammatthewsteinberger/)).")
+
+# A pre-existing project hook runs first and may do its own thing.
+[ -x "$(dirname "$0")/commit-msg.local" ] && "$(dirname "$0")/commit-msg.local" "$@"
+
+# Normalize the subject without assuming the Python package is importable in the hook's
+# process. The body and existing trailers remain unchanged.
+subject=$(sed -n '1p' "$msg_file")
+if [ -n "$subject" ] && ! printf '%s\n' "$subject" | grep -Eq '^[a-z][a-z0-9-]*(\([a-z0-9][a-z0-9._/-]*\))?!?: [^[:space:]].*$'; then
+  tmp="${msg_file}.vibey-gh.tmp"
+  { printf 'chore: %s\n' "$subject"; sed '1d' "$msg_file"; } > "$tmp"
+  mv "$tmp" "$msg_file"
+fi
+
+# Already present in any case — nothing to do.
+if grep -qiE "^${key}:[[:space:]]*[^[:space:]]" "$msg_file"; then
+  exit 0
+fi
+
+# A comment-only or empty message means an aborted commit; leave it alone.
+if ! grep -qvE '^\s*(#.*)?$' "$msg_file"; then
+  exit 0
+fi
+
+printf '\n%s\n' "$trailer" >> "$msg_file"

codexloop-0.4.0/.githooks/commit-msg.local

@@ -0,0 +1,11 @@
+#!/bin/sh
+# vibey-gh owns core.hooksPath, so .git/hooks is never consulted again and the
+# pre-commit framework's hooks would silently stop running -- a worse failure
+# than any gate they enforce, because everything keeps looking green.
+#
+# Delegates to the framework's OWN generated hook rather than calling
+# `pre-commit run`: that script knows where its environment lives, and a git
+# hook does not inherit an activated virtualenv, so re-invoking by name finds
+# the wrong tools or none at all.
+[ -x ".git/hooks/commit-msg" ] || exit 0
+exec ".git/hooks/commit-msg" "$@"

codexloop-0.4.0/.githooks/pre-commit

@@ -0,0 +1,11 @@
+#!/bin/sh
+# vibey-gh owns core.hooksPath, so .git/hooks is never consulted again and the
+# pre-commit framework's hooks would silently stop running -- a worse failure
+# than any gate they enforce, because everything keeps looking green.
+#
+# Delegates to the framework's OWN generated hook rather than calling
+# `pre-commit run`: that script knows where its environment lives, and a git
+# hook does not inherit an activated virtualenv, so re-invoking by name finds
+# the wrong tools or none at all.
+[ -x ".git/hooks/pre-commit" ] || exit 0
+exec ".git/hooks/pre-commit" "$@"

codexloop-0.4.0/.githooks/pre-push

@@ -0,0 +1,78 @@
+#!/bin/sh
+# Installed by `vibey-gh install` — do not edit; edit the template in vibey-gh.
+#
+# THE GATE. A repository that has adopted the vibey GitHub automation must keep it
+# installed and working. If the tooling is missing, or the fingerprints it enforces are
+# not intact, the push is refused — to any branch, local or remote.
+#
+# The point is not ceremony. Provenance that can be skipped whenever it is inconvenient
+# is provenance nobody can rely on, so the check has to sit on the last action before
+# code leaves the machine.
+#
+# Escape hatch: `git push --no-verify` still works, because a hook that cannot be
+# bypassed in an emergency gets uninstalled instead. CI applies the same rule server-side,
+# so skipping here only defers the failure rather than avoiding it.
+
+set -e
+
+red() { printf '\033[0;31m%s\033[0m\n' "$1"; }
+
+
+# Resolve the CLI. `vibey-gh` on PATH is the normal case, but a project virtualenv that
+# has not been activated is just as normal — and a gate that reports "not installed"
+# when the tool IS installed is a gate people learn to bypass. Look where it actually
+# lives before giving up. Hooks run from the top of the working tree.
+vibey_gh() {
+  # A repository that IS vibey-gh must run its own working tree, never an installed copy.
+  # Its `develop` is ahead of the last release nearly always, so a globally installed
+  # vibey-gh compares the repository's managed assets against the older ones it bundles,
+  # reports them out of date, and refuses every push — a contributor who installed the
+  # tool the obvious way cannot commit to it. The package is dependency-free stdlib, so
+  # `python3 -m` against the checkout needs no install and no virtualenv at all.
+  if [ -f pyproject.toml ] && grep -qE '^name = "vibey-gh"' pyproject.toml \
+    && [ -d vibey_gh ] && python3 -c "import vibey_gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_gh.cli "$@"
+  elif command -v vibey-gh >/dev/null 2>&1; then
+    vibey-gh "$@"
+  elif [ -n "${VIRTUAL_ENV:-}" ] && [ -x "${VIRTUAL_ENV}/bin/vibey-gh" ]; then
+    "${VIRTUAL_ENV}/bin/vibey-gh" "$@"
+  elif [ -x ".venv/bin/vibey-gh" ]; then
+    ./.venv/bin/vibey-gh "$@"
+  elif [ -x "venv/bin/vibey-gh" ]; then
+    ./venv/bin/vibey-gh "$@"
+  elif python3 -c "import vibey_gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_gh.cli "$@"
+  elif python3 -c "import vibey_bootstrap.gh.cli" >/dev/null 2>&1; then
+    python3 -m vibey_bootstrap.gh.cli "$@"   # pre-split layout
+  else
+    return 127
+  fi
+}
+
+if ! vibey_gh trailer-key >/dev/null 2>&1; then
+  red "✖ push refused: the vibey GitHub automation is not installed."
+  echo
+  echo "  This repository requires it for provenance and release automation."
+  echo
+  echo "      pip install vibey-gh"
+  echo "      vibey-gh install"
+  echo
+  echo "  Then push again. To bypass once: git push --no-verify"
+  exit 1
+fi
+
+if ! vibey_gh check --quiet; then
+  red "✖ push refused: the provenance fingerprints are not intact."
+  echo
+  echo "      vibey-gh check          # see what is missing"
+  echo "      vibey-gh check --apply  # add the missing file headers"
+  echo
+  echo "  Commit trailers are added automatically by the commit-msg hook."
+  echo "  To bypass once: git push --no-verify"
+  exit 1
+fi
+
+# Chain to a pre-existing project hook, so adopting this does not discard local checks.
+if [ -x "$(dirname "$0")/pre-push.local" ]; then
+  "$(dirname "$0")/pre-push.local" "$@"
+fi

codexloop-0.4.0/.githooks/pre-push.local

@@ -0,0 +1,11 @@
+#!/bin/sh
+# vibey-gh owns core.hooksPath, so .git/hooks is never consulted again and the
+# pre-commit framework's hooks would silently stop running -- a worse failure
+# than any gate they enforce, because everything keeps looking green.
+#
+# Delegates to the framework's OWN generated hook rather than calling
+# `pre-commit run`: that script knows where its environment lives, and a git
+# hook does not inherit an activated virtualenv, so re-invoking by name finds
+# the wrong tools or none at all.
+[ -x ".git/hooks/pre-push" ] || exit 0
+exec ".git/hooks/pre-push" "$@"

codexloop-0.4.0/.github/vibey-gh/release/channel.js

@@ -0,0 +1,63 @@
+(() => {
+  "use strict";
+
+  document.documentElement.dataset.bsTheme = "dark";
+
+  const segments = window.location.pathname.split("/").filter(Boolean);
+  const channel = segments.includes("develop") ? "develop" : "main";
+  document.body.dataset.releaseChannel = channel;
+
+  const brand = document.querySelector(".navbar-brand");
+  if (brand) {
+    const badge = document.createElement("span");
+    badge.className = "release-badge";
+    badge.innerHTML = `<span aria-hidden="true"></span>${channel === "main" ? "__PRODUCTION_LABEL__" : "__PREVIEW_LABEL__"}`;
+    brand.insertAdjacentElement("afterend", badge);
+  }
+
+  const primaryNav = document.querySelector("#navbar-collapse .navbar-nav");
+  if (primaryNav) {
+    const pagesRoot = "__PAGES_ROOT__";
+    primaryNav.querySelectorAll("a.nav-link").forEach((link) => {
+      if (link.textContent.trim() === "Home") {
+        link.href = pagesRoot;
+      } else {
+        link.closest("li")?.remove();
+      }
+    });
+    for (const [label, target] of [["__PRODUCTION_LABEL__", "main"], ["__PREVIEW_LABEL__", "develop"]]) {
+      const item = document.createElement("li");
+      item.className = "nav-item";
+      const link = document.createElement("a");
+      link.className = `nav-link channel-link${channel === target ? " active" : ""}`;
+      link.href = `${pagesRoot}${target}/`;
+      link.textContent = label;
+      item.append(link);
+      primaryNav.append(item);
+    }
+    document.querySelectorAll("[data-release-target]").forEach((link) => {
+      link.href = `${pagesRoot}${link.dataset.releaseTarget}/`;
+    });
+  }
+
+  const editLink = [...document.querySelectorAll("a.nav-link")].find((link) =>
+    link.textContent.includes("Edit on GitHub"),
+  );
+  if (editLink) {
+    editLink.href = editLink.href.replace("/edit/main/", `/edit/${channel}/`);
+  }
+
+  const footer = document.querySelector("footer.col-md-12");
+  if (footer) {
+    const provenance = document.createElement("p");
+    provenance.className = "release-provenance";
+    provenance.innerHTML = [
+      `<strong>Provenance</strong>`,
+      `<a href="__REPOSITORY_URL__/tree/__RELEASE_SHA__">__REPOSITORY__@__SHORT_SHA__</a>`,
+      `<span>branch / __RELEASE_BRANCH__</span>`,
+      `<span>channel / __RELEASE_CHANNEL__</span>`,
+      `<span>Made with ❤️ by <a href="https://adammatthewsteinberger.github.io/vibey/">Vibey</a>, Developed by <a href="https://hire.adam.matthewsteinberger.com/">Adam Matthew Steinberger</a> (<a href="https://github.com/adammatthewsteinberger/">@adammatthewsteinberger</a>).</span>`,
+    ].join('<span aria-hidden="true">·</span>');
+    footer.append(provenance);
+  }
+})();