docs(adr): capture task output

Signed-off-by: Ourchitecture <[email protected]>

src/docs/decisions/!template_[verb]_[the-nouns].md

@@ -1,5 +1,4 @@
 ---
-# These are optional elements. Feel free to remove any of them.
 status: {proposed | rejected | accepted | deprecated | … | superseded by [ADR-0005](0005-example.md)}
 date: {YYYY-MM-DD when the decision was last updated}
 deciders: {list everyone involved in the decision}

src/docs/decisions/capture_automation-task-output.md

@@ -0,0 +1,39 @@
+---
+status: accepted
+date: 2023-09-19
+deciders: Ourchitecture
+---
+
+# Capture automation task output
+
+## Context and Problem Statement
+
+Streaming task automation output to the terminal is useful for humans, but
+writing the output to a file can be useful for referencing long after the
+task is executed, used for task cache optimizations e.g. wireit, as well
+as can be uploaded for specific DevOps pipeline builds e.g. Continuous
+Integration.
+
+## Considered Options
+
+-   Pipe command output
+-   Capture "stderr" and "stdout"
+
+## Decision Outcome
+
+Building on the decision to [use NodeJS scripts](./script_automation-tasks.md)
+as well as [using Wireit](./optimize_automation-tasks.md),
+building on top of Node's built-in `exec` function was selected along with
+logging through the "winston" library. The team is already familiar with
+these technologies.
+
+### Consequences
+
+-   Good, because it enables Wireit output caching
+-   Good, because winston is a fairly ubiquitous solution for NodeJS logging
+-   Good, because it enables artifact uploads during DevOps pipeline runs
+    e.g. Continuous Integration
+
+## More Information
+
+-   [winston website](https://github.com/winstonjs/winston#readme)

src/docs/decisions/manage_automation-task-package-dependencies.md

@@ -1,5 +1,4 @@
 ---
-# These are optional elements. Feel free to remove any of them.
 status: accepted
 date: 2023-09-19
 deciders: Ourchitecture
@@ -9,7 +8,7 @@ deciders: Ourchitecture
 
 ## Context and Problem Statement
 
-Building on top of the decision ["Use NodeJS scripts for developer task automation"](./dev-tasks-using-node-scripts.md),
+Building on top of the decision ["Use NodeJS scripts for developer task automation"](./script_automation-tasks.md),
 the NodeJS package management offers a handful of unique tool choices.
 
 ## Considered Options

src/docs/decisions/optimize_automation-tasks.md

@@ -1,5 +1,4 @@
 ---
-# These are optional elements. Feel free to remove any of them.
 status: accepted
 date: 2023-09-19
 deciders: Ourchitecture
@@ -21,7 +20,7 @@ Automation can benefit drastically from caching, dependency management, and more
 
 ## Decision Outcome
 
-Building on the decision to [use NodeJS scripts](./dev-tasks-using-node-scripts.md),
+Building on the decision to [use NodeJS scripts](./script_automation-tasks.md),
 Wireit was selected. The team is already familiar with the choice and the
 advantages of Wireit including task dependencies, localized caching as well
 as Continuous Integration caching across independent executions, performance

src/docs/decisions/script_automation-tasks.md

@@ -1,5 +1,4 @@
 ---
-# These are optional elements. Feel free to remove any of them.
 status: accepted
 date: 2023-09-19
 deciders: Ourchitecture