// MENKETECHNOLOGIESMETA — ENGINEERING REPORT

>_EXECUTIVE SUMMARY

MenkeTechnologiesMeta is a single umbrella git repository that vendors every active MenkeTechnologies project as a submodule. The goal: one git clone --recurse-submodules produces a fully-loaded development workstation with the language, shell, VM, CLIs, GUIs, plugins, completions, and supporting infrastructure already in place. Currently 64 submodules across 6 tiers, ~1.7 GB on disk, 27 Rust crates + 28 zsh plugins + 2 Tauri desktop apps + 1 Chrome extension + 2 web-API services + the public website.

~ SCALE & POSITION

MetricValueNotes
Submodules64All canonical URLs https://github.com/MenkeTechnologies/<repo>.git, flat layout
Tiers6Core, Stryke ecosystem, completions, zsh plugins, editor/multiplexer plugins, apps/web/APIs
Rust crates27All clippy/fmt/doc clean under -D warnings
Zsh plugins (Tier 4)28All have .github/workflows/ci.yml running zunit on each push
Total checkout~1.7 GBBulk: MenkeTechnologies.github.io (~514 MB — image history), strykelang (~352 MB — vendored compiler/runtime), zsh-more-completions (~203 MB), Audio-Haxor (~161 MB — Tauri + JUCE C++), zshrs (~120 MB), rest small
Homebrew tap10 formulasMenkeTechnologies/menketech — auto-bumped by each repo's release.yml

# TIER BREAKDOWN

TierCountDescription
Tier 1 — Core12strykelang, zshrs, fusevm, lsofrs, temprs, awkrs, iftoprs, Audio-Haxor, traderview, nmaprs, powerliners, zpwr
Tier 2 — Stryke ecosystem16homebrew-menketech + 15 stryke-* per-service connectors
Tier 3 — zsh-more-completions137,135-completion corpus (counts _* functions only — per scripts/print-repo-stats.zsh)
Tier 4 — Zsh plugins28full ZPWR_GH_PLUGINS canonical list
Tier 5 — Editor / multiplexer2VimColorSchemes (732 schemes), tmux-fzf-url
Tier 6 — Apps, ext, web, APIs5zpwrchrome, storageshower, MenkeTechnologies.github.io, spring-boot-rest-generator, LearningCollectionAPI

! POLISH GATES (per Rust crate)

The target polish bar for every Rust crate in the meta repo is to pass all four gates locally and in CI before a tag is cut. The shared release flow then promotes the binary to MenkeTechnologies/homebrew-menketech via the HOMEBREW_TAP_TOKEN cross-repo write secret. Audit gate tests/rust-ci-polish-gates.sh in the meta repo verifies the per-submodule ci.yml coverage; current state is 21 of 27 crates running all four (the 7 Tier 1 Rust binaries lsofrs/temprs/awkrs/iftoprs/nmaprs/storageshower/powerliners + all 14 stryke-* connectors). The remaining 6 enforce a subset — strykelang explicitly marks fmt/clippy advisory in its ci.yml header; zshrs and fusevm follow the same pattern; Audio-Haxor and traderview are Tauri apps with pnpm-driven build pipelines; spring-boot-rest-generator is mid-transition from Kotlin to Rust.

@ META REPO CI

.github/workflows/ci.yml on the meta repo runs 5 gate jobs on every push:

  1. .gitmodules syntax — path/url count match, every URL is canonical https://github.com/MenkeTechnologies/*.git, no nested paths
  2. Submodule URL reachabilitygit ls-remote every URL
  3. Shellcheck across bin/* helper scripts
  4. bin/ smokebin/status-all + bin/foreach don't crash on empty checkout
  5. README link sanity — 5 independent drift gates: (a) every .gitmodules path is referenced from README, (b) submodule-count badge matches actual entry count, (c) each ### Tier N — Label (M) header has exactly M table rows + tier-counts sum to total submodules, (d) docs/index.html stat-cards for submodules, tiers, and zsh plugins match README values, (e) rust crates stat-card matches actual top-level Cargo.toml count (skipped when submodules aren't initialized in this job's checkout)

% HELPER SCRIPTS (bin/)

ScriptRole
bin/pull-allPull every submodule to its tracking-branch tip in parallel
bin/status-allOne-line status for every submodule (branch + ahead/behind + dirty marker)
bin/foreachRun an arbitrary shell command inside every submodule
bin/sync-pointersStage + commit all submodule pointer bumps as one commit

^ DEPENDENCY POSTURE

Cross-repo Cargo.lock sweep run periodically — cargo update across all 27 Rust crates, lockfile committed, CI re-run. Dependabot security PRs (e.g. rustls-webpki, rand) get absorbed into the same sweep when they appear. Major-version bumps require maintainer review and aren't auto-applied.

. NEXT

Roadmap is per-repo; consult each project's docs/report.html for codebase-specific milestones. Meta repo's own roadmap is light: