@rse/ase 2.0.2 → 2.0.4

package/dst/man/ase-artifact.1

@@ -1,56 +0,0 @@
-.TH "ASE-ARTIFACT" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-artifact\fR - Resolve Project Artifact Kinds to File Lists
-.SH "SYNOPSIS"
-.P
-\fBase artifact\fR \[lB]\fB-h\fR|\fB--help\fR\[rB]
-.P
-\fBase artifact list\fR \[lB]\fB--kind\fR \fIkinds\fR\[rB]
-.P
-\fBase artifact name\fR \[lB]\fB--kind\fR \fIkind\fR\[rB] \fIfilename\fR
-.SH "DESCRIPTION"
-.P
-\fBase artifact\fR is the entry point group for resolving the \fIartifact kinds\fR of a project to project-relative file lists. The \fIASE\fR skills use it (and the MCP tools \fBase_artifact_list\fR and \fBase_artifact_name\fR, which provide the same) to locate the files of a kind. The recognized kinds are:
-.RS 0
-.IP \(bu 4
-\fBspec\fR: the specification (by default below \fBdocs/specbook\fR, the files \fB*.{md,txt,svg,png,jpg}\fR).
-.IP \(bu 4
-\fBcode\fR: the source code (by default below \fBsrc\fR, all files except \fB**/etc/**\fR and \fB**/{.gitignore,.npmignore,package.json}\fR).
-.IP \(bu 4
-\fBdocs\fR: the documentation (by default below \fBdoc\fR, all files plus \fB**/{README,LICENSE,CHANGELOG}.{md,txt}\fR, except \fB{spec,arch}/**\fR).
-.IP \(bu 4
-\fBinfr\fR: the infrastructure (by default below the project root, the files \fB**/{.github,.claude*,etc}/**\fR and \fB**/{AGENTS.md,{package,tsconfig*}.json,.{git,npm}ignore}\fR).
-.IP \(bu 4
-\fBothr\fR: the implicit catch-all of all other files.
-.RE 0
-.P
-The first four kinds are configured by the configuration keys \fBproject.artifact.\fR\fIkind\fR\fB.basedir\fR (the base directory, relative to the project root, where an empty value denotes the project root itself, and which must not escape the project root via \fB..\fR) and \fBproject.artifact.\fR\fIkind\fR\fB.files\fR (a \fIminiglob\fR specification, resolved relative to the base directory), with the defaults given above (see \fBase-config\fR(1)).
-.P
-A \fIminiglob\fR specification is a whitespace-separated list of glob patterns (in the syntax of \fIpicomatch\fR, with dot files matched), each optionally negated by a \fB!\fR prefix. The tokens are applied in order: the resulting set starts empty (or with all files, if the first token is negated), a plain pattern adds all files matching it, and a negated pattern removes all files matching it.
-.P
-The file universe is the set of all files below the project root (the Git top-level directory, else the current working directory), except the \fB.git\fR directories and all files excluded by the Git exclude rules: the global excludes file (\fBcore.excludesFile\fR, else \fB$XDG_CONFIG_HOME/git/ignore\fR, falling back to \fB~/.config/git/ignore\fR), the repository-local \fBinfo/exclude\fR, and the \fB.gitignore\fR files from the project root downwards, with the last matching rule winning.
-.P
-The universe is partitioned among the kinds by descending precedence \fBspec\fR, \fBcode\fR, \fBdocs\fR, and \fBinfr\fR: a file matched by multiple kinds belongs to the first one only, and every file matched by none of them belongs to \fBothr\fR.
-.P
-Without a sub-command, the usage information is shown and the command exits with status \fB1\fR.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.RE 0
-.SH "COMMANDS"
-.RS 0
-.IP \(bu 4
-\fBase artifact list\fR \[lB]\fB--kind\fR \fIkinds\fR\[rB]: Resolve one or more artifact kinds to project-relative file paths. See \fBase-artifact-list\fR(1).
-.IP \(bu 4
-\fBase artifact name\fR \[lB]\fB--kind\fR \fIkind\fR\[rB] \fIfilename\fR: Resolve a base-relative filename within an artifact kind to a project-relative path. See \fBase-artifact-name\fR(1).
-.RE 0
-.SH "EXIT STATUS"
-.P
-The group command without a sub-command exits with status \fB1\fR.
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-artifact-list\fR(1), \fBase-artifact-name\fR(1), \fBase-config\fR(1), \fBase-spec\fR(1), \fBgitignore\fR(5).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-delete.1

@@ -1,45 +0,0 @@
-.TH "ASE-CONFIG-DELETE" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-delete\fR - Delete a Configuration Value
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBdelete\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIkey\fR
-.SH "DESCRIPTION"
-.P
-\fBase config delete\fR deletes the configuration \fIkey\fR from the configuration file of the target scope (the strongest scope of the scope chain, by default \fBproject\fR inside a project, else \fBuser\fR) and writes the file back. Weaker scopes are never modified, so a value of the same key on a weaker scope (or the built-in default) becomes effective again.
-.P
-Deleting a key which is not set on the target scope is no error. As for \fBase config set\fR, a key which is not writable on the target scope cannot be deleted there either, and a target file which carries invalid content is not overwritten.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain, whose strongest scope is the target scope written by this command. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBdelete\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "ARGUMENTS"
-.RS 0
-.IP \(bu 4
-\fIkey\fR: The dotted configuration key, e.g., \fBagent.persona\fR, or any unambiguous trailing part of a known key, e.g., \fBpersona\fR.
-.RE 0
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR on a \fIkey\fR not writable on the target scope, an ambiguous \fIkey\fR, an invalid \fIscope\fR, or a target file carrying invalid content.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# fall back to the default persona again
-$ ase config delete agent.persona
-
-# remove the task store token of the user
-$ ase config --scope user delete project.task.store.token
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-set\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-edit.1

@@ -1,48 +0,0 @@
-.TH "ASE-CONFIG-EDIT" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-edit\fR - Edit the Configuration File with an Editor
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBedit\fR \[lB]\fB-h\fR|\fB--help\fR\[rB]
-.SH "DESCRIPTION"
-.P
-\fBase config edit\fR opens the configuration file of the target scope (the strongest scope of the scope chain, by default \fBproject\fR inside a project, else \fBuser\fR) in a text editor. The file and its parent directories are created if missing (a new \fBuser\fR scope file with file mode \fB0600\fR).
-.P
-After the editor exits, the file is re-read and strictly validated against the configuration schema. If it carries invalid YAML or invalid entries, the error is reported and the question \fBre-edit? \[lB]Y/n\[rB]\fR is asked on standard error: any answer other than \fBn\fR or \fBno\fR opens the editor again, while \fBn\fR or \fBno\fR lets the command fail (leaving the invalid file as is).
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain, whose strongest scope is the target scope whose file is edited. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBedit\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "ENVIRONMENT"
-.RS 0
-.IP \(bu 4
-\fBVISUAL\fR, \fBEDITOR\fR: The editor command, taken from the first non-empty one of \fBVISUAL\fR and \fBEDITOR\fR, falling back to \fBvi\fR. The value is split on whitespace into the command and its arguments (it is not run through a shell), and the file name is appended as the last argument.
-.RE 0
-.SH "FILES"
-.P
-The configuration file of the target scope: \fIper-user configuration directory\fR\fB/config.yaml\fR (\fBuser\fR), \fB.ase/config.yaml\fR (\fBproject\fR), \fB.ase/task/\fR\fIid\fR\fB/config.yaml\fR (\fBtask:\fR\fIid\fR), or \fIper-user state directory\fR\fB/session/\fR\fIid\fR\fB/config.yaml\fR (\fBsession:\fR\fIid\fR). See \fBase-config\fR(1).
-.SH "EXIT STATUS"
-.P
-\fB0\fR once the edited file is valid, \fB1\fR if the editor could not be run, or if the file stayed invalid and re-editing was declined.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# edit the project configuration with Vim
-$ EDITOR=vim ase config edit
-
-# edit the user configuration
-$ ase config --scope user edit
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-set\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-get.1

@@ -1,46 +0,0 @@
-.TH "ASE-CONFIG-GET" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-get\fR - Print a Configuration Value
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBget\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIkey\fR
-.SH "DESCRIPTION"
-.P
-\fBase config get\fR prints the effective value of the configuration \fIkey\fR, followed by a newline, on standard output. The value is looked up from the strongest scope of the scope chain down to the built-in \fBdefault\fR scope, and the first defined value wins. In contrast to \fBase
-config list\fR, secret values are printed unmasked.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain whose values are cascaded. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBget\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "ARGUMENTS"
-.RS 0
-.IP \(bu 4
-\fIkey\fR: The dotted configuration key, e.g., \fBagent.persona\fR, or any unambiguous trailing part of a known key, e.g., \fBpersona\fR. See \fBase-config\fR(1) for all keys.
-.RE 0
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR if \fIkey\fR is not set on any scope, if \fIkey\fR does not address a leaf value (e.g., \fBproject.task\fR), if \fIkey\fR is ambiguous, or on an invalid \fIscope\fR.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# print the effective task lifecycle model
-$ ase config get project.task.lifecycle
-solo
-
-# print the user-level persona via its abbreviated key
-$ ase config --scope user get persona
-engineer
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-list\fR(1), \fBase-config-set\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-init.1

@@ -1,60 +0,0 @@
-.TH "ASE-CONFIG-INIT" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-init\fR - Initialize Configuration with Preset Values
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBinit\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fItype\fR
-.SH "DESCRIPTION"
-.P
-\fBase config init\fR initializes the configuration file of the target scope (the strongest scope of the scope chain, by default \fBproject\fR inside a project, else \fBuser\fR) with the preset values of \fItype\fR. The file (and its parent directories) are created if missing. Already existing keys of the file which the preset does not cover are kept, while those covered by the preset are overwritten.
-.P
-Keys of the preset which are not writable on the target scope (e.g., all \fBproject.task.*\fR, \fBproject.artifact.*\fR, and \fBboard.*\fR keys on a \fBtask\fR or \fBsession\fR scope, or \fBtelemetry.prices.ai\fR on the \fBproject\fR scope) are silently skipped. The file is written under an advisory file lock and atomically.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain, whose strongest scope is the target scope written by this command. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBinit\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "ARGUMENTS"
-.RS 0
-.IP \(bu 4
-\fItype\fR: The preset to apply, one of:
-.RS 4
-.IP \(bu 4
-\fBdefault\fR: The complete baseline of the built-in \fBdefault\fR scope: \fBagent.persona\fR \fBengineer\fR, \fBagent.guidance\fR \fBnormal\fR, \fBproject.name\fR \fBExample Project\fR, \fBproject.boxing\fR \fBwhite\fR, \fBproject.task.lifecycle\fR \fBsolo\fR, \fBproject.task.idscheme\fR \fBslug\fR, \fBproject.task.store.url\fR \fBase:./.ase/task\fR, \fBproject.task.default.source\fR \fBworktree\fR, \fBproject.task.default.changeset\fR \fBworktree\fR, \fBproject.task.default.target\fR \fBsource\fR, \fBproject.task.effort.scale\fR \fB15,60,240,960\fR, \fBproject.task.effort.factor\fR \fB1\fR, \fBproject.task.effort.file\fR \fB1\fR, \fBproject.task.effort.line\fR \fB0.025\fR, \fBproject.task.effort.iteration\fR \fB2.5\fR, the full set of \fBproject.artifact.*\fR globs, the \fBboard.tui.color.*\fR, \fBboard.web.color.*\fR, and \fBboard.web.editor.keymap\fR defaults, and \fBtelemetry.enabled\fR \fBfalse\fR, \fBtelemetry.prices.ai\fR \fB*=4.00/20.00/0.20/5.00\fR, and \fBtelemetry.prices.hr\fR \fB*=110\fR.
-.IP \(bu 4
-\fBvibe\fR: \fBagent.persona\fR \fBwriter\fR, \fBproject.name\fR \fBExample Project\fR, and \fBproject.boxing\fR \fBblack\fR.
-.IP \(bu 4
-\fBpro\fR: \fBagent.persona\fR \fBengineer\fR, \fBproject.name\fR \fBExample Project\fR, and \fBproject.boxing\fR \fBwhite\fR.
-.IP \(bu 4
-\fBindustry\fR: \fBagent.persona\fR \fBengineer\fR, \fBproject.name\fR \fBExample Project\fR, and \fBproject.boxing\fR \fBgrey\fR.
-.RE 0
-.IP "" 4
-Any other \fItype\fR is an error.
-.RE 0
-.SH "FILES"
-.P
-The configuration file of the target scope: \fIper-user configuration directory\fR\fB/config.yaml\fR (\fBuser\fR), \fB.ase/config.yaml\fR (\fBproject\fR), \fB.ase/task/\fR\fIid\fR\fB/config.yaml\fR (\fBtask:\fR\fIid\fR), or \fIper-user state directory\fR\fB/session/\fR\fIid\fR\fB/config.yaml\fR (\fBsession:\fR\fIid\fR). See \fBase-config\fR(1).
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR on an unknown \fItype\fR, an invalid \fIscope\fR, or a target file carrying invalid content.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# initialize the project configuration for an industrial project
-$ ase config init industry
-
-# write the entire baseline into the user configuration
-$ ase config --scope user init default
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-list\fR(1), \fBase-config-set\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-list.1

@@ -1,42 +0,0 @@
-.TH "ASE-CONFIG-LIST" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-list\fR - List the Effective Configuration
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBlist\fR \[lB]\fB-h\fR|\fB--help\fR\[rB]
-.SH "DESCRIPTION"
-.P
-\fBase config list\fR lists all configuration keys known to the configuration schema, plus all further leaf keys found in the files of the scope chain, with their effective values, rendered as a table with the three columns \fBKEY\fR, \fBVALUE\fR, and \fBSCOPE\fR, sorted by key.
-.P
-The \fBSCOPE\fR column names the scope which supplied the value: \fBdefault\fR (the built-in defaults), \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, or \fBsession:\fR\fIid\fR. For a key set on multiple scopes, only the value of the strongest scope is shown. A key which is not set on any scope is shown with an empty \fBVALUE\fR and the \fBSCOPE\fR \fB-\fR. The values of the secret keys \fBproject.task.store.token\fR, \fBproject.relay.token\fR, and \fBtelemetry.service.token\fR are masked as \fB***\fR.
-.P
-Invalid entries of the configuration files are warned about and skipped.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain whose values are cascaded. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBlist\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR on an invalid \fIscope\fR.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# list the effective project configuration
-$ ase config list
-
-# list the configuration as seen by a particular task
-$ ase config --scope task:json-export list
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-get\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config-set.1

@@ -1,52 +0,0 @@
-.TH "ASE-CONFIG-SET" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config-set\fR - Set a Configuration Value
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBset\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIkey\fR \fIvalue\fR
-.SH "DESCRIPTION"
-.P
-\fBase config set\fR sets the configuration \fIkey\fR to \fIvalue\fR in the configuration file of the target scope (the strongest scope of the scope chain, by default \fBproject\fR inside a project, else \fBuser\fR), creating the file, its parent directories, and the intermediate maps of the dotted key as needed. Weaker and intermediate scopes are never modified.
-.P
-The \fIvalue\fR is validated against the configuration schema before the file is written, and an invalid value is an error. Some keys are writable on particular scopes only (e.g., \fBproject.task.*\fR on \fBuser\fR and \fBproject\fR, the token keys on \fBuser\fR): setting such a key on any other scope is an error naming the permitted scopes. See \fBase-config\fR(1) for all keys, their values, and their scopes. A target file which already carries invalid content is not overwritten, as this content would be lost.
-.P
-The file is written under an advisory file lock and atomically, with file mode \fB0600\fR for the \fBuser\fR scope and for any file carrying a secret key.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain, whose strongest scope is the target scope written by this command. As an option of \fBase config\fR, it has to be given \fIbefore\fR \fBset\fR. The \fIscope\fR value is a comma-separated list of the terms \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, and \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR), at most one per kind and in any order, canonicalized into the order \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR.
-.sp
-\fBuser\fR is always added implicitly, and \fBproject\fR is added implicitly whenever a project context (a Git working tree or a \fB.ase\fR directory at or above the current directory) exists, but never above the strongest explicitly requested term, so an explicit \fB--scope user\fR is never silently retargeted to \fBproject\fR. An explicit \fBproject\fR without a project context is an error. Default: \fBproject\fR inside a project context, else \fBuser\fR. See \fBase-config\fR(1) for details.
-.RE 0
-.SH "ARGUMENTS"
-.RS 0
-.IP \(bu 4
-\fIkey\fR: The dotted configuration key, e.g., \fBagent.persona\fR, or any unambiguous trailing part of a known key, e.g., \fBpersona\fR.
-.IP \(bu 4
-\fIvalue\fR: The value to set, stored as a string (e.g., \fBtrue\fR for \fBtelemetry.enabled\fR or \fB44318\fR for \fBtelemetry.service.port\fR).
-.RE 0
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR on an invalid \fIvalue\fR, a \fIkey\fR not writable on the target scope, an ambiguous \fIkey\fR, an intermediate path of \fIkey\fR which is not a map, an invalid \fIscope\fR, or a target file carrying invalid content.
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# switch the project to the enterprise task lifecycle model
-$ ase config set project.task.lifecycle enterprise
-
-# enable the AI usage accounting for the current user
-$ ase config --scope user set telemetry.enabled true
-
-# set the persona for a single session only
-$ ase config --scope session:4711 set agent.persona caveman
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config\fR(1), \fBase-config-get\fR(1), \fBase-config-delete\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-config.1

@@ -1,231 +0,0 @@
-.TH "ASE-CONFIG" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-config\fR - Manage the Layered ASE Configuration
-.SH "SYNOPSIS"
-.P
-\fBase config\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB--scope\fR \fIscope\fR\[rB] \fIcommand\fR \[lB]\fIargs\fR \[lB]...\[rB]\[rB]
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBinit\fR \fItype\fR
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBlist\fR
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBedit\fR
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBget\fR \fIkey\fR
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBset\fR \fIkey\fR \fIvalue\fR
-.P
-\fBase config\fR \[lB]\fB--scope\fR \fIscope\fR\[rB] \fBdelete\fR \fIkey\fR
-.SH "DESCRIPTION"
-.P
-\fBase config\fR manages the layered \fIASE\fR configuration, a stack of \fBconfig.yaml\fR files of the \fIscopes\fR \fBuser\fR < \fBproject\fR < \fBtask:\fR\fIid\fR < \fBsession:\fR\fIid\fR, on top of a built-in \fBdefault\fR scope carrying the default values. Reads cascade from the strongest scope down to the weakest one and return the first defined value, while writes are always confined to the file of the strongest scope of the chain (the \fItarget\fR scope).
-.P
-All files are validated against the configuration schema: on read, unknown or invalid entries are warned about and dropped from the in-memory view, while on set, delete, and write they lead to a fatal error. A target file still carrying invalid content is never overwritten, as the skipped content would otherwise be lost: repair it first (e.g. via \fBase config edit\fR).
-.P
-Obsolete (pre-1.1.0) entries \fBproject.artifact.task.{basedir,files}\fR and \fBagent.{task,skill}\fR are migrated in place on reading: a \fBbasedir\fR becomes \fBproject.task.store.url\fR (as \fBase:\fR\fIbasedir\fR) unless the latter is already set, and the other entries are dropped.
-.P
-A \fIkey\fR is a dotted path like \fBagent.persona\fR. Any unambiguous trailing part of a known key is accepted, too, e.g., \fBpersona\fR for \fBagent.persona\fR or \fBstore.url\fR for \fBproject.task.store.url\fR, while an ambiguous one (like \fBcolor.dim\fR) is an error.
-.P
-Without a \fIcommand\fR, the usage information is shown and the command exits with status \fB1\fR.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB--scope\fR \fIscope\fR\[rB]: Select the scope chain. This option belongs to \fBase config\fR itself and hence has to be given \fIbefore\fR the \fIcommand\fR, e.g., \fBase config --scope user set agent.persona writer\fR.
-.sp
-The \fIscope\fR value is a comma-separated list of scope terms, in any order, where each term is one of \fBuser\fR, \fBproject\fR, \fBtask:\fR\fIid\fR, or \fBsession:\fR\fIid\fR (with \fIid\fR matching \fB\[lB]A-Za-z0-9._-\[rB]+\fR, but neither \fB.\fR nor \fB..\fR). At most one term per kind is allowed. The chain is canonicalized into the fixed inheritance order \fBdefault\fR < \fBuser\fR < \fBproject\fR < \fBtask\fR < \fBsession\fR:
-.RS 4
-.IP \(bu 4
-\fBuser\fR is always implicitly added at the bottom of the chain.
-.IP \(bu 4
-\fBproject\fR is implicitly added only when a \fIproject context\fR exists, i.e., when the current working directory is inside a Git working tree or a \fB.ase\fR directory exists at or above it (except in the home directory), and only as long as it stays weaker than the strongest explicitly requested term, so an explicit \fB--scope
-user\fR is never silently retargeted to \fBproject\fR.
-.IP \(bu 4
-Specifying \fBproject\fR explicitly without a project context is an error.
-.RE 0
-.IP "" 4
-Without \fB--scope\fR, the chain is \fBproject\fR (with \fBuser\fR below it) when a project context exists, otherwise \fBuser\fR only. Example: \fB--scope
-task:T1,session:S1\fR yields the chain \fBdefault\fR -> \fBuser\fR -> \fBproject\fR -> \fBtask:T1\fR -> \fBsession:S1\fR with \fBsession:S1\fR as the target scope.
-.RE 0
-.SH "COMMANDS"
-.RS 0
-.IP \(bu 4
-\fBinit\fR \fItype\fR: Initialize the target scope with the preset values of \fItype\fR (\fBdefault\fR, \fBvibe\fR, \fBpro\fR, or \fBindustry\fR). See \fBase-config-init\fR(1).
-.IP \(bu 4
-\fBlist\fR: List all configuration keys with their effective values and the scopes supplying them. See \fBase-config-list\fR(1).
-.IP \(bu 4
-\fBedit\fR: Edit the configuration file of the target scope with the text editor. See \fBase-config-edit\fR(1).
-.IP \(bu 4
-\fBget\fR \fIkey\fR: Print the effective value of \fIkey\fR. See \fBase-config-get\fR(1).
-.IP \(bu 4
-\fBset\fR \fIkey\fR \fIvalue\fR: Set \fIkey\fR to \fIvalue\fR on the target scope. See \fBase-config-set\fR(1).
-.IP \(bu 4
-\fBdelete\fR \fIkey\fR: Delete \fIkey\fR from the target scope. See \fBase-config-delete\fR(1).
-.RE 0
-.SH "CONFIGURATION KEYS"
-.P
-The following keys are recognized. Every key is restricted to the listed values (where \fIstring\fR means any non-empty string) and is writable on all scopes \fBuser\fR, \fBproject\fR, \fBtask\fR, and \fBsession\fR, unless stated otherwise. A default stems from the built-in \fBdefault\fR scope (shown by \fBase config list\fR with scope \fBdefault\fR) or, where stated, from the code using the key.
-.P
-Project identity and classification:
-.RS 0
-.IP \(bu 4
-\fBproject.id\fR (\fIstring\fR): The unique id of the project. Default: the sanitized basename of the project root (with all characters other than \fBA-Z\fR, \fBa-z\fR, \fB0-9\fR, \fB_\fR, and \fB-\fR replaced by \fB_\fR), or \fIbasedir\fR\fB-\fR\fIworktree\fR if the project root is a worktree \fIbasedir\fR\fB/\fR\fIworktree\fR next to an \fBactive\fR symbolic link in \fIbasedir\fR. An explicit id is required for a remote task store and for the agent relay.
-.IP \(bu 4
-\fBproject.name\fR (\fIstring\fR): The full name of the project (default: \fBExample Project\fR).
-.IP \(bu 4
-\fBproject.boxing\fR (\fBwhite\fR, \fBgrey\fR, or \fBblack\fR): Whether the project artifacts are treated as a white box (fully transparent and understood), grey box (partially), or black box (not at all), which modulates the work depth and output visibility of the skills (default: \fBwhite\fR).
-.IP \(bu 4
-\fBproject.users\fR (\fIstring\fR, \fBuser\fR and \fBproject\fR scopes only): The comma-separated list of the known human assignees of the tasks (default: empty). If not empty, an assignment to anybody else than \fBnone\fR, the current user, one of these users, or an agent present at the agent relay is warned about (see \fBase-task-assign\fR(1)), and the assign popup of the task boards suggests these users (else the current user) besides the agents (see \fBase-task-board\fR(1)).
-.RE 0
-.P
-Task plans (all writable on the \fBuser\fR and \fBproject\fR scopes only, \fBproject.task.store.token\fR on the \fBuser\fR scope only):
-.RS 0
-.IP \(bu 4
-\fBproject.task.lifecycle\fR (\fBsolo\fR, \fBteam\fR, or \fBenterprise\fR): The task lifecycle model: single-phase for a local solo developer, two-phase for a small team, or four-phase for a gated enterprise pipeline (default: \fBsolo\fR). See \fBase-task-lifecycle\fR(1).
-.IP \(bu 4
-\fBproject.task.idscheme\fR (\fBslug\fR\[lB]\fB:\fR\fIwords\fR\[rB], \fBseq\fR\[lB]\fB:\fR\fItemplate\fR\[rB], or \fBany\fR): The task id scheme (default: \fBslug\fR). See \fBase-task-idscheme\fR(1) and \fBase-task-newid\fR(1).
-.IP \(bu 4
-\fBproject.task.store.url\fR (\fIstring\fR): The URL of the task store: \fBase:\fR\fIpath\fR (local, default \fBase:./.ase/task\fR), \fBase://\fR\fIaddr\fR\fB:\fR\fIport\fR\[lB]\fB/\fR\fItoken\fR\[rB] resp. \fBases://\fR\fIaddr\fR\fB:\fR\fIport\fR\[lB]\fB/\fR\fItoken\fR\[rB]\[lB]\fB?insecure\fR\[rB] (remote task store server), \fBgithub:\fR\fIowner\fR\fB/\fR\fIrepo\fR (and \fBgithub+http\fR\[lB]\fBs\fR\[rB]\fB://\fR\fIhost\fR\fB/\fR\fIowner\fR\fB/\fR\fIrepo\fR), \fBgitlab:\fR\fInamespace\fR\fB/\fR\fIproject\fR (and \fBgitlab://\fR\fIhost\fR\fB/\fR..., \fBgitlab+http\fR\[lB]\fBs\fR\[rB]\fB://\fR\fIhost\fR\fB/\fR...), or \fBgitea+http\fR\[lB]\fBs\fR\[rB]\fB://\fR\fIhost\fR\fB/\fR\fIowner\fR\fB/\fR\fIrepo\fR. See \fBase-task\fR(1).
-.IP \(bu 4
-\fBproject.task.store.token\fR (\fIstring\fR, \fBuser\fR scope only): The bearer token of a remote task store, resp. the token of a GitHub, GitLab, or Gitea task store. Masked as \fB***\fR by \fBase config list\fR.
-.IP \(bu 4
-\fBproject.task.store.crt\fR, \fBproject.task.store.key\fR (\fIstring\fR): The PEM certificate (chain) and private key files of the task store server, relative to the directory of the configuration file defining them. See \fBase-task-store\fR(1).
-.IP \(bu 4
-\fBproject.task.default.source\fR (\fBworktree\fR or \fBbranch:\fR\fIname\fR): The default of the \fBSource:\fR key of the task plans (default: \fBworktree\fR).
-.IP \(bu 4
-\fBproject.task.default.changeset\fR (\fBworktree\fR, \fBbranch:\fR\fIname\fR, or \fBattachment:\fR\fIname\fR): The default of the \fBChangeset:\fR key of the task plans (default: \fBworktree\fR).
-.IP \(bu 4
-\fBproject.task.default.target\fR (\fBworktree\fR, \fBbranch:\fR\fIname\fR, or \fBsource\fR): The default of the \fBTarget:\fR key of the task plans (default: \fBsource\fR).
-.sp
-A branch \fIname\fR has to start with a letter, digit, or \fB_\fR, consist of letters, digits, \fB_\fR, \fB.\fR, \fB/\fR, and \fB-\fR, must not end in \fB/\fR, \fB.\fR, or \fB.lock\fR, and must not contain \fB..\fR or \fB//\fR. An attachment \fIname\fR consists of letters, digits, \fB_\fR, and \fB-\fR. A branch or attachment \fIname\fR can carry the placeholder \fB{id}\fR, which reads as the id of the task (with every character other than letters, digits, \fB_\fR, and \fB-\fR replaced by \fB-\fR, runs of \fB-\fR reduced to one, and leading and trailing \fB-\fR and \fB_\fR removed, e.g., \fB12\fR for \fB#12\fR and \fBFOO-12\fR for \fBFOO#12\fR), e.g., \fBbranch:cs-{id}\fR for a separate changeset branch per task.
-.IP \(bu 4
-\fBproject.task.effort.scale\fR (\fIxs\fR\fB,\fR\fIs\fR\fB,\fR\fIm\fR\fB,\fR\fIl\fR): The upper bounds of the effort size bands \fBXS\fR, \fBS\fR, \fBM\fR, and \fBL\fR of the \fBEffort:\fR key of the task plans, in strictly ascending human minutes, while \fBXL\fR is open-ended (default: \fB15,60,240,960\fR). The task boards sum the efforts via the band midpoints, counting \fBXL\fR as twice the \fBL\fR bound.
-.IP \(bu 4
-\fBproject.task.effort.factor\fR (\fInumber\fR): The human minutes per point of the \fIattention score\fR of the effort estimation, i.e., of the weighted requirements, behaviors, and changes stated by the checklist items of a plan (default: \fB1\fR). Fitted and stored by \fB/ase-task-estimate --calibrate --save\fR.
-.IP \(bu 4
-\fBproject.task.effort.file\fR, \fBproject.task.effort.line\fR (\fInumber\fR): The additional human minutes per touched file resp. per predicted changed line of the \fIvolume score\fR of the effort estimation, where the line minutes also cover the edge cases and polishing no plan describes, and a newly written line weighs three times a changed one (defaults: \fB1\fR resp. \fB0.025\fR). Fitted and stored by \fB/ase-task-estimate --calibrate --save\fR.
-.IP \(bu 4
-\fBproject.task.effort.iteration\fR (\fInumber\fR): The multiplier of the estimated minutes of a task whose main deliverable is an interactive or visual user interface, covering its many rounds of post-adjustment, at least \fB1\fR (default: \fB2.5\fR). Not fitted by the calibration.
-.RE 0
-.P
-Agent relay (all writable on the \fBuser\fR and \fBproject\fR scopes only, \fBproject.relay.token\fR on the \fBuser\fR scope only):
-.RS 0
-.IP \(bu 4
-\fBproject.relay.url\fR (\fIstring\fR): The URL of the agent relay, as \fBase://\fR\fIaddr\fR\fB:\fR\fIport\fR\[lB]\fB/\fR\fItoken\fR\[rB] or \fBases://\fR\fIaddr\fR\fB:\fR\fIport\fR\[lB]\fB/\fR\fItoken\fR\[rB]\[lB]\fB?insecure\fR\[rB] (default: none). See \fBase-agent-relay\fR(1).
-.IP \(bu 4
-\fBproject.relay.token\fR (\fIstring\fR, \fBuser\fR scope only): The bearer token of the agent relay. Masked as \fB***\fR by \fBase config
-list\fR.
-.IP \(bu 4
-\fBproject.relay.crt\fR, \fBproject.relay.key\fR (\fIstring\fR): The PEM certificate (chain) and private key files of the agent relay server, relative to the directory of the configuration file defining them.
-.RE 0
-.P
-Per-project service:
-.RS 0
-.IP \(bu 4
-\fBproject.service.port\fR (\fIport\fR \fB1024\fR..\fB65535\fR, \fBproject\fR scope only): The preferred port of the per-project background service on \fB127.0.0.1\fR, falling back to a random port out of the range \fB42000\fR..\fB44000\fR if unavailable (default: none). See \fBase-service-start\fR(1).
-.RE 0
-.P
-Project artifacts (all writable on the \fBuser\fR and \fBproject\fR scopes only), each kind defined by a \fBbasedir\fR directory (relative to the project root, empty for the root itself) and a whitespace-separated \fBfiles\fR glob specification (relative to \fBbasedir\fR, with \fB!\fR negating a glob). See \fBase-artifact\fR(1):
-.RS 0
-.IP \(bu 4
-\fBproject.artifact.spec.basedir\fR, \fBproject.artifact.spec.files\fR: The specification files (default: \fBdocs/specbook\fR and \fB*.{md,txt,svg,png,jpg}\fR).
-.IP \(bu 4
-\fBproject.artifact.spec.schema\fR (\fIstring\fR): The whitespace-separated list of \fISpecBook\fR schema configuration files, where \fBstd\fR names the bundled standard one and every other entry is a file relative to the project root (default: empty, i.e., \fBstd\fR). See \fBase-spec\fR(1).
-.IP \(bu 4
-\fBproject.artifact.code.basedir\fR, \fBproject.artifact.code.files\fR: The source code files (default: \fBsrc\fR and \fB** !**/etc/**
-!**/{.gitignore,.npmignore,package.json}\fR).
-.IP \(bu 4
-\fBproject.artifact.docs.basedir\fR, \fBproject.artifact.docs.files\fR: The documentation files (default: \fBdoc\fR and \fB**
-**/{README,LICENSE,CHANGELOG}.{md,txt} !{spec,arch}/**\fR).
-.IP \(bu 4
-\fBproject.artifact.infr.basedir\fR, \fBproject.artifact.infr.files\fR: The infrastructure files (default: empty and \fB**/{.github,.claude*,etc}/**
-**/{AGENTS.md,{package,tsconfig*}.json,.{git,npm}ignore}\fR).
-.RE 0
-.P
-Agent:
-.RS 0
-.IP \(bu 4
-\fBagent.persona\fR (\fBwriter\fR, \fBengineer\fR, \fBjournalist\fR, \fBtelegrapher\fR, or \fBcaveman\fR): The communication style of the AI agent (default: \fBengineer\fR).
-.IP \(bu 4
-\fBagent.guidance\fR (\fBnone\fR, \fBminimal\fR, \fBnormal\fR, or \fBverbose\fR): The amount of unsolicited help hints of the AI agent (default: \fBnormal\fR).
-.RE 0
-.P
-AI usage accounting (see \fBase-task-assign\fR(1) and \fBase-setup-telemetry\fR(1)):
-.RS 0
-.IP \(bu 4
-\fBtelemetry.enabled\fR (\fBtrue\fR or \fBfalse\fR, \fBuser\fR and \fBproject\fR scopes only): Whether the AI usage accounting is enabled as a whole (default: \fBfalse\fR).
-.IP \(bu 4
-\fBtelemetry.implicit\fR (\fBtrue\fR or \fBfalse\fR, \fBuser\fR and \fBproject\fR scopes only): Whether the usage of an interactive session is also accounted onto its active task while the task is \fIunassigned\fR, i.e., without assigning it to oneself (default: \fBtrue\fR, never for task \fBdefault\fR).
-.IP \(bu 4
-\fBtelemetry.service.port\fR (\fIport\fR \fB1024\fR..\fB65535\fR, \fBuser\fR scope only): The port of the per-user OTLP ingress on \fB127.0.0.1\fR (default: \fB44318\fR).
-.IP \(bu 4
-\fBtelemetry.service.token\fR (\fIstring\fR, \fBuser\fR scope only): The bearer token of the OTLP ingress, generated by \fBase setup
-telemetry activate\fR. Masked as \fB***\fR by \fBase config list\fR.
-.IP \(bu 4
-\fBtelemetry.service.interval\fR (\fIminutes\fR, \fBuser\fR and \fBproject\fR scopes only): The interval of the interim bookings of the open usage windows (default: \fB10\fR, \fB0\fR disables).
-.IP \(bu 4
-\fBtelemetry.service.idle\fR (\fIminutes\fR, \fBuser\fR and \fBproject\fR scopes only): The idle time after which a usage window pauses (default: \fB30\fR, \fB0\fR disables).
-.IP \(bu 4
-\fBtelemetry.prices.ai\fR (\fItable\fR, \fBuser\fR scope only): The price table \fImodel\fR\fB=\fR\fIinput\fR\fB/\fR\fIoutput\fR\[lB]\fB/\fR\fIcread\fR\fB/\fR\fIcwrite\fR\[rB] \[lB]...\[rB] (whitespace-separated) in USD per million input, output, cache read, and cache write tokens (the cache prices defaulting to the input price), keyed by the model or the tool name, with \fB*\fR for all others (default: \fB*=4.00/20.00/0.20/5.00\fR).
-.IP \(bu 4
-\fBtelemetry.prices.hr\fR (\fItable\fR, \fBuser\fR and \fBproject\fR scopes only): The hourly rate table \fIuser-id\fR\fB=\fR\fIusd-per-hour\fR\[lB]\fB,\fR...\[rB] of the human time, keyed by the assignee, with \fB*\fR for all others (default: \fB*=110\fR).
-.RE 0
-.P
-Task board (all writable on the \fBuser\fR and \fBproject\fR scopes only, see \fBase-task-board\fR(1)):
-.RS 0
-.IP \(bu 4
-\fBboard.tui.color.dim\fR, \fBboard.tui.color.normal\fR, \fBboard.tui.color.accent\fR, \fBboard.tui.color.signal\fR: The colors of the four color roles of the terminal board (defaults: \fBgrey\fR, \fBdefault\fR, \fBblue\fR, and \fBred\fR), each either \fBdefault\fR (the foreground color of the terminal), a color name (like \fBblue\fR or \fBblueBright\fR), \fB#rgb\fR, \fB#rrggbb\fR, \fBansi256(\fR\fIn\fR\fB)\fR, or \fBrgb(\fR\fIr\fR\fB,\fR\fIg\fR\fB,\fR\fIb\fR\fB)\fR.
-.IP \(bu 4
-\fBboard.web.color.dim\fR, \fBboard.web.color.normal\fR, \fBboard.web.color.accent\fR, \fBboard.web.color.signal\fR: The base colors of the four color roles of the web board (defaults: \fBgrey\fR, \fBblack\fR, \fBblue\fR, and \fBorange\fR), each either \fBdefault\fR, a color name (\fBblack\fR, \fBgrey\fR, \fBgray\fR, \fBbrown\fR, \fBred\fR, \fBorange\fR, \fByellow\fR, \fBgreen\fR, \fBteal\fR, \fBcyan\fR, \fBblue\fR, \fBpurple\fR, or \fBmagenta\fR), \fB#rgb\fR, or \fB#rrggbb\fR. Each base color is expanded into a spread of 64 colors over the entire lightness range, out of which the web board takes all its colors.
-.IP \(bu 4
-\fBboard.web.editor.keymap\fR (\fBdefault\fR, \fBvim\fR, or \fBemacs\fR): The key bindings of the task plan editor of the web board (default: \fBdefault\fR).
-.RE 0
-.SH "ENVIRONMENT"
-.RS 0
-.IP \(bu 4
-\fBEDITOR\fR, \fBVISUAL\fR: The text editor of \fBase config edit\fR.
-.IP \(bu 4
-\fBXDG_CONFIG_HOME\fR, \fBXDG_STATE_HOME\fR, \fBAPPDATA\fR, \fBLOCALAPPDATA\fR: The base directories of the \fIper-user configuration directory\fR and the \fIper-user state directory\fR (see \fBFILES\fR).
-.RE 0
-.SH "FILES"
-.RS 0
-.IP \(bu 4
-\fIper-user configuration directory\fR\fB/config.yaml\fR: The configuration of scope \fBuser\fR (with file mode \fB0600\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) elsewhere.
-.IP \(bu 4
-\fB.ase/config.yaml\fR: The configuration of scope \fBproject\fR, searched upward from the current working directory up to the project root, else located in the project root.
-.IP \(bu 4
-\fB.ase/task/\fR\fIid\fR\fB/config.yaml\fR: The configuration of scope \fBtask:\fR\fIid\fR, located in the project root (or the current working directory outside of a project).
-.IP \(bu 4
-\fIper-user state directory\fR\fB/session/\fR\fIid\fR\fB/config.yaml\fR: The configuration of scope \fBsession:\fR\fIid\fR, independent of any project. The per-user state directory is \fB~/Library/Application
-Support/ase\fR on macOS, \fB%LOCALAPPDATA%\[rs]ase\fR on Windows, and \fB$XDG_STATE_HOME/ase\fR (falling back to \fB~/.local/state/ase\fR) elsewhere.
-.RE 0
-.P
-Every write happens under an advisory file lock and atomically. A file carrying a secret key (a token) is written with file mode \fB0600\fR.
-.SH "EXIT STATUS"
-.P
-\fB0\fR on success, \fB1\fR on any error (including a missing \fIcommand\fR).
-.SH "EXAMPLES"
-.P
-.RS 2
-.nf
-# initialize the project configuration with the "industry" preset
-$ ase config init industry
-
-# show the effective configuration
-$ ase config list
-
-# set the persona of the agent on the user scope
-$ ase config --scope user set agent.persona telegrapher
-
-# read a value by an abbreviated key
-$ ase config get persona
-.fi
-.RE
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-config-init\fR(1), \fBase-config-list\fR(1), \fBase-config-edit\fR(1), \fBase-config-get\fR(1), \fBase-config-set\fR(1), \fBase-config-delete\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-hook-permission-request.1

@@ -1,36 +0,0 @@
-.TH "ASE-HOOK-PERMISSION-REQUEST" "1" "October 2026" "2.0.2" "Agentic Software Engineering (ASE)"
-.SH "NAME"
-\fBase-hook-permission-request\fR - Handle the PermissionRequest Hook Event
-.SH "SYNOPSIS"
-.P
-\fBase hook permission-request\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB-t\fR|\fB--tool\fR \fItool\fR\[rB]
-.SH "DESCRIPTION"
-.P
-\fBase hook permission-request\fR handles the \fBPermissionRequest\fR hook event of \fIOpenAI Codex CLI\fR, which the agent tool fires only when a tool invocation would otherwise require an interactive user approval. It is intended to be invoked by the agent tool internally as a configured hook handler only, and not directly by end users. It is configured for \fB--tool codex\fR only, as \fIOpenAI Codex CLI\fR does not honor an approval in its \fBPreToolUse\fR event.
-.P
-The handler reads the event payload from standard input, a JSON object with the tool name (field \fBtool_name\fR), the tool input (field \fBtool_input\fR), and the session id (field \fBsession_id\fR), and applies the very same auto-approval rules as \fBase hook pre-tool-use\fR (see \fBase-hook-pre-tool-use\fR(1)): \fIASE\fR CLI invocations, \fIASE\fR skills, \fIASE\fR MCP tools, tools of the pre-defined foreign MCP servers, reads of plugin files, and edits during an active edit-capable skill.
-.P
-On approval, the handler writes the decision \fB{"hookSpecificOutput":{"hookEventName":"PermissionRequest","decision":{"behavior":"allow"}}}\fR to standard output. Otherwise, it stays silent and hence defers to the regular approval flow of the agent tool.
-.SH "OPTIONS"
-.RS 0
-.IP \(bu 4
-\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
-.IP \(bu 4
-\[lB]\fB-t\fR|\fB--tool\fR \fItool\fR\[rB]: The agent tool whose event payload is read: \fBclaude\fR, \fBcopilot\fR, or \fBcodex\fR (as configured: \fBcodex\fR). Default: \fB$ASE_TOOL\fR, else \fBclaude\fR.
-.RE 0
-.SH "ENVIRONMENT"
-.RS 0
-.IP \(bu 4
-\fBPLUGIN_ROOT\fR, \fBCLAUDE_PLUGIN_ROOT\fR, \fBCOPILOT_PLUGIN_ROOT\fR: The plugin root directory for the auto-approval of plugin file reads.
-.IP \(bu 4
-\fBASE_TOOL\fR: The default of \fB--tool\fR.
-.RE 0
-.SH "EXIT STATUS"
-.P
-Exits with status \fB0\fR, unless \fB--tool\fR is invalid (status \fB1\fR).
-.SH "SEE ALSO"
-.P
-\fBase\fR(1), \fBase-hook\fR(1), \fBase-hook-pre-tool-use\fR(1).
-.SH "AUTHOR"
-.P
-Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR