Skip to content

Latest commit

 

History

History
98 lines (79 loc) · 5.46 KB

workflow.md

File metadata and controls

98 lines (79 loc) · 5.46 KB

Workflow Facts for eser/stack

Facts about the eser/stack repository that the workflow-practices skill refers to. The skill states the rules; this file names the concrete areas, commands and files they apply to here.

Full Gate and Narrower Commands

The full gate is eser ok, which pnpm ok runs as go run ./cmd/eser ok. It runs the precommit workflow of .eser/manifest.yml on the Go eser (cmd/eser, the engine in pkg/ajan/workflowfx): the codebasefx validators under their validate-* names, then oxfmt --check, oxlint, tsc --noEmit, the node:test suites with coverage and the Go checks as shell steps. pnpm fix (eser fix) runs it with fixes, and pnpm preflight (eser preflight) runs the preflight workflow. The git hooks that eser codebase install writes run the same Go eser.

go run ./cmd/eser workflows run -e precommit --only validate-eof   # one validator step
go run ./cmd/eser workflows run -e precommit --only go-lint        # one shell step, by its name
go run ./cmd/eser codebase validate-licenses [--fix]               # one validator, with its manifest options
pnpm cli go-ok     # Go only; same as make ok
make lint          # golangci-lint on the root module
make test          # go test -race
pnpm cli test      # node:test with coverage
pnpm preflight     # release-only steps; needed before tagging

--only matches a step's tool name or its name, so it selects a validator or a shell step, and a filter that matches no step fails the run and names the filter.

make ok covers Go only, so it never replaces pnpm ok for a change that touches TypeScript.

File Ownership

Area Concern
pkg/@eserstack/standards/ Cross-runtime abstractions; high impact, every package depends on it
pkg/@eserstack/codebase/ Git, package config and workspace helpers; tooling in pkg/ajan/codebasefx
pkg/@eserstack/shell/ CLI framework and TUI; owns cli-system/, the command tree of every binary
cmd/eser/ The eser binary; pkg/@eserstack/eser-bin/ is its npm launcher
pkg/@eserstack/noskills*/ Spec workflow, daemon client, web dashboard
pkg/@eserstack/laroux*/ Framework: server, bundler, React integration
pkg/@eserstack/ai/ AI providers: TypeScript adapters and the Go bridge
pkg/@eserstack/kit/ Recipes and scaffolding
pkg/@eserstack/ajan/ FFI bridge to the Go library; its own Go module
pkg/ajan/ Go library packages (*fx); api/business/ is pure domain, api/adapters/ is I/O
pkg/ajan/noskillsserverfx/ The noskills daemon: sessions, ledger, agent and mux workers
cmd/ Go entry points: eser, noskills, noskills-server and the laroux stub
.github/workflows/ CI/CD; high impact
.eser/ Workflow manifest, recipes and scripts
.agents/skills/ Agent rules; update them when a convention changes

A package is pkg/@eserstack/<name>/ or one pkg/ajan/<name>fx/.

High-Impact Changes That Need Approval

  • a new import between @eserstack/* packages that did not depend on each other before;
  • any change to @eserstack/standards or .github/workflows/;
  • publishing configuration: exports, files, bin and optionalDependencies in a package.json, and the npm build scripts.

Generated Files and Versions

  • VERSION holds the shared version; eser codebase release bumps it and every package.json together.
  • Each package's package.json is its only manifest; nothing generates another one from it.
  • In each library's package.json, scripts.build, files and publishConfig.exports, and its tsconfig.build.json, are written by node ./etc/scripts/gen-library-manifests.ts; the precommit step library-manifests fails when they no longer match exports.
  • Lock files: pnpm-lock.yaml and go.sum.

Commits, Pushes and Releases

AGENTS.md here does not delegate task commits to agents, so the Parallel Task Agents flow of workflow-practices does not apply. An agent commits only when the user asks for that commit, with the configured git identity and a one- or two-line message. Pushes, tags and releases are the user's: an agent does not start, suggest or offer them.

Release Commands

eser codebase release, rerelease and unrelease commit, push to main and push tags. The v*.*.* tag push starts publishing to npm; JSR is frozen at 4.5.x (decision-5).

Package Layers

.github/ARCHITECTURE.md defines the layers a cross-package change follows, dependencies first: Layer 0 (@eserstack/standards and other foundations), then core utilities and infrastructure, then the framework, and the shipped binaries last (Layer 4: cli, noskills, laroux-server). All packages share one version, so a cross-package change needs no per-package bump.