Updates.

Author: DariuszDepta

TaskCmd.idml .taskcmdTaskCmd.idml renamed to .taskcmd

@@ -1,16 +1,16 @@
 .tasks
 
   .build
-    .desc Builds in debug mode
+    .desc Builds task commander in debug mode
     .cmd cargo +stable build
 
   .clean
-    .desc Cleans all targets
+    .desc Cleans all generated artifacts
     .cmd cargo +stable clean
     .cmd rm -rf manual/book
 
   .clippy
-    .desc Runs clippy for all targets
+    .desc Runs linter
     .cmd cargo +stable clippy --all-targets
 
   .cov
@@ -24,12 +24,12 @@
     .cmd cargo +stable llvm-cov --no-cfg-coverage --html
 
   .cov-html-open
-    .desc Generates code coverage report in HTML format
+    .desc Generates code coverage report in HTML format and opens in browser
     .cmd cargo +stable llvm-cov clean
     .cmd cargo +stable llvm-cov --no-cfg-coverage --html --open
 
   .cov-badge
-    .desc Generates the detailed code coverage badge
+    .desc Generates code coverage badge
     .cmd cargo +stable llvm-cov clean
     .cmd cargo +stable llvm-cov --no-cfg-coverage --json --summary-only | coverio -l coverage -c --tag cov-badge
 
@@ -38,23 +38,23 @@
     .cmd cargo +stable doc
 
   .doc-private
-    .desc Generates documentation
+    .desc Generates private documentation
     .cmd cargo +stable doc --document-private-items
 
   .doc-open
     .desc Generates documentation and opens in browser
     .cmd cargo +stable doc --open
 
   .doc-private-open
-    .desc Generates documentation and opens in browser
+    .desc Generates private documentation and opens in browser
     .cmd cargo +stable doc --open --document-private-items
 
   .fmt
     .desc Runs code formatter
     .cmd cargo +nightly fmt
 
   .install
-    .desc Builds and installs release version from local sources
+    .desc Installs task commander from local sources
     .cmd cargo +stable install taskcmd --path . --force
 
   .manual
@@ -69,17 +69,17 @@
     .task cov-badge
 
   .serve
-    .desc Serves the manual locally and rebuilds on changes
+    .desc Serves manual locally
     .cmd cd manual && mdbook serve
 
   .test
     .desc Runs tests in debug mode
     .cmd cargo +stable test
 
   .testn
-    .desc Runs tests in debug mode
+    .desc Runs tests in debug mode using nextest
     .cmd cargo +stable nextest run
 
   .uninstall
-    .desc Uninstalls previously installed local version
+    .desc Uninstalls previously installed task commander
     .cmd cargo +stable uninstall taskcmd

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "taskcmd"
-version = "0.1.1"
+version = "0.1.2"
 authors = ["Dariusz Depta <depta@engos.de>"]
 description = "Task commander"
 documentation = "https://docs.rs/taskcmd"
@@ -11,7 +11,13 @@ categories = ["command-line-utilities"]
 edition = "2024"
 license = "MIT OR Apache-2.0"
 exclude = [
-    "manual/"
+    ".gitignore",
+    ".taskcmd",
+    "CODE_OF_CONDUCT.md",
+    "rustfmt.toml",
+    "adr",
+    "manual",
+    "tmBundle"
 ]
 
 [dependencies]

Cargo.toml

@@ -0,0 +1,72 @@
+# ADR-0001 Build task runner in Rust
+
+## Date
+ 
+**2026-01-03**
+
+## Status
+
+**Accepted**
+
+## Context
+
+Rust projects typically require a command runner to orchestrate common development workflows
+such as building, testing, linting, generating coverage reports, and releasing crates.
+
+The de facto standard for this purpose is [go-task], a mature and widely adopted task runner
+implemented in Go. It is configured through `Taskfile.yml` and distributed as a standalone binary.
+
+We have used [go-task] for several years across multiple non-trivial Rust projects and have gained
+substantial operational experience with it. This experience has helped us identify both the essential
+capabilities required from a task runner in the Rust ecosystem and the limitations of [go-task].
+
+These observations motivated an evaluation of whether a purpose-built solution could better address
+the needs of Rust projects while retaining the simplicity of a standalone command runner.
+
+## Decision
+
+We build a new, independent task runner written in Rust for Rust project workflows.
+
+## Decision Drivers
+
+### Toolchain purity
+
+[go-task] is implemented in Go. Even though it ships as a single binary,
+depending on it still means a Go-originated tool sits in the middle of an otherwise
+all-Rust toolchain and release pipeline.
+
+### Distribution as a Rust crate
+ 
+Shipping task runner as a installable crate for projects that are already standardized on `cargo`.
+
+### A different task-definition format
+
+[go-task]'s `Taskfile.yml` is YAML. The intent with a new task runner is to move
+away from YAML for task definitions in favor of a syntax better suited to the tool's
+own semantics without a need to build a DSL.
+
+### Full control as a from-scratch project
+ 
+Building task runner from the ground up means owning the feature roadmap, file format,
+and execution model directly. This also serves as a deliberate opportunity to design
+and ship a complete Rust CLI tool end-to-end.
+
+## Consequences
+
+### Positive
+
+- The full toolchain for Rust-centric repositories can stay Rust-only,
+  with no Go dependency required to build or run project tasks.
+- Full freedom to define the task file format and feature set to fit the
+  workflows actually needed, rather than working within [go-task]'s existing model.
+
+### Negative
+
+- All maintenance burden shifts from an established upstream project onto
+  task runner own development — no inherited community, issue triage, or battle-testing.
+- Task runner starts with a smaller feature set and ecosystem than [go-task]
+  and will need time to reach maturity.
+- Anyone adopting a new task runner has to learn a new, non-standard task-definition
+  syntax instead of reusing the widely known `Taskfile.yml` format.
+
+[go-task]: https://taskfile.dev

Taskfile.yml

@@ -0,0 +1,5 @@
+# Architecture Decision Records
+
+| No.                                         | Title                     |
+|---------------------------------------------|---------------------------|
+| [0001](./0001-build-task-runner-in-Rust.md) | Build task runner in Rust |

adr/0001-build-task-runner-in-Rust.md

@@ -9,15 +9,21 @@ use std::fs::{read_dir, read_to_string};
 /// are not reported precisely because such failures are expected to be rare.
 /// This function will just panic if the task definitions file is not accessible.
 pub fn load_definitions() -> Result<String> {
+  let mut files = vec![];
   let paths = read_dir(".").expect("Failed to access current directory");
   for entry in paths.flatten() {
     let file_type = entry.file_type().expect("Failed to get file type");
     if file_type.is_file() {
-      let file_name = entry.file_name();
-      if file_name.eq_ignore_ascii_case("taskcmd.idml") {
-        return Ok(read_to_string(file_name).expect("Failed to read task definitions file"));
+      let file_name = entry.file_name().to_string_lossy().to_string();
+      if file_name.ends_with(".taskcmd") {
+        files.push(file_name);
       }
     }
   }
-  Err(err_definitions_not_found())
+  files.sort();
+  if let Some(file_name) = files.first() {
+    Ok(read_to_string(file_name).expect("Failed to read task definitions file"))
+  } else {
+    Err(err_definitions_not_found())
+  }
 }