@rse/ase 1.0.7 → 2.0.0

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

@@ -0,0 +1,47 @@
+.TH "ASE-TASK-LIST" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-list\fR - List Persisted Task Ids
+.SH "SYNOPSIS"
+.P
+\fBase task list\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB-v\fR|\fB--verbose\fR\[rB] \[lB]\fB-i\fR|\fB--include\fR \fIstates\fR\[rB] \[lB]\fB-e\fR|\fB--exclude\fR \fIstates\fR\[rB]
+.SH "DESCRIPTION"
+.P
+\fBase task list\fR lists the ids of the persisted task plans of the current project in the task store (see \fBase-task\fR(1)), one per line, in natural order (numbers ordered by their value, e.g., \fBFOO-2\fR before \fBFOO-10\fR).
+.P
+The listed tasks are restricted to those whose lifecycle status (the \fBStatus\fR frontmatter key, or the initial state of the task lifecycle model if absent) is in the effective state set of the \fB--include\fR and \fB--exclude\fR options. By default, all tasks except the ones in a \fIfinished\fR state of the task lifecycle model are listed. A task whose status is unknown to the task lifecycle model is always listed, but warned about.
+.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-v\fR|\fB--verbose\fR\[rB]: Annotate each task id with the lifecycle status of its plan, the modification time of its plan as \fB(YYYY-MM-DD HH:MM)\fR, its effort size (the T-shirt size \fBXS\fR, \fBS\fR, \fBM\fR, \fBL\fR, or \fBXL\fR of the valid \fBEffort\fR frontmatter key of the plan, else \fB-\fR), and its title (the text after \fBTASK:\fR of the first \fB#   TASK:\fR heading of the plan body, else empty), all separated by a single tab character.
+.IP \(bu 4
+\[lB]\fB-i\fR|\fB--include\fR \fIstates\fR\[rB]: Restrict the listing to the tasks in one of the \fIstates\fR, a comma-separated list of lifecycle states of the task lifecycle model of the project (given case-insensitively), where the term \fBfinished\fR expands to the finished states of the model and the term \fBnone\fR (as well as an empty term) is ignored. An empty list (default: \fBnone\fR) means all states.
+.sp
+The states of the models are \fBOPEN\fR, \fBSHELVED\fR, \fBCLOSED\fR, and \fBCANCELLED\fR (\fBsolo\fR), \fBPLANNING\fR, \fBSHELVED\fR, \fBIMPLEMENTING\fR, \fBSTALLED\fR, \fBIMPLEMENTED\fR, and \fBCANCELLED\fR (\fBteam\fR), and \fBDRAFTED\fR, \fBSHELVED\fR, \fBPLANNING\fR, \fBPLANNED\fR, \fBSTALLED\fR, \fBIMPLEMENTING\fR, \fBIMPLEMENTED\fR, \fBDECLINED\fR, \fBQUALIFYING\fR, \fBQUALIFIED\fR, \fBDEFERRED\fR, \fBINTEGRATING\fR, \fBINTEGRATED\fR, and \fBCANCELLED\fR (\fBenterprise\fR). A state which is not one of the model is an error.
+.IP \(bu 4
+\[lB]\fB-e\fR|\fB--exclude\fR \fIstates\fR\[rB]: Exclude the tasks in one of the \fIstates\fR from the listing, a comma-separated list of the same form as for \fB--include\fR, applied after \fB--include\fR (default: \fBfinished\fR, i.e., the finished states of the model). Use \fBnone\fR to exclude nothing. If \fB--include\fR and \fB--exclude\fR cancel out to an empty state set, this is an error.
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR on an error, like an invalid state, an empty effective state set, or an unreachable task store.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# list all unfinished tasks
+$ ase task list
+
+# list all tasks, including the finished ones, with details
+$ ase task list -v -e none
+
+# list the tasks waiting for their qualification
+$ ase task list -i IMPLEMENTED,DECLINED
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-status\fR(1), \fBase-task-board\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-load.1

@@ -0,0 +1,36 @@
+.TH "ASE-TASK-LOAD" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-load\fR - Write a Task Plan to Standard Output
+.SH "SYNOPSIS"
+.P
+\fBase task load\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIid\fR
+.SH "DESCRIPTION"
+.P
+\fBase task load\fR loads the task plan with the given \fIid\fR from the task store (see \fBase-task\fR(1)) and writes it to standard output, in the textual task format: the frontmatter block (with its keys in canonical order and their values column-aligned), the plan body, and the attachment blocks (with their \fBData\fR as literal block scalars). A plan in a legacy format is normalized into the current frontmatter shape on the fly. If no such task exists, nothing is written.
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\fIid\fR: The id of the task, matching \fB\[lB]A-Za-z0-9#\[rB]\[lB]A-Za-z0-9#_-\[rB]*\fR.
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, also if no such task exists, \fB1\fR on an invalid \fIid\fR or an unreachable task store.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# copy a task plan into a file
+$ ase task load json-export >json-export.md
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-save\fR(1), \fBase-task-view\fR(1), \fBase-task-edit\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-newid.1

@@ -0,0 +1,61 @@
+.TH "ASE-TASK-NEWID" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-newid\fR - Print the Next Free Task Id
+.SH "SYNOPSIS"
+.P
+\fBase task newid\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB-p\fR|\fB--proposal\fR \fIid\fR\[rB] \[lB]\fB-t\fR|\fB--taken\fR \fIids\fR\[rB] \[lB]\fB-v\fR|\fB--verbose\fR\[rB] \[lB]\fItitle\fR\[rB]
+.SH "DESCRIPTION"
+.P
+\fBase task newid\fR prints the next free task id according to the effective task id scheme of the project (see \fBase-task-idscheme\fR(1) and \fBTASK ID SCHEMES\fR in \fBase-task\fR(1)), determined by searching all existing task ids of the project in the task store, plus the ids given via \fB--taken\fR, plus the reserved id \fBdefault\fR:
+.RS 0
+.IP \(bu 4
+\fBslug\fR\[lB]\fB:\fR\fIwords\fR\[rB]: The slug of the first \fIwords\fR words of \fItitle\fR (starting with the first word beginning with a letter, with diacritics stripped, lower-cased, and joined with \fB-\fR).
+.IP \(bu 4
+\fBseq\fR\[lB]\fB:\fR\fItemplate\fR\[rB]: The highest sequence number of all ids matching \fItemplate\fR plus one, but at least the high-water mark of all ids ever removed (deleted, purged, or renamed) or allocated plus one, so the number of such a task is never reused. Ids not matching the current \fItemplate\fR (e.g., after a template change) are ignored.
+.sp
+The allocated number is \fIreserved\fR by raising the high-water mark atomically, so a concurrent allocation never yields the same id. The \fItitle\fR is not used.
+.IP \(bu 4
+\fBany\fR: The proposed id of \fB--proposal\fR, sanitized (whitespace runs replaced by \fB-\fR, all characters other than \fBA-Z\fR, \fBa-z\fR, \fB0-9\fR, \fB#\fR, \fB_\fR, and \fB-\fR removed, and leading \fB_\fR and \fB-\fR stripped), else the slug of the first two words of \fItitle\fR.
+.RE 0
+.P
+A slug or proposed id which is already taken gets a numeric suffix \fB-2\fR, \fB-3\fR, etc. As only a \fBseq\fR id is reserved, the first save of the new task should be a create-only one (\fBase task save --create\fR, see \fBase-task-save\fR(1)), which fails instead of overwriting a concurrently created task of the same id.
+.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-p\fR|\fB--proposal\fR \fIid\fR\[rB]: The proposed task id, honored for the task id scheme \fBany\fR only (default: none).
+.IP \(bu 4
+\[lB]\fB-t\fR|\fB--taken\fR \fIids\fR\[rB]: A comma-separated list of task ids to consider as taken in addition to the existing ones (default: none), e.g., the ids planned for further tasks not yet saved. Whitespace around the ids is ignored.
+.IP \(bu 4
+\[lB]\fB-v\fR|\fB--verbose\fR\[rB]: Instead of the id only, print the three lines \fBscheme:\fR (the effective task id scheme), \fBid:\fR (the new id), and \fBmatch:\fR (the regular expression matching all ids conforming to the scheme).
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\[lB]\fItitle\fR\[rB]: The title of the new task, from which the id is derived for the schemes \fBslug\fR and \fBany\fR (default: empty). For \fBslug\fR (and for \fBany\fR without \fB--proposal\fR), a title without any word beginning with a letter is an error.
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if no id can be derived (e.g., a missing title) or the task store is unreachable.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# derive an id from a title under the "slug" scheme
+$ ase task newid "Export the Tasks as JSON"
+export-the
+
+# show the details of the allocation under the "seq:#%d" scheme
+$ ase task newid -v
+scheme: seq:#%d
+id:     #43
+match:  ^#(\[lB]0-9\[rB]+)$
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-idscheme\fR(1), \fBase-task-save\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-purge.1

@@ -0,0 +1,37 @@
+.TH "ASE-TASK-PURGE" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-purge\fR - Remove Old Task Plans
+.SH "SYNOPSIS"
+.P
+\fBase task purge\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fIage\fR\[rB]
+.SH "DESCRIPTION"
+.P
+\fBase task purge\fR removes all persisted task plans of the current project from the task store (see \fBase-task\fR(1)) whose modification time is older than \fIage\fR, regardless of their lifecycle status. Each removed task is logged as \fBtask: purged "\fR\fIid\fR\fB"\fR, or \fBtask: no tasks
+to purge\fR is logged if none was removed. For a \fBseq\fR task id scheme, the sequence numbers of the purged tasks are never reused by \fBase-task-newid\fR(1).
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\[lB]\fIage\fR\[rB]: The maximum age of the task plans to keep, as \fB<number><unit>\fR, where \fIunit\fR is one of \fBh\fR (hour), \fBd\fR (day, 24 hours), \fBm\fR (month, 30 days), or \fBy\fR (year, 365 days) (default: \fB31d\fR).
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success (also if no task was removed), \fB1\fR on a malformed \fIage\fR or an unreachable task store.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# remove all tasks not modified within the last half year
+$ ase task purge 6m
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-delete\fR(1), \fBase-task-list\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-rename.1

@@ -0,0 +1,44 @@
+.TH "ASE-TASK-RENAME" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-rename\fR - Rename a Task Plan
+.SH "SYNOPSIS"
+.P
+\fBase task rename\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIold-id\fR \fInew-id\fR
+.SH "DESCRIPTION"
+.P
+\fBase task rename\fR renames the task plan with the given \fIold-id\fR to \fInew-id\fR in the task store (see \fBase-task\fR(1)), rewriting the \fBId\fR frontmatter key inside the plan.
+.P
+All references to \fIold-id\fR in the \fBAfter\fR frontmatter keys of all other task plans of the project are rewritten to \fInew-id\fR (in the frontmatter only, so their \fBModified\fR key stays untouched), and the number of updated plans is reported. For an \fIexplicit epic\fR, i.e., a task whose \fBGroup\fR key equals its old (or already its new) id, its own \fBGroup\fR key and those of all its member task plans are rewritten, too, while otherwise the group names are left untouched, as they form a namespace of their own.
+.P
+The task itself is renamed first, so an interruption never leaves both ids behind; a failure to update the references afterwards is reported together with the plans left behind.
+.P
+For a \fBseq\fR task id scheme, the sequence number of \fIold-id\fR is never reused by \fBase-task-newid\fR(1). A \fInew-id\fR not conforming to the task id scheme of the project is warned about. Finally, the rename is reported to the \fBase service\fR of the project (if it ever ran, i.e., \fB.ase/service.yaml\fR exists), so its AI usage windows follow the task; a failure of this report is only warned about.
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\fIold-id\fR: The current id of the task, matching \fB\[lB]A-Za-z0-9#\[rB]\[lB]A-Za-z0-9#_-\[rB]*\fR.
+.IP \(bu 4
+\fInew-id\fR: The new id of the task, matching \fB\[lB]A-Za-z0-9#\[rB]\[lB]A-Za-z0-9#_-\[rB]*\fR, which must not be in use already.
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if no such task existed (reported as \fBtask: no
+task "\fR\fIold-id\fR\fB" to rename\fR), the \fInew-id\fR is already in use, or on any other error.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+$ ase task rename json-export export-json
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-edit\fR(1), \fBase-task-newid\fR(1), \fBase-task-delete\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-request.1

@@ -0,0 +1,61 @@
+.TH "ASE-TASK-REQUEST" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-request\fR - Request the Processing of a Task by a Prompt
+.SH "SYNOPSIS"
+.P
+\fBase task request\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIid\fR \fIname\fR \[lB]\fIprompt\fR ...\[rB]
+.SH "DESCRIPTION"
+.P
+\fBase task request\fR requests the processing of the task \fIid\fR by the \fIprompt\fR under the request name \fIname\fR, for an agent processing the requests of this name (see \fBase-agent\fR(1)): \fBedit\fR for the edit requests of \fBase agent editor\fR (the same as key \fBE\fR of the task board, see \fBase-task-board\fR(1)), \fBestimate\fR for the (re-)estimation requests of \fBase agent estimator --mode request\fR (see \fBase-agent-estimator\fR(1)), \fBresearch\fR for the research requests of \fBase agent researcher\fR (see \fBase-agent-researcher\fR(1)), and any other name for the requests of a request agent of a definition kind or of \fBase agent adhoc\fR (with \fB--type request\fR and \fB--request-name\fR \fIname\fR).
+.P
+The request is attached to the task plan as an attachment of the type \fBtext/plain; charset=utf-8; kind="\fR\fIname\fR\fB"\fR, with the prompt as its data, its whitespace-collapsed first 60 characters as its description (resp. \fIname\fR\fB request without prompt\fR for an empty prompt), and its creation and modification timestamps. The aggregated state of the requests of the name is mirrored in the \fBTags\fR frontmatter key of the task as the tag \fBase-agent-\fR\fIname\fR\fB:pending\fR (resp. \fBase-agent-editor:pending\fR for \fBedit\fR), as the agents and the task boards see the task headers only.
+.P
+While being processed, the request turns into \fBkind="\fR\fIname\fR\fB-running"\fR (tag value \fBactive\fR), and on a failure into \fBkind="\fR\fIname\fR\fB-failed"\fR (tag value \fBfailed\fR). A new request replaces all failed requests of the name.
+.P
+The request is refused for a missing task, for a task in a finished state of the task lifecycle model, for an empty prompt of an \fBedit\fR request, and while a request of the name is being processed, as adding a request would change the task plan under the agent processing the running one. The prompt of any other request may be empty, for the request agents ignoring the prompts of their requests (like \fBase agent
+estimator --mode request\fR) or taking them as optional (like \fBase agent
+researcher\fR, which then researches the task plan itself), while a request agent consuming the prompts (by the placeholder \fB{prompt}\fR of its prompt template, or by its hooks \fBprepare\fR, \fBprompt\fR, or \fBfinish\fR, see \fBase-agent-adhoc\fR(1)) turns a request with an empty prompt into a failed one.
+.P
+The MCP tool \fBase_task_request\fR provides the same functionality.
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\fIid\fR: The id of the task.
+.IP \(bu 4
+\fIname\fR: The request name: a lower-case word of letters, digits, and dashes, starting with a letter, not ending in \fB-running\fR or \fB-failed\fR, and none of the built-in agent kinds \fBrebooter\fR, \fBcondenser\fR, \fBimplementer\fR, \fBqualifier\fR, \fBintegrator\fR, \fBeditor\fR, \fBestimator\fR, and \fBresearcher\fR (as its tag \fBase-agent-\fR\fIname\fR is the one of a built-in agent). The name \fBedit\fR selects the edit requests of \fBase agent editor\fR, the name \fBestimate\fR the estimation requests of \fBase agent estimator --mode
+request\fR, and the name \fBresearch\fR the research requests of \fBase agent
+researcher --mode request\fR.
+.IP \(bu 4
+\[lB]\fIprompt\fR ...\[rB]: The prompt of the request, with all its words joined by single spaces (and leading and trailing whitespace removed), where an omitted prompt is an empty one (refused for \fBedit\fR).
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if the request name is invalid or the request is refused.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# request an edit of the plan of task "json-export"
+$ ase task request json-export edit "Also support JSON5 output"
+
+# request a lint report from a request agent of name "lint"
+$ ase task request json-export lint focus on error handling
+
+# request a re-estimation of the effort (without a prompt)
+$ ase task request json-export estimate
+
+# request a research of a topic for the task
+$ ase task request json-export research streaming JSON serialization
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-board\fR(1), \fBase-agent\fR(1), \fBase-agent-editor\fR(1), \fBase-agent-researcher\fR(1), \fBase-agent-adhoc\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-save.1

@@ -0,0 +1,48 @@
+.TH "ASE-TASK-SAVE" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-save\fR - Save a Task Plan from Standard Input
+.SH "SYNOPSIS"
+.P
+\fBase task save\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fB-c\fR|\fB--create\fR\[rB] \fIid\fR
+.SH "DESCRIPTION"
+.P
+\fBase task save\fR reads a task plan in the textual task format (see \fBase util meta format-task\fR) from standard input and saves it under the given \fIid\fR in the task store (see \fBase-task\fR(1)), creating or overwriting the task.
+.P
+The text is parsed into the frontmatter block, the plan body, and the attachment blocks, where a plan in a legacy format is normalized into the current frontmatter shape first. The \fBId\fR frontmatter key is always taken from the \fIid\fR argument, and a missing \fBType\fR key is set to \fBtext/vnd.ase.task\fR. A text without a closed frontmatter block is taken as the plan body.
+.P
+Attachment data given as the elision marker \fB\[lB]elided: \fR\fIN\fR\fB lines\[rB]\fR is restored from the stored plan. The usage attachment (\fBkind="usage"\fR) can be changed by a booking only: an overwrite keeps the stored usage attachment, while a create drops any given one.
+.P
+The \fBStatus\fR frontmatter key is checked against the task lifecycle model of the project: a changed status which is not a state of the model, or which is not reachable from the previously saved status (or, for a new task, from the initial state of the model) via one or more transitions of the model, lets the save fail. An \fIid\fR not conforming to the task id scheme of the project is saved, but warned about.
+.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-c\fR|\fB--create\fR\[rB]: Create the task only: fail if a task with \fIid\fR already exists, instead of overwriting it (default: off). Intended for the first save of a task whose \fIid\fR was obtained via \fBase-task-newid\fR(1), as only a \fBseq\fR id is reserved there, so a concurrently created task of the same id is never overwritten.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\fIid\fR: The id of the task, matching \fB\[lB]A-Za-z0-9#\[rB]\[lB]A-Za-z0-9#_-\[rB]*\fR.
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if the \fIid\fR is invalid, the plan is invalid (e.g., a multi-line frontmatter value, or a body which would be misread as attachments), the \fBStatus\fR is not a state of the model or not reachable, or, with \fB--create\fR, the task already exists.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# create a new task from a plan file
+$ id=$(ase task newid "Export as JSON")
+$ ase task save --create "$id" <plan.md
+
+# round-trip a task plan through a filter
+$ ase task load json-export | sed -e 's/^Kind:.*/Kind: CRAFTING/' | ase task save json-export
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-load\fR(1), \fBase-task-edit\fR(1), \fBase-task-newid\fR(1), \fBase-task-status\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-status.1

@@ -0,0 +1,55 @@
+.TH "ASE-TASK-STATUS" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-status\fR - Get or Set the Lifecycle Status of a Task
+.SH "SYNOPSIS"
+.P
+\fBase task status\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \[lB]\fIid\fR\[lB]\fB:\fR\[rB]\[rB] \[lB]\fIstatus\fR\[rB]
+.SH "DESCRIPTION"
+.P
+\fBase task status\fR gets or sets the lifecycle status, i.e., the \fBStatus\fR frontmatter key, of the task plan with the given \fIid\fR in the task store (see \fBase-task\fR(1)).
+.P
+Without \fIstatus\fR, the current status is printed to standard output, where a plan without a \fBStatus\fR key reads as the initial state of the task lifecycle model of the project.
+.P
+With \fIstatus\fR, the status is set and the change is logged as \fBtask: set status of "\fR\fIid\fR\fB" from "\fR\fIfrom\fR\fB" to "\fR\fIto\fR\fB"\fR. The \fIstatus\fR is given case-insensitively and has to be a state of the task lifecycle model of the project, which is reachable from the current status via one or more transitions of the model (see \fBTASK LIFECYCLE MODELS\fR in \fBase-task\fR(1)); a current status foreign to the model can be changed to any state, to allow its correction.
+.P
+Only the frontmatter is changed: the \fBModified\fR key is left alone, as it tracks the changes of the plan body only.
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\[lB]\fIid\fR\[lB]\fB:\fR\[rB]\[rB]: The id of the task (default: \fB$ASE_TASK_ID\fR, else \fBdefault\fR). A trailing colon is stripped, which allows to mark a single argument explicitly as the \fIid\fR: if only a single argument is given, it is taken as \fIstatus\fR if it is a state of the task lifecycle model (case-insensitively) and has no trailing colon, else as \fIid\fR.
+.IP \(bu 4
+\[lB]\fIstatus\fR\[rB]: The lifecycle status to set.
+.RE 0
+.SH "ENVIRONMENT"
+.RS 0
+.IP \(bu 4
+\fBASE_TASK_ID\fR: The default task id (default: \fBdefault\fR).
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if no such task exists, the \fIstatus\fR is not a state of the task lifecycle model, or it is not reachable from the current status.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# print the status of the task "json-export"
+$ ase task status json-export:
+
+# move the task "json-export" into "SHELVED"
+$ ase task status json-export shelved
+
+# close the task of $ASE_TASK_ID
+$ ase task status CLOSED
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-lifecycle\fR(1), \fBase-task-list\fR(1), \fBase-task-save\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-store.1

@@ -0,0 +1,194 @@
+.TH "ASE-TASK-STORE" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-store\fR - Manage the per-user task store REST API server
+.SH "SYNOPSIS"
+.P
+\fBase task store\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIcommand\fR \[lB]\fIoptions\fR \[lB]...\[rB]\[rB]
+.P
+\fBase task store start\fR \[lB]\fB-a\fR|\fB--address\fR \fIhost\fR\[rB] \[lB]\fB-p\fR|\fB--port\fR \fIport\fR\[rB] \[lB]\fB-t\fR|\fB--token\fR \fItoken\fR\[rB] \[lB]\fB-c\fR|\fB--cors\fR \fIorigin\fR\[rB] \[lB]\fB-m\fR|\fB--module\fR \fIname\fR\[rB] \[lB]\fB-d\fR|\fB--basedir\fR \fIdir\fR\[rB] \[lB]\fB-s\fR|\fB--solo\fR|\fB--no-solo\fR\[rB] \[lB]\fB--with-agent-relay\fR|\fB--without-agent-relay\fR\[rB] \[lB]\fB--tls-cert\fR \fIfile\fR \fB--tls-key\fR \fIfile\fR\[rB] \[lB]\fB-f\fR|\fB--foreground\fR\[rB]
+.P
+\fBase task store status\fR
+.P
+\fBase task store log\fR \[lB]\fB-f\fR|\fB--follow\fR\[rB] \[lB]\fB-n\fR|\fB--lines\fR \fIn\fR\[rB]
+.P
+\fBase task store stop\fR
+.SH "DESCRIPTION"
+.P
+\fBase task store\fR manages the \fItask store server\fR: a per-user (not per-project), bearer token authenticated REST API server, which persists the task plans of \fIall\fR projects registered with it and which the \fBase task\fR commands of a project use through a remote \fBproject.task.store.url\fR of the form \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] (see \fBase-task\fR(1)).
+.P
+It can run locally or on a central host, as long as all clients reach it. The REST API itself, its task plan model, and its event notifications are described in \fBdocs/task-api.md\fR of the \fIASE\fR distribution.
+.P
+The server is \fIstorage agnostic\fR: it implements the authentication, the validation, the task lifecycle model checks, and the event notifications itself, and delegates the \fIpersistence\fR of projects and task plans to a single \fIstorage plugin\fR loaded at its start (see \fBSTORAGE PLUGINS\fR below).
+.P
+The server is configured through its per-user configuration file \fIper-user configuration directory\fR\fB/store.yaml\fR (see \fBFILES\fR), into which the effective configuration of every start is persisted again, so later starts, \fBase task store status\fR, and \fBase task store stop\fR find and probe the running server with the very same address, port, token, and TLS setting. Optionally, the server additionally co-hosts the \fIagent relay\fR (see \fBase-agent-relay\fR(1)), so a central host needs a single server process only.
+.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 of \fBase task store\fR resp. of the given \fIcommand\fR and exit.
+.RE 0
+.SH "COMMANDS"
+.P
+The following commands exist:
+.SS "ase task store start"
+.P
+\fBase task store start\fR \[lB]\fIoptions\fR\[rB]
+.P
+Start the task store server in the background (detached, logging into \fIper-user configuration directory\fR\fB/store.log\fR), or with \fB--foreground\fR in the current process. Before the server is started, the given port is validated, and the TLS certificate and key are resolved (where both or none have to be given) and checked for readability, so invalid options never leave no server running.
+.P
+The start is \fIidempotent\fR: a server already running on the configured address and port (as identified by probing its \fB/projects\fR endpoint) is left alone and reported as \fBtask store: already running on\fR \fIurl\fR. If an explicitly given option \fIdeviates\fR from the configuration of the running server (\fB--address\fR, \fB--port\fR, \fB--token\fR, \fB--cors\fR, \fB--tls-cert\fR, \fB--tls-key\fR, \fB--module\fR, \fB--basedir\fR, \fB--solo\fR/\fB--no-solo\fR, \fB--with-agent-relay\fR, or \fB--without-agent-relay\fR), the running server is instead stopped and restarted with the new configuration.
+.P
+A running server rejecting the configured token is an error. A configured port held by a foreign service is re-allocated (with a warning). Binding to a non-loopback \fIhost\fR without TLS is warned about, as the bearer token would then travel unencrypted over the network.
+.P
+A detached server is awaited (for up to 10 seconds) until it responds to the probe with the expected token, and is reported as \fBtask store:
+started on\fR \fIurl\fR \fB(storage plugin "\fR\fIname\fR\fB")\fR. If it exits during startup, does not respond, or its port is taken by a foreign service meanwhile, it is terminated and the failure is reported together with the last 20 lines of its log. The server terminates on \fBSIGTERM\fR, \fBSIGINT\fR, \fBSIGHUP\fR, or \fBSIGQUIT\fR, stopping its storage plugin and removing its \fBpid\fR from \fBstore.yaml\fR. The options are:
+.RS 0
+.IP \(bu 4
+\[lB]\fB-a\fR|\fB--address\fR \fIhost\fR\[rB]: The IP address (or hostname) to bind to (default: the configured \fBaddress\fR, else \fB127.0.0.1\fR). Use \fB0.0.0.0\fR resp. \fB::\fR to bind to all interfaces (the local probes then connect to \fB127.0.0.1\fR resp. \fB::1\fR).
+.IP \(bu 4
+\[lB]\fB-p\fR|\fB--port\fR \fIport\fR\[rB]: The TCP port to bind to, an integer in the range \fB1\fR..\fB65535\fR (default: the configured \fBport\fR, else a free port allocated randomly in the range \fB42000\fR..\fB44000\fR).
+.IP \(bu 4
+\[lB]\fB-t\fR|\fB--token\fR \fItoken\fR\[rB]: The bearer token every request has to carry in its \fBAuthorization: Bearer\fR \fItoken\fR header (default: \fB$ASE_TASK_STORE_TOKEN\fR, else the configured \fBtoken\fR, else a freshly generated random token of 48 hexadecimal digits). The token grants \fIfull\fR access to \fIall\fR projects of the server.
+.IP \(bu 4
+\[lB]\fB-c\fR|\fB--cors\fR \fIorigin\fR\[rB]: Allow cross-origin browser requests (Cross-Origin Resource Sharing, CORS) from \fIorigin\fR, e.g. \fBhttp://localhost:5173\fR, or from any origin with \fB*\fR. Repeatable for multiple origins (default: the configured \fBcors\fR list, else none, i.e., no CORS headers are emitted and cross-origin browser requests fail).
+.IP \(bu 4
+\[lB]\fB-m\fR|\fB--module\fR \fIname\fR\[rB]: The storage plugin to load: \fBase\fR for the built-in file-based one, \fBgithub\fR, \fBgitlab\fR, resp. \fBgitea\fR for the built-in GitHub, GitLab, resp. Gitea Issues one, any other plain \fIname\fR (matching \fB\[lB]A-Za-z0-9_-\[rB]+\fR) for the NPM package \fBase-task-store-\fR\fIname\fR (resolvable from the \fIASE\fR installation), and a relative or absolute path for a local module (default: the configured \fBstorage.plugin\fR, else \fBase\fR).
+.sp
+The given plugin is persisted as \fBstorage.plugin\fR.
+.IP \(bu 4
+\[lB]\fB-d\fR|\fB--basedir\fR \fIdir\fR\[rB]: The base directory of the built-in \fBase\fR storage plugin (default: the configured \fBstorage.options.basedir\fR, resolved relative to the per-user configuration directory, else \fBtasks\fR below it). A given \fIdir\fR is persisted as \fBstorage.options.basedir\fR. Ignored for all other storage plugins.
+.IP \(bu 4
+\[lB]\fB-s\fR|\fB--solo\fR\[rB]: Let the built-in \fBase\fR storage plugin store a \fIsingle\fR project flat in its base directory, accepting \fIany\fR project id (default: the configured \fBstorage.options.solo\fR, else one sub-directory per project). Persisted as \fBstorage.options.solo\fR. Ignored for all other storage plugins.
+.IP \(bu 4
+\[lB]\fB--no-solo\fR\[rB]: Let the built-in \fBase\fR storage plugin store one sub-directory per project, removing a configured \fBstorage.options.solo\fR.
+.IP \(bu 4
+\[lB]\fB--with-agent-relay\fR\[rB]: Additionally co-host the agent relay (see \fBase-agent-relay\fR(1)), i.e., its \fB/agents\fR and \fB/projects/\fR\fIid\fR\fB/agents\fR... endpoints, under the same address, port, and token (default: the configured \fBrelay\fR, else not co-hosted). Persisted as \fBrelay\fR. Mutually exclusive with \fB--without-agent-relay\fR.
+.IP \(bu 4
+\[lB]\fB--without-agent-relay\fR\[rB]: Do not co-host the agent relay, removing a configured \fBrelay\fR. Mutually exclusive with \fB--with-agent-relay\fR.
+.IP \(bu 4
+\[lB]\fB--tls-cert\fR \fIfile\fR\[rB]: Serve HTTPS (and \fBwss://\fR for the WebSocket event endpoint) instead of plain HTTP, with the PEM certificate (chain) in \fIfile\fR. Requires \fB--tls-key\fR. Default: the \fBproject.task.store.crt\fR configuration (resolved relative to the configuration file defining it), unless \fBproject.task.store.url\fR selects plain HTTP via \fBase://\fR on this host, else the configured \fBtls.cert\fR, else plain HTTP. The effective path is persisted as \fBtls.cert\fR.
+.IP \(bu 4
+\[lB]\fB--tls-key\fR \fIfile\fR\[rB]: The PEM private key in \fIfile\fR for HTTPS. Requires \fB--tls-cert\fR. Default: the \fBproject.task.store.key\fR configuration (under the same condition as for \fB--tls-cert\fR), else the configured \fBtls.key\fR. The effective path is persisted as \fBtls.key\fR.
+.IP \(bu 4
+\[lB]\fB-f\fR|\fB--foreground\fR\[rB]: Run the server in the current process instead, logging to the terminal, until it is interrupted (e.g. via \fBCTRL+C\fR) or stopped via \fBase task store stop\fR. An already running server with an unchanged configuration is then an error.
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SS "ase task store status"
+.P
+\fBase task store status\fR
+.P
+Report whether the task store server is running, by probing the configured address and port with the configured token. Prints \fBtask
+store: running on\fR \fIurl\fR \fB(pid\fR \fIpid\fR\fB)\fR, followed by \fBwith agent
+relay\fR if the server co-hosts the agent relay, and exits with status \fB0\fR. Otherwise it prints why it is not running -- no port configured, port not responding, port in use by a foreign service, or a running server rejecting the configured token -- and exits with status \fB1\fR.
+.SS "ase task store log"
+.P
+\fBase task store log\fR \[lB]\fB-f\fR|\fB--follow\fR\[rB] \[lB]\fB-n\fR|\fB--lines\fR \fIn\fR\[rB]
+.P
+Show the log \fIper-user configuration directory\fR\fB/store.log\fR of the task store server run in the background. A server run with \fB--foreground\fR logs to the terminal instead, and without a log file just an informational message is printed. The log file is trimmed down to its last 2000 lines whenever a server is started on a log file larger than 1 MB. The options are:
+.RS 0
+.IP \(bu 4
+\[lB]\fB-f\fR|\fB--follow\fR\[rB]: Show the last \fIn\fR lines (default: \fB10\fR) and then, in the style of \fBtail -f\fR, follow all newly appended lines until interrupted, even once the server has stopped.
+.IP \(bu 4
+\[lB]\fB-n\fR|\fB--lines\fR \fIn\fR\[rB]: Show the last \fIn\fR lines only, where \fIn\fR is a positive integer (default: all lines, or \fB10\fR with \fB--follow\fR).
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SS "ase task store stop"
+.P
+\fBase task store stop\fR
+.P
+Stop the task store server: it is first probed (as a stale process id might meanwhile belong to a foreign process), then sent \fBSIGTERM\fR, and awaited for up to 5 seconds until it is gone, and finally its \fBpid\fR is removed from \fBstore.yaml\fR. A server which is not running (or not configured at all) is reported informationally with exit status \fB0\fR. A responding server whose process id is unknown, resp. a server not stopping within the timeout, is an error.
+.SH "STORAGE PLUGINS"
+.P
+A storage plugin is a Node.js module default-exporting a factory function, which receives the \fBstorage.options\fR of \fBstore.yaml\fR verbatim (see \fBdocs/task-api.md\fR for the plugin API). The following built-in storage plugins exist:
+.RS 0
+.IP \(bu 4
+\fBase\fR: The default, file-based plugin, persisting the task plans in the textual task format as \fBTASK-\fR\fIid\fR\fB.md\fR files. Its options are \fBbasedir\fR (the base directory, see \fB--basedir\fR), \fBsolo\fR (see \fB--solo\fR), and \fBlifecycle\fR (the task lifecycle model of newly registered projects, default: \fBsolo\fR).
+.sp
+Without \fBsolo\fR, every project is stored below \fIbasedir\fR\fB/\fR\fIproject-id\fR\fB/\fR, with its \fBPROJECT.yaml\fR as the project registry entry (carrying the task lifecycle model, the task id scheme, and the sequence number high-water mark). With \fBsolo\fR, a single project is stored flat in \fIbasedir\fR itself, with a single \fBPROJECT.yaml\fR there, and any project id is accepted -- which is exactly what the local \fBase:\fR\fIpath\fR form of \fBproject.task.store.url\fR uses in-process, without any server.
+.IP \(bu 4
+\fBgithub\fR: Persists the task plans as the \fIissues\fR of GitHub repositories, through the GitHub REST API.
+.sp
+Its options are \fBurl\fR (the web URL of the GitHub instance, default: \fBhttps://github.com\fR, else e.g. the one of a GitHub Enterprise Server or Cloud), \fBtoken\fR (default: \fB$GITHUB_TOKEN\fR, else \fB$GH_TOKEN\fR; required), \fBrepos\fR (required, a mapping of each project id onto its \fIowner\fR\fB/\fR\fIrepo\fR), and \fBpoll\fR (the polling interval of the change detection in seconds, default: \fB60\fR, \fB0\fR disables it).
+.IP \(bu 4
+\fBgitlab\fR: Persists the task plans as the \fIissues\fR of GitLab projects, through the GitLab REST API v4. Its options are \fBurl\fR (the GitLab instance, default: \fB$GITLAB_HOST\fR, else \fBhttps://gitlab.com\fR), \fBtoken\fR (default: \fB$GITLAB_TOKEN\fR; required, a token with scope \fBapi\fR and at least the role \fIPlanner\fR in the projects), \fBrepos\fR (required, a mapping of each project id onto its \fInamespace\fR\fB/\fR\fIproject\fR path, with nested groups allowed), and \fBpoll\fR (as for \fBgithub\fR).
+.IP \(bu 4
+\fBgitea\fR: Persists the task plans as the \fIissues\fR of Gitea repositories, through the Gitea REST API v1. Its options are \fBurl\fR (the Gitea instance, default: \fBhttps://gitea.com\fR), \fBtoken\fR (default: \fB$GITEA_TOKEN\fR; required, a token with the scopes \fBwrite:issue\fR and \fBread:repository\fR and write access to the repositories), \fBrepos\fR (required, a mapping of each project id onto its \fIowner\fR\fB/\fR\fIrepo\fR), and \fBpoll\fR (as for \fBgithub\fR).
+.RE 0
+.P
+The issue tracker plugins register a project by the label \fBase:project\fR of its repository and map the task plan frontmatter onto the issue state, assignees, labels, and dependencies, as detailed in \fBdocs/task-api.md\fR. The same plugins also run in-process (without any server) for the \fBgithub:\fR, \fBgitlab:\fR, and \fBgitea+http\[lB]s\[rB]:\fR forms of \fBproject.task.store.url\fR (see \fBase-task\fR(1)).
+.SH "ENVIRONMENT"
+.RS 0
+.IP \(bu 4
+\fBASE_TASK_STORE_TOKEN\fR: The default bearer token of \fBase task store start\fR (taking precedence over the configured \fBtoken\fR, but not over \fB--token\fR).
+.IP \(bu 4
+\fBGITHUB_TOKEN\fR, \fBGH_TOKEN\fR: The default access token of the \fBgithub\fR storage plugin.
+.IP \(bu 4
+\fBGITLAB_HOST\fR, \fBGITLAB_TOKEN\fR: The default instance and access token of the \fBgitlab\fR storage plugin.
+.IP \(bu 4
+\fBGITEA_TOKEN\fR: The default access token of the \fBgitea\fR storage plugin.
+.RE 0
+.SH "FILES"
+.RS 0
+.IP \(bu 4
+\fIper-user configuration directory\fR\fB/store.yaml\fR: The configuration and runtime state of the task store server (see \fBase\fR(1) for the location of the per-user configuration directory), written with mode \fB0600\fR, as it carries the token.
+.sp
+Its keys are \fBaddress\fR (the bound address), \fBport\fR (the bound port), \fBtoken\fR (the expected bearer token), \fBpid\fR (the process id of the running server), \fBcors\fR (the list of allowed CORS origins), \fBtls.cert\fR and \fBtls.key\fR (the paths of the PEM certificate and key, resolved relative to the file), \fBrelay\fR (\fBtrue\fR to co-host the agent relay), \fBstorage.plugin\fR (the storage plugin), and \fBstorage.options\fR (the options of the storage plugin, see \fBSTORAGE PLUGINS\fR), as in the example below.
+.IP \(bu 4
+\fIper-user configuration directory\fR\fB/store.log\fR: The log of the task store server run in the background.
+.IP \(bu 4
+\fIper-user configuration directory\fR\fB/tasks/\fR: The default base directory of the built-in \fBase\fR storage plugin.
+.RE 0
+.P
+An example \fBstore.yaml\fR is:
+.P
+.RS 2
+.nf
+address: 127.0.0.1
+port:    42042
+token:   8f3c\[lB]...\[rB]
+cors:
+    - http://localhost:5173
+storage:
+    plugin: ase
+    options:
+        basedir: /Users/rse/Library/Application Support/ase/tasks
+.fi
+.RE
+.SH "EXIT STATUS"
+.P
+\fBase task store status\fR exits with status \fB0\fR if the server is running and with status \fB1\fR otherwise. All other commands exit with status \fB0\fR on success and with status \fB1\fR on any error.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+# start the task store server locally and point the project to it
+$ ase task store start --port 42042
+$ ase config set project.task.store.url ase://127.0.0.1:42042
+
+# start a central task store server with TLS and co-hosted agent relay
+$ ase task store start --address 0.0.0.0 --port 42042 \[rs]
+    --tls-cert /etc/ssl/tasks.example.com.crt \[rs]
+    --tls-key /etc/ssl/tasks.example.com.key \[rs]
+    --with-agent-relay
+
+# start a task store server on the GitHub Issues storage plugin
+# (after configuring "storage.options.repos" in "store.yaml")
+$ ase task store start --module github
+
+# check and follow the server
+$ ase task store status
+$ ase task store log -f
+
+# stop the server
+$ ase task store stop
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-board\fR(1), \fBase-agent-relay\fR(1), \fBase-config\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR

package/dst/man/ase-task-view.1

@@ -0,0 +1,40 @@
+.TH "ASE-TASK-VIEW" "1" "October 2026" "2.0.0" "Agentic Software Engineering (ASE)"
+.SH "NAME"
+\fBase-task-view\fR - Show a Task Plan in the Pager
+.SH "SYNOPSIS"
+.P
+\fBase task view\fR \[lB]\fB-h\fR|\fB--help\fR\[rB] \fIid\fR
+.SH "DESCRIPTION"
+.P
+\fBase task view\fR loads the task plan with the given \fIid\fR from the task store (see \fBase-task\fR(1)) and shows it in the pager defined by \fB$PAGER\fR (falling back to \fBmore\fR), run through the shell (so a value with arguments is supported) and fed with the plan via its standard input. If standard output is not a terminal, the pager is bypassed and the plan is written plainly to standard output.
+.SH "OPTIONS"
+.RS 0
+.IP \(bu 4
+\[lB]\fB-h\fR|\fB--help\fR\[rB]: Show usage information and exit.
+.RE 0
+.SH "ARGUMENTS"
+.RS 0
+.IP \(bu 4
+\fIid\fR: The id of the task, matching \fB\[lB]A-Za-z0-9#\[rB]\[lB]A-Za-z0-9#_-\[rB]*\fR.
+.RE 0
+.SH "ENVIRONMENT"
+.RS 0
+.IP \(bu 4
+\fBPAGER\fR: The pager command (default: \fBmore\fR).
+.RE 0
+.SH "EXIT STATUS"
+.P
+\fB0\fR on success, \fB1\fR if no such task exists.
+.SH "EXAMPLES"
+.P
+.RS 2
+.nf
+$ PAGER="less -R" ase task view json-export
+.fi
+.RE
+.SH "SEE ALSO"
+.P
+\fBase\fR(1), \fBase-task\fR(1), \fBase-task-load\fR(1), \fBase-task-edit\fR(1), \fBmore\fR(1), \fBless\fR(1).
+.SH "AUTHOR"
+.P
+Dr. Ralf S. Engelschall \fI\(larse@engelschall.com\(ra\fR