binding-architecture

The shared Cargo feature-flag naming and semantics contract across xberg-io Rust libraries — the same flag names mean the same thing everywhere (otel…

Release/publish a Rust core crate or CLI in an xberg-io polyglot repo (crawlberg, html-to-markdown, xberg, tree-sitter-language-pack, liter-llm).

The canonical contract for tracing as a first-class product observability surface across xberg-io Rust libraries and services — level semantics, span/field…

Canonical xberg.io brand, product catalog, docs-site (Astro Starlight + @xberg-io/docs-theme), alef badge, docs task commands, prose style, Google Analytics…

How to dispatch, monitor, recover, and trust subagents and worktree-isolated peers safely in a repo other agents may also be touching.

Reproduce an alef-generated consumer repo's release gate locally before cutting a release, and verify published package names against the real manifest rather…

Developer quick-start for xberg-io repos — prerequisites, initial setup, and the core build/test/lint workflow.

How to use basemind's MCP tools and CLI for structural and historical code questions instead of grep, file reads, and naked git.

Standard Taskfile conventions across xberg-io repos — task discovery, common and language-scoped tasks, build profiles, the alef and e2e task families…

Reference for poly, the single-binary multi-language linter and formatter — per-language engines, the lint/fmt commands, poly.toml configuration, severity…

How to author a new e2e test fixture for cross-language test generation — fixture fields, assertion types, and id conventions.

Maintain the Windows Scoop release channel: the per-repo manifest template and config, the publish-scoop-manifest job, and the shared xberg-io/scoop-bucket.