@mokoconsulting/mokoabs-mcp 0.0.0-stage → 4.0.2

package/.mokogit/workflows/rc-revert.yml

@@ -0,0 +1,75 @@
+# Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
+#
+# SPDX-License-Identifier: GPL-3.0-or-later
+#
+# FILE INFORMATION
+# DEFGROUP: MokoGIT.Workflow
+# INGROUP: MokoCLI.Universal
+# REPO: https://git.mokoconsulting.tech/MokoConsulting/Template-Generic
+# PATH: /.mokogit/workflows/rc-revert.yml
+# VERSION: 09.23.00
+# BRIEF: Rename rc/ branch back to dev/ when PR is closed without merge
+
+name: "RC Revert"
+
+on:
+  pull_request:
+    types: [closed]
+
+permissions:
+  contents: write
+
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+jobs:
+  revert:
+    name: Rename rc/ back to dev/
+    runs-on: ubuntu-latest
+    if: >-
+      github.event.pull_request.merged == false &&
+      startsWith(github.event.pull_request.head.ref, 'rc/') &&
+      !startsWith(github.event.repository.name, 'Template-')
+
+    steps:
+      - name: Rename branch
+        env:
+          BRANCH: ${{ github.event.pull_request.head.ref }}
+          REPO: ${{ github.repository }}
+          GIT_URL: ${{ vars.MOKOGIT_URL || 'https://git.mokoconsulting.tech' }}
+          TOKEN: ${{ github.token }}
+        run: |
+          set -euo pipefail
+          # BRANCH is attacker-controlled (PR head ref). Strict allowlist before ANY use.
+          if ! printf '%s' "$BRANCH" | grep -Eq '^rc/[A-Za-z0-9._/-]+$'; then
+            echo "::error::Refusing unsafe branch name: $BRANCH"; exit 1
+          fi
+          SUFFIX="${BRANCH#rc/}"
+          DEV_BRANCH="dev/${SUFFIX}"
+          API="${GIT_URL}/api/v1/repos/${REPO}/branches"
+
+          # Create dev/ branch from rc/ branch
+          STATUS=$(curl -sf -o /dev/null -w "%{http_code}" -X POST \
+            -H "Authorization: token ${TOKEN}" \
+            -H "Content-Type: application/json" \
+            -d "{\"new_branch_name\": \"${DEV_BRANCH}\", \"old_branch_name\": \"${BRANCH}\"}" \
+            "${API}" 2>/dev/null || true)
+          if [ "$STATUS" = "201" ]; then
+            echo "Created branch: ${DEV_BRANCH}" >> "$GITHUB_STEP_SUMMARY"
+          else
+            echo "::error::Failed to create ${DEV_BRANCH} from ${BRANCH} (HTTP ${STATUS})"; exit 1
+          fi
+
+          # Read BRANCH from the environment inside PHP (getenv, no string interpolation -> no PHP injection)
+          ENCODED=$(php -r 'echo rawurlencode(getenv("BRANCH"));')
+          STATUS=$(curl -sf -o /dev/null -w "%{http_code}" -X DELETE \
+            -H "Authorization: token ${TOKEN}" \
+            "${API}/${ENCODED}" 2>/dev/null || true)
+          if [ "$STATUS" = "204" ]; then
+            echo "Deleted branch: ${BRANCH}" >> "$GITHUB_STEP_SUMMARY"
+          else
+            echo "::warning::Failed to delete ${BRANCH} (HTTP ${STATUS})"
+          fi
+
+          echo "### RC Reverted" >> "$GITHUB_STEP_SUMMARY"
+          echo "${BRANCH} → ${DEV_BRANCH}" >> "$GITHUB_STEP_SUMMARY"

package/AGENTS.md

@@ -0,0 +1,48 @@
+<!--
+  Copyright 2026 Moko Consulting
+  SPDX-License-Identifier: GPL-3.0-or-later
+
+  Brief: Agent instructions for the Template-NPM repository. This is the
+  authoritative, repo-specific guidance for AI agents. For company-wide
+  standards, follow the pointers referenced below rather than duplicating
+  them here.
+-->
+
+# Template-NPM — Agent Instructions
+
+Template-NPM is the scaffold template used to generate new MokoCLI-compliant
+MCP / npm API server repositories. Files committed here seed generated
+npm/MCP-server repos, so keep the scaffolding generic and ready to be renamed
+and filled in for a specific server.
+
+> Pointers: standards, contribution rules, and governance live in the
+> repository docs (CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md) and in
+> the MokoCLI standards wiki.
+
+## Platform & Layout
+
+- Role: scaffold template for npm/MCP servers (TypeScript/Node).
+- Seed source: scaffolding under `source/`; docs under `docs/`.
+- Tooling: npm (`package.json`), TypeScript (`tsconfig.json`), `Makefile`.
+- Config: `config.example.json` documents server configuration.
+- History: `CHANGELOG.md`.
+- Workflow/automation config lives under `.mokogit/`.
+
+## Commands
+
+- `npm install` — install dependencies.
+- `npm run build` — compile TypeScript (see `package.json` scripts).
+- `npm test` — run the test suite (see `package.json` scripts).
+
+## Rules
+
+- Never commit agent/tooling scratch: `.claude/`, `.gemini/`, `.mokoai/`,
+  `.mcp.json`, `TODO.md`, or minified/built assets.
+- Never commit real secrets — use `config.example.json` as the template only.
+- Repository workflow/automation configuration belongs under `.mokogit/`.
+- Attribute machine-authored commits with a trailer:
+  `Authored-by: Moko Consulting`.
+- Because this is a Template-* repo, CI is guarded to skip template repos; the
+  npm/MCP CI it defines runs in the generated child repos.
+- Standards: follow MokoCLI conventions —
+  https://git.mokoconsulting.tech/MokoConsulting/mokocli/wiki/Home

package/CHANGELOG.md

@@ -0,0 +1,37 @@
+## [Unreleased]
+
+## [04.00.00] --- 2026-09-11
+
+### Changed
+
+- **Stop reading the per-repo metadata API.** `resolve-source-dir` now resolves the
+  source dir purely from the Makefile `SRC_DIR` (source/ default); `pre-release.yml`
+  sources the platform from `platform_detect.php` (Makefile `PLATFORM`) instead of
+  `GET /repos/.../metadata`. The global platform registry (`GET /api/v1/platforms`)
+  is unchanged. Part of retiring the repo metadata tab/API.
+
+- CI (`auto-release.yml` / `pre-release.yml`): adopt the **bump-on-dev** release flow. The base version + CHANGELOG `[Unreleased]` promotion now happen on `dev` pre-promotion (promote-rc calls `release_bump_dev.php --branch dev --bump minor`); the RC and stable publishes run `--bump none --no-commit`, so `main` inherits the promoted version via the merge and never mints a divergent `chore(release): build` commit. The main changelog step is now an idempotent safety-net reconcile (no-op on the dev path, still promotes on `fix`/`hotfix`->main). `pre-release.yml`'s dev-push trigger skips `[skip ci]`/`[skip bump]` so the dev base-bump commit does not spawn a redundant dev build.
+
+### Added
+- Root `Makefile` with native build/test/lint/package/release logic. Its identity block (`PROJECT_NAME`/`PROJECT_VERSION`/`PLATFORM`) is the version source of truth, auto-filled per repo by the mokocli workflow sync (`--makefiles`).
+
+### Fixed
+- CI (`npm-build-test.yml`): removed the stranded `ci-summary` job (`needs: [build]`, `if: always()`). The Gitea act_runner never schedules a `needs:`+`if: always()` job — it parks in `waiting` (runner_id 0) forever, so under the org-governance `main` rule (`status_check_contexts: ["*"]`) it silently blocked every PR into `main`. Per-job status is already on the Actions run page and `wiki-reminder` posts its own sticky comment, so the aggregation job was redundant. Replaced with a NOTE comment (matches `ci-go.yml`). No other job changed.
+- CI (`cascade-dev.yml`): the main->dev cascade now authenticates its `git push origin dev` with the bypass-capable PAT (`secrets.MOKOGIT_TOKEN`) instead of the per-job action token. On repos where `dev` is branch-protected, the action token is not on dev's push-bypass allowlist, so the pre-receive hook declined the push and `dev` stranded behind `main`. Each of the three push sites (clean-merge, inline-resolved, cascade_resolve paths) reconfigures the `origin` remote to the PAT immediately before pushing, falling back to the action token when the secret is empty. Merge/resolve logic and all API-call tokens are unchanged. (#257)
+
+- CI: the stable release now prunes superseded-major `version/*` branches after publishing — keeps every `version/*` branch of the current major, retires older majors (no-op until a major bump). Same-repo deletes use the per-repo `github.token`.
+
+- CI: retire the generic `ci-generic.yml` (npm-build-test.yml is the platform CI).
+
+- Branding: Git -> MokoGIT in workflow DEFGROUP tags, committer identity (git-actions[bot] -> mokogit-actions[bot]), and platform prose. Functional tokens (GIT_TOKEN/GITHUB_TOKEN, GIT_ACTIONS_*, vars.GITEA_*, git.mokoconsulting.tech) preserved.
+
+### Removed
+- CI: stripped the retired GitHub Composer auth (`GH_MIRROR_TOKEN`/`GH_PAT` github-oauth) from the workflows — Composer installs the public dev-tools anonymously.
+- CI: stripped GitHub-only workflows (DEFGROUP GitHub.Workflow), which do not run on MokoGIT Actions: auto-dev-issue.yml changelog-validation.yml standards-compliance.yml sync-version-on-merge.yml.
+
+- Migrated all workflow and template paths from `.github/` to `.mokogit/`
+- Template source paths updated: `templates/git/` to `templates/mokogit/`
+- HCL definition files removed -- Template repos are now the canonical source
+
+- CI: gate build/CI/release/version workflows so they skip template repos; smart-gate the sync workflows to run only on Template-* repos; normalize mokocli/MokoCLI refs and drop the stale mokoconsulting-tech org slug.
+- `branch-cleanup.yml`: auto-delete merged feature branches after PR merge

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,70 @@
+<!--	Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
+
+	This file is part of a Moko Consulting project.
+
+	SPDX-LICENSE-IDENTIFIER: GPL-3.0-or-later
+
+	This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
+
+	This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the IMPLIED WARRANTY of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+	You should have received a copy of the GNU General Public License (./LICENSE).
+
+	# FILE INFORMATION
+	DEFGROUP: 
+	INGROUP: Project.Documentation
+	REPO: MokoConsulting/Template-NPM
+	VERSION: 01.01.00
+	PATH: ./CODE_OF_CONDUCT.md
+	BRIEF: Contributor Covenant Code of Conduct version 1.3.0
+-->
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@mokoconsulting.tech. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.3.0, available at [http://contributor-covenant.org/version/1/3/0/](http://contributor-covenant.org/version/1/3/0/)
+
+## Revision History
+
+| Date | Version | Author | Notes |
+| --- | --- | --- | --- |
+| 2026-01-16 | 1.3.0 | Copilot | Contributor Covenant v1.3.0 |

package/CONTRIBUTING.md

@@ -0,0 +1,164 @@
+<!--	Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
+
+	This file is part of a Moko Consulting project.
+
+	SPDX-LICENSE-IDENTIFIER: GPL-3.0-or-later
+
+	This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
+
+	This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the IMPLIED WARRANTY of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+	You should have received a copy of the GNU General Public License (./LICENSE).
+
+	# FILE INFORMATION
+	DEFGROUP: 
+	INGROUP: Project.Documentation
+	REPO: https://git.mokoconsulting.tech/MokoConsulting/Template-NPM
+	VERSION: 01.01.00
+	PATH: ./CONTRIBUTING.md
+	BRIEF: Contribution guidelines for the project
+-->
+
+# Contributing to Template-NPM
+
+> **Reporting issues:** This repository's issue tracker is disabled. All bugs, feature requests, and questions for MokoConsulting templates and shared tooling are tracked centrally in **[mokocli](https://git.mokoconsulting.tech/MokoConsulting/mokocli/issues)** — please open issues there, not in the individual template repos.
+
+
+We appreciate your interest in contributing to this project! This document provides guidelines for contributing.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [How to Contribute](#how-to-contribute)
+- [Development Workflow](#development-workflow)
+- [Commit Messages](#commit-messages)
+- [Pull Request Process](#pull-request-process)
+
+## Code of Conduct
+
+This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to hello@mokoconsulting.tech.
+
+## Getting Started
+
+1. Fork the repository
+2. Clone your fork locally
+3. Set up the development environment
+4. Create a new branch for your work
+
+## How to Contribute
+
+### Reporting Bugs
+
+- Use the GitHub issue tracker
+- Describe the bug clearly with steps to reproduce
+- Include relevant logs, screenshots, or error messages
+- Specify your environment (OS, version, etc.)
+
+### Suggesting Enhancements
+
+- Use the GitHub issue tracker
+- Clearly describe the enhancement and its benefits
+- Provide examples of how it would work
+
+### Contributing Code
+
+- Pick an issue or create one
+- Fork the repository and create a branch
+- Make your changes following the project conventions
+- Write or update tests as needed
+- Submit a pull request
+
+## Development Workflow
+
+1. Ensure your fork is up to date with the main repository
+2. Create a feature branch from `main`
+3. Make your changes
+4. Test your changes thoroughly
+5. Commit your changes with clear messages
+6. Push to your fork
+7. Create a pull request
+
+## Commit Messages
+
+Follow the conventional commit format:
+
+```
+<type>(<scope>): <subject>
+
+<body>
+
+<footer>
+```
+
+Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`, `ci`, `build`, `perf`, `revert`
+
+Example:
+```
+feat(docs): add contributing guidelines
+
+Add comprehensive contributing guidelines to help new contributors
+understand the development workflow and coding standards.
+```
+
+## Pull Request Process
+
+1. Update documentation for any new features
+2. Follow the project's coding style and conventions
+3. Ensure all tests pass
+4. Update the CHANGELOG.md with your changes
+5. Request review from maintainers
+6. Address any feedback promptly
+7. Once approved, your PR will be merged
+
+## Style Guidelines
+
+- Follow the `.editorconfig` settings
+- Use tabs for indentation (width: 2 spaces)
+- Ensure files end with a newline
+- Use LF line endings (except for Windows-specific files)
+- Trim trailing whitespace (except in Markdown)
+
+## Questions?
+
+If you have questions about contributing, feel free to open an issue or contact the maintainers.
+
+## Revision History
+
+| Date | Version | Author | Notes |
+| --- | --- | --- | --- |
+| 2026-01-16 | 0.1.0 | Copilot | Initial contributing guidelines |
+
+## Infrastructure Standards
+
+All repositories in the MokoConsulting org follow these conventions:
+
+### Release Tags
+
+Every repo maintains 5 standard release channel tags:
+
+- `development` - Active development builds
+- `alpha` - Early internal testing
+- `beta` - Broader testing / client UAT
+- `release-candidate` - Final QA before production
+- `stable` - Production release
+
+### Branch Protection
+
+- `main` is protected; only `jmiller` can push directly
+- All other contributors must use pull requests
+- PRs are automatically reviewed by Claude Code
+
+### CI/CD
+
+- MokoGIT Actions runs all CI workflows
+- GitHub Actions are disabled on mirrored repos
+- Workflows live in both `.github/workflows/` and `.mokogit/workflows/`
+
+### Update Servers (Joomla)
+
+In manifest `<updateservers>`, MokoGIT must be priority 1, GitHub priority 2.
+
+### Secrets
+
+All repos have `GA_TOKEN` and `GH_TOKEN` as Actions secrets for API access.