@rse/ase 0.0.14 → 0.0.16

package/dst/ase.1

@@ -1,91 +0,0 @@
-.TH "ASE" "1" "April 2026" "" ""
-.SH "NAME"
-\fBase\fR - Agentic Software Engineering (ASE)
-.SH "SYNOPSIS"
-.P
-\fBase\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB-V\fR|\fB--version\fR\[rB] \[lB]\fB-l\fR|\fB--log-level\fR \fIlevel\fR\[rB] \[lB]\fB-L\fR|\fB--log-file\fR \fIfile\fR\[rB] \[lB]\fIcommand\fR \[lB]\fIoptions\fR \[lB]...\[rB]\[rB] \[lB]\fIargs\fR \[lB]...\[rB]\[rB]\[rB]
-.SH "DESCRIPTION"
-.P
-\fBase\fR, \fIAgentic Software Engineering (ASE)\fR, is the command-line companion tool to the \fIASE\fR Claude Code plugin. It provides project-level configuration management and a small per-project background HTTP service for dispatching commands.
-.SH "OPTIONS"
-.P
-The following top-level command-line options exist:
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show program usage information only.
-.IP \(bu 4
-\[lB]\fB-V\fR|\fB--version\fR\[rB]: Show program version information only.
-.IP \(bu 4
-\[lB]\fB-l\fR|\fB--log-level\fR \fIlevel\fR\[rB]: Set the logging verbosity. Supported \fIlevel\fR values are \fBerror\fR, \fBwarning\fR (default), \fBinfo\fR, and \fBdebug\fR.
-.IP \(bu 4
-\[lB]\fB-L\fR|\fB--log-file\fR \fIfile\fR\[rB]: Redirect log output to \fIfile\fR (appended). Use \fB-\fR (default) to write log messages to standard output. If \fIfile\fR is connected to a TTY, colors are used in the output.
-.RE 0
-
-.SH "COMMANDS"
-.P
-The following top-level commands exist for configuration handling:
-.RS 0
-.IP \(bu 4
-\fBase config\fR: Manage \fIASE\fR configuration stored in \fB.ase/config.yaml\fR. Without a subcommand, prints usage information. The file is validated against a schema: on read, unknown or invalid entries are warned about and silently dropped from the in-memory view; on set/write, they cause a fatal error. Recognized keys are grouped under three top-level sections: \fBproject.*\fR (project identity, classification, and artifact globs), \fBagent.*\fR (agent persona and process), and \fBtask.*\fR (currently \fBtask.id\fR, the active task identifier). All \fBase config\fR subcommands accept a \fB--scope\fR \fIscope\fR option that selects the scope chain. The \fIscope\fR value is a comma-separated list of scope terms, in any order; each term is one of \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, or \fBsession:\fR\fIid\fR (where \fIid\fR matches \fB\[lB]A-Za-z0-9._-\[rB]+\fR). At most one term per kind is allowed. The chain is canonicalized into the fixed inheritance order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR. \fBuser\fR is always implicitly added at the bottom of the chain. \fBproject\fR is implicitly added only when a \fIproject context\fR exists -- i.e. when the current working directory is inside a Git repository, or a \fB.ase\fR directory is found at or above it. Specifying \fBproject\fR explicitly without a project context is an error. Without an explicit \fB--scope\fR, the target defaults to \fBproject\fR when a project context exists, otherwise to \fBuser\fR. Reads cascade from the strongest (rightmost) scope down to the weakest and return the first value that is defined. Writes (\fBset\fR, \fBdelete\fR, \fBedit\fR, \fBinit\fR) are always confined to the strongest (target) scope's own file -- intermediate and weaker scopes are never modified. See \fIFILES\fR below for the resulting paths. Example: \fB--scope task:T1,session:S1\fR yields the chain \fBuser\fR -> \fBproject\fR -> \fBtask:T1\fR -> \fBsession:S1\fR, with \fBsession:S1\fR as the write target.
-.IP \(bu 4
-\fBase config init\fR \fItype\fR: Initialize \fB.ase/config.yaml\fR with preset values for all recognized keys. The \fItype\fR argument selects the preset: \fBvibe\fR (solo rookie: small black-box prototype, bare code, fully agent-driven, spec-driven, engineer ambition), \fBpro\fR (solo expert: medium white-box product, framework-based, human-controlled, code-driven, artist ambition), or \fBindustry\fR (team crew: large grey-box MVP, framework-based, human-in-the-loop, code-driven, craftsman ambition).
-.IP \(bu 4
-\fBase config edit\fR: Open \fB.ase/config.yaml\fR in the editor defined by the \fB$EDITOR\fR or \fB$VISUAL\fR environment variable (falling back to \fBvi\fR). The file and its parent directory are created if missing. After the editor exits, the file is re-read and schema warnings are reported.
-.IP \(bu 4
-\fBase config list\fR: List all effective configured values across the scope inheritance chain, rendered as a three-column table of \fBkey\fR, \fBvalue\fR, and \fBorigin\fR. The \fBorigin\fR column identifies the scope (\fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, or \fBsession:\fR\fIid\fR) that supplied each value. For overlapping keys only the value from the strongest scope is shown.
-.IP \(bu 4
-\fBase config get\fR \fIkey\fR: Print the value at the given dotted \fIkey\fR. Fails with an error if \fIkey\fR does not resolve to a leaf value.
-.IP \(bu 4
-\fBase config set\fR \fIkey\fR \fIvalue\fR: Set the value at the given dotted \fIkey\fR (creating intermediate maps as needed) and persist the file.
-.RE 0
-
-.P
-The following top-level commands exist for service management:
-.RS 0
-.IP \(bu 4
-\fBase service\fR: Manage the per-project background HTTP service. The service is bound to \fB127.0.0.1\fR on a port persisted in \fB.ase/service.yaml\fR and stops itself after 30 minutes of idle time. Without a subcommand, the help text is shown.
-.IP \(bu 4
-\fBase service start\fR: Start the background service (detached). Allocates a random port in the range \fB42000\fR..\fB44000\fR if none is persisted yet, writes it to \fB.ase/service.yaml\fR, and probes readiness. Exits silently with status 0 if the service is already running; prints \fBase: service: started on port <port>\fR on a fresh start.
-.IP \(bu 4
-\fBase service status\fR: Report whether the background service is running. Probes the persisted port via HTTP \fBGET /ping\fR and verifies that the responding service belongs to the current project. Prints \fBase: service: running on port <port>\fR and exits with status 0 if a matching service is reachable; otherwise prints a diagnostic message (no port configured, port not responding, or port in use by a foreign service) and exits with status 1.
-.IP \(bu 4
-\fBase service send\fR \fIcmd\fR: Dispatch the \fIcmd\fR token as a passthrough command to the running service via HTTP \fBPOST /command\fR; if the service is not running, it is auto-started first.
-.IP \(bu 4
-\fBase service stop\fR: Stop the background service via HTTP \fBGET /stop\fR. Exits silently with status 0 on successful stop. If no port is configured or the port is not responding, prints an informational message and exits with status 0.
-.RE 0
-
-.P
-The following top-level commands exist for \fIClaude Code\fR hook integration:
-.RS 0
-.IP \(bu 4
-\fBase hook\fR: Entry point group for \fIClaude Code\fR hook events. Without a subcommand, the help text is shown and the command exits with status 1.
-.IP \(bu 4
-\fBase hook session-start\fR: Handle the \fIClaude Code\fR \fBSessionStart\fR hook event. This subcommand is intended to be invoked by \fIClaude Code\fR internally as a configured hook handler only, not directly by end users.
-.RE 0
-
-.SH "CONFIGURATION FILES"
-.RS 0
-.IP \(bu 4
-\fBuser\fR: \fIper-user configuration directory\fR\fB/config.yaml\fR: Per-user \fIASE\fR configuration (scope \fBuser\fR). The per-user configuration directory is \fB~/Library/Application Support/ase\fR on macOS, \fB%APPDATA%\[rs]ase\fR on Windows, and \fB$XDG_CONFIG_HOME/ase\fR (falling back to \fB~/.config/ase\fR) on Linux and other Unix systems.
-.IP \(bu 4
-\fBproject\fR: \fB.ase/config.yaml\fR: Per-project \fIASE\fR configuration (scope \fBproject\fR). Read upward from the current working directory.
-.IP \(bu 4
-\fBtask\fR: \fB.ase/task/\fR\fIid\fR\fB/config.yaml\fR: Per-task \fIASE\fR configuration (scope \fBtask:\fR\fIid\fR), located relative to the Git top-level directory. Outside a Git repository, the file is placed relative to the current working directory.
-.IP \(bu 4
-\fBsession\fR: \fB~/.ase/session/\fR\fIid\fR\fB/config.yaml\fR: Per-session \fIASE\fR configuration (scope \fBsession:\fR\fIid\fR), located under the user's home directory (independent of any project context).
-.RE 0
-
-.SH "STATE FILES"
-.RS 0
-.IP \(bu 4
-\fB.ase/service.yaml\fR: Per-project service state.
-.IP \(bu 4
-\fB.ase/service.log\fR: Stdout/stderr log of the detached background service.
-.RE 0
-
-.SH "HISTORY"
-.P
-\fBase\fR was started to be developed in October 2025.
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR