coding-agent-harness 1.0.2 → 1.0.4

package/skills/preset-creator/references/complex-task-skeleton/task_plan.md

@@ -0,0 +1,111 @@
+# [Task Name]
+
+Task Contract: harness-task/v1
+
+## Goal
+
+[State the outcome this task must deliver in one sentence.]
+
+## Scope
+
+- In scope: [specific files, modules, behavior, or docs]
+- Out of scope: [explicit exclusions]
+
+## Task Budget
+
+| Budget | Use When | Required Structure |
+| --- | --- | --- |
+| simple | One owner, no subagent, L0/L1 evidence, no formal review gate | `brief.md`, `task_plan.md`, `visual_map.md`, `progress.md` |
+| standard | Normal feature, fix, or documentation change | `brief.md`, `task_plan.md`, `execution_strategy.md`, `visual_map.md`, `findings.md`, `lesson_candidates.md`, `progress.md`, `review.md` |
+| complex | Multi-hour work, L2/L3 evidence, subagent/reviewer, or optional artifact/reference indexes | Standard files plus `references/INDEX.md` and `artifacts/INDEX.md` |
+
+Selected budget: {{TASK_BUDGET}}
+
+## Context Packet
+
+| ID | Type | Path | Why It Matters | Used By |
+| --- | --- | --- | --- | --- |
+| C-001 | public-doc / private-plan / external / code | PUBLIC:path or PRIVATE:path or TARGET:path or URL:https://example.com | [why this source matters] | coordinator / reviewer / worker |
+
+## Required Files
+
+Do not hand-copy this template to create task directories. Use `harness new-task`
+so the selected budget creates the correct file set and `harness check` can
+enforce it.
+
+| Budget | Required Files |
+| --- | --- |
+| simple | `brief.md`, `task_plan.md`, `visual_map.md`, `progress.md` |
+| standard | simple files plus `execution_strategy.md`, `findings.md`, `lesson_candidates.md`, `review.md` |
+| complex | standard files plus `references/INDEX.md`, `artifacts/INDEX.md` |
+| long-running add-on | `long-running-task-contract.md` when `--long-running` is selected |
+
+Optional subdirectories are created only when triggered:
+
+- `lessons/LC-*.md`: task-local detail artifacts for lesson candidates marked `needs-promotion`.
+- `references/INDEX.md`: complex-task source package and reference index.
+- `artifacts/INDEX.md`: complex-task generated evidence and artifact index.
+
+File purposes:
+
+| Contract File | Purpose |
+| --- | --- |
+| `brief.md` | Human-readable task summary and current context packet |
+| `task_plan.md` | Goal, scope, budget, acceptance, and operating decisions |
+| `execution_strategy.md` | Operating model, allocation, conflict control, and evidence strategy |
+| `visual_map.md` | Diagram collection: phase map, optional architecture/sequence/data-flow/state diagrams, completion state, evidence state, and blocking risk |
+| `progress.md` | Execution log, decisions, and handoff |
+| `findings.md` | Findings, research notes, and unresolved risks |
+| `lesson_candidates.md` | Task-local lesson candidate queue. Human review must accept no-candidate, reject candidates, or queue promotion before review confirmation |
+| `lessons/LC-*.md` | Optional task-local lesson detail artifacts written while source context is fresh and linked from `Detail Artifact` |
+| `review.md` | Agent review submission, adversarial review, or specialist review report |
+| `references/INDEX.md` | Complex-task source package and reference index |
+| `artifacts/INDEX.md` | Complex-task generated evidence and artifact index |
+| `long-running-task-contract.md` | Continuous execution permission, loop rules, and stop conditions |
+
+## Steps
+
+1. [First concrete step]
+2. [Second concrete step]
+3. [Third concrete step]
+
+## Acceptance Criteria
+
+- [ ] [Observable criterion]
+- [ ] [Verification criterion]
+- [ ] [Documentation or handoff criterion]
+
+## Worktree
+
+- Path: [worktree path or n/a]
+- Branch: [branch or n/a]
+- Worker owner: coordinator / subagent id / n/a
+- Worker handoff commit required: yes / no / n/a
+- If no worktree, reason: [reason]
+
+## Long-Running Task Decision
+
+- Long-running task: yes / no
+- Contract file if yes: `long-running-task-contract.md`
+- Continuous execution permission: granted / not granted / n/a
+- Stop condition summary: [one sentence]
+
+## Review Decision
+
+- Adversarial review required: yes / no
+- Report file if yes: `review.md`
+- Reviewer: self / subagent / external / human / n/a
+- No-finding requirement: [requirement or n/a]
+
+## Links
+
+- Related Regression Gate: [reference]
+- Review Report: [path / n/a]
+- Generated Ledger: rebuilt by lifecycle CLI / `harness governance rebuild`
+- Prerequisite tasks: [reference or none]
+
+## Coordinator Handoff
+
+- Global sync owner: coordinator / n/a
+- Global sync status: pending-coordinator-pass / synced / n/a
+- Shared updates needed: [Module Registry / Harness Ledger / Closeout SSoT / Regression SSoT / none]

package/skills/preset-creator/references/complex-task-skeleton/visual_map.md

@@ -0,0 +1,50 @@
+# [Task Name] - Visual Map
+
+Visual Map Contract: v1.0
+
+This file is the task's diagram collection. It is not only a phase roadmap.
+Include only diagrams that materially help a human or agent understand the task.
+
+## Map Index
+
+| ID | Type | Purpose | Required For Understanding | Source Evidence | Promotion Candidate |
+| --- | --- | --- | --- | --- | --- |
+| MAP-01 | phase | Show the execution phases and dependencies | yes | `task_plan.md` | no |
+
+## Phase Graph
+
+```mermaid
+flowchart LR
+  PH01["PH-01 Plan"] --> PH02["PH-02 Implement"]
+  PH02 --> PH03["PH-03 Verify"]
+  PH03 --> PH04["PH-04 Review and Closeout"]
+```
+
+## Phase Table
+
+| Phase ID | Depends On | State | Completion | Output | Required Evidence | Evidence Status | Blocking Risk | Owner / Handoff |
+| --- | --- | --- | ---: | --- | --- | --- | --- | --- |
+| PH-01 | none | planned | 0 | Approved task plan and execution strategy | `task_plan.md`, `execution_strategy.md` | missing | none | coordinator |
+| PH-02 | PH-01 | planned | 0 | Scoped implementation or document update | diff, worker handoff, or artifact path | missing | [risk] | [owner] |
+| PH-03 | PH-02 | planned | 0 | Verification evidence | commands, logs, screenshots, or runtime proof | missing | [risk] | [owner] |
+| PH-04 | PH-03 | planned | 0 | Review disposition and closeout updates | `review.md`, progress update, ledger updates | missing | [risk] | coordinator |
+
+Allowed Evidence Status: missing, partial, present, waived.
+
+## Supporting Maps
+
+Add optional diagrams only when useful:
+
+- architecture: module, component, or service structure.
+- sequence: frontend/backend/service/database/agent interaction.
+- data-flow: data movement and ownership.
+- state: state machine or lifecycle.
+- topology: repo, service, worker, or worktree layout.
+- decision: branch and tradeoff tree.
+
+## Map Notes
+
+- Use `missing` when no evidence has been checked.
+- Use `partial` when some evidence exists but required checks remain.
+- Use `present` when the phase has sufficient evidence for its current claim.
+- Use `waived` only when the reason and owner are recorded in `progress.md`.

package/skills/preset-creator/references/preset-package-skeleton.md

@@ -0,0 +1,296 @@
+# Preset Package Skeleton
+
+Use this reference when creating a Coding Agent Harness preset package. Start from the smallest useful subset, then delete files and manifest sections the preset does not need.
+
+Before designing a complex-task preset, inspect `references/complex-task-skeleton/`. That folder shows the base task contract the preset overlays. Presets should add method-specific context and resources; they should not silently replace the complex task skeleton itself.
+
+## Copyable Package Tree
+
+```text
+my-preset/
+  preset.yaml
+  templates/
+    task_plan.append.md
+    references/
+      upstream-contract.md
+  resources/
+    service-runbook.md
+    artifacts/
+      input-packet.md
+```
+
+## Complete Reference Bundle Manifest
+
+```yaml
+id: service-context
+version: 1
+purpose: Create tasks with shared upstream service context
+compatibleBudgets: [complex]
+localeSupport: [en-US]
+task:
+  kind: service-integration
+  defaultTaskId: service-integration-task
+entrypoints:
+  newTask:
+    type: template
+    writes: [docs/09-PLANNING/TASKS/**]
+    audit: true
+    templates:
+      taskPlanAppend: templates/task_plan.append.md
+inputs:
+  service:
+    type: text
+    flag: --service
+    required: true
+templateValues:
+  service:
+    from: inputs.service
+metadata:
+  UpstreamService:
+    label: Upstream Service
+    from: inputs.service
+resources:
+  references:
+    upstreamContract:
+      path: references/upstream-contract.md
+      template: templates/references/upstream-contract.md
+      index:
+        id: REF-001
+        type: code
+        summary: Shared upstream {{service}} contract for every task created by this preset.
+        usedBy: coordinator,worker,reviewer
+    serviceRunbook:
+      path: references/service-runbook.md
+      source: resources/service-runbook.md
+      index:
+        id: REF-002
+        type: runbook
+        summary: Local verification notes for the shared upstream service.
+        usedBy: worker
+  artifacts:
+    inputPacket:
+      path: artifacts/input-packet.md
+      source: resources/artifacts/input-packet.md
+      index:
+        id: ART-001
+        type: fixture
+        summary: Shared fixture packet copied by the preset.
+        producedBy: preset
+context:
+  requiredReads: [REF-001, REF-002]
+evidence:
+  bundleDir: artifacts/preset
+  files:
+    subject:
+      path: subject.txt
+      type: text
+      value: inputs.subject
+audit:
+  manifestRequired: true
+  evidenceFiles: [preset-audit.json, preset-manifest.json, write-scope.json]
+writeScopes:
+  taskDocs:
+    path: docs/09-PLANNING/TASKS/**
+    access: write
+```
+
+## Starter Files
+
+### `templates/task_plan.append.md`
+
+```markdown
+## Preset Context
+
+This task depends on {{service}}. Read the preset required references before implementation and cite any behavior that changes the integration contract.
+```
+
+### `templates/references/upstream-contract.md`
+
+```markdown
+# {{service}} Contract
+
+## Purpose
+
+Record the contract details that every task created by this preset must understand before implementation.
+
+## Required Context
+
+- Service owner:
+- Local path or repository:
+- API, event, or data boundary:
+- Compatibility constraints:
+- Known test or smoke command:
+
+## Open Questions
+
+- [question]
+```
+
+### `resources/service-runbook.md`
+
+```markdown
+# Service Runbook
+
+## Local Setup
+
+- Command:
+- Required environment:
+- Health check:
+
+## Verification Notes
+
+- Integration smoke:
+- Known failure mode:
+```
+
+### `resources/artifacts/input-packet.md`
+
+```markdown
+# Input Packet
+
+## Fixture Purpose
+
+Describe why this shared input packet exists and which tasks should use it.
+
+## Contents
+
+- [fixture or packet item]
+```
+
+## Minimal Non-Resource Preset
+
+Use this smaller manifest when the preset only needs metadata, task-plan guidance, and audit evidence.
+
+```yaml
+id: custom-review
+version: 1
+purpose: Create a custom review task
+compatibleBudgets: [standard, complex]
+localeSupport: [en-US]
+task:
+  kind: review-task
+  defaultTaskId: custom-review-task
+entrypoints:
+  newTask:
+    type: template
+    writes: [docs/09-PLANNING/TASKS/**]
+    audit: true
+    templates:
+      taskPlanAppend: templates/task_plan.append.md
+inputs:
+  subject:
+    type: text
+    flag: --subject
+    required: true
+templateValues:
+  subject:
+    from: inputs.subject
+metadata:
+  ReviewSubject:
+    label: Review Subject
+    from: inputs.subject
+evidence:
+  bundleDir: artifacts/preset
+audit:
+  manifestRequired: true
+  evidenceFiles: [preset-audit.json, preset-manifest.json, write-scope.json]
+writeScopes:
+  taskDocs:
+    path: docs/09-PLANNING/TASKS/**
+    access: write
+```
+
+## File And Field Rules
+
+- `id` uses lowercase letters, numbers, and hyphens only.
+- Supported `inputs.*.type` values are `text`, `flag`, and `json-file`.
+- `entrypoints.newTask.writes` entries must exactly match declared `writeScopes.*.path` entries.
+- `path` for references must stay under `references/`.
+- `path` for artifacts must stay under `artifacts/`.
+- Do not target `references/INDEX.md`, `artifacts/INDEX.md`, `task_plan.md`, or any canonical task contract file.
+- `source` and `template` must point to files inside the preset package, not directories.
+- Resource `index.id` values must be unique inside references or artifacts.
+- Resource destination paths must be unique across references and artifacts.
+- `context.requiredReads` can only list declared reference IDs.
+- `context.requiredReads` generates `## Preset Required Reads` in `task_plan.md`; each generated row must contain the reference ID and the exact `TARGET:<task-relative-reference-path>`.
+- `evidence.bundleDir` names the task-local audit/evidence directory; `evidence.files` is an optional mapping of named custom evidence declarations, while `audit.evidenceFiles` names built-in audit files.
+- Do not write `evidence.files` as an array. Each custom evidence file must be a mapping with `path`, `type`, and `value`.
+- Supported custom evidence types are `text`, `json`, `input-json`, `preset-audit`, `preset-manifest`, `write-scope`, `migration-verify`, `migration-ledger`, `dashboard-hash`, `target-git-status`, `target-commit`, `harness-version`, and `generated-at`.
+- Resource `index.type`, `usedBy`, and `producedBy` are reader-facing labels, not strict enums. Prefer stable simple words: `code`, `doc`, `runbook`, `fixture`, `preset`, `coordinator`, `worker`, `reviewer`.
+- Keep `entrypoints.newTask.type` as `template`; do not add JavaScript for task creation.
+- Keep `writeScopes` narrow and task-doc scoped.
+
+## Custom Evidence Shape
+
+Use a mapping, not an array:
+
+```yaml
+evidence:
+  bundleDir: artifacts/preset
+  files:
+    subject:
+      path: subject.txt
+      type: text
+      value: inputs.subject
+    resolvedInputs:
+      path: resolved-inputs.json
+      type: json
+      value: inputs
+audit:
+  manifestRequired: true
+  evidenceFiles: [preset-audit.json, preset-manifest.json, write-scope.json]
+```
+
+This creates named files under the generated task's preset evidence bundle. Arrays such as `evidence.files: [summary.json]` are invalid.
+
+## Generated Required Reads Shape
+
+For a declared reference like:
+
+```yaml
+resources:
+  references:
+    upstreamContract:
+      path: references/upstream-contract.md
+      index:
+        id: REF-001
+context:
+  requiredReads: [REF-001]
+```
+
+The generated `task_plan.md` must include:
+
+```markdown
+## Preset Required Reads
+
+Open `references/INDEX.md`, then read these preset-provided references before implementation.
+
+| Reference | Path | Why |
+| --- | --- | --- |
+| REF-001 | TARGET:docs/09-PLANNING/TASKS/<task-folder>/references/upstream-contract.md | [rendered summary] |
+```
+
+The same `REF-001` and exact `TARGET:` path must also appear in `references/INDEX.md`.
+
+## Verification Checklist
+
+Run these commands in an isolated HOME or disposable target:
+
+```bash
+harness preset check ./my-preset
+harness preset install ./my-preset --force
+harness init --locale en-US --capabilities core /tmp/preset-target
+harness new-task first-api --budget complex --preset service-context --service payment-service /tmp/preset-target
+harness new-task second-api --budget complex --preset service-context --service payment-service /tmp/preset-target
+harness status --json /tmp/preset-target
+harness task-index --json /tmp/preset-target
+harness check --profile target-project /tmp/preset-target
+```
+
+Manually inspect both created tasks:
+
+- `task_plan.md` includes preset metadata and `## Preset Required Reads`.
+- `references/INDEX.md` includes every `REF-*` row with a concrete `TARGET:` path.
+- `artifacts/INDEX.md` includes every `ART-*` row with a concrete `TARGET:` path.
+- The copied or rendered reference files exist under each task directory.
+- Evidence bundles are independent per task.

package/templates/AGENTS.md.template

@@ -19,7 +19,7 @@ Keep it as a charter and routing index. Detailed rules belong in
 3. Start non-trivial work with a task directory under `docs/09-PLANNING/TASKS/`.
 4. Record evidence before claiming completion.
 5. Protect unrelated working-tree changes; never revert files outside the assigned scope.
-6. Commit verified, meaningful work slices unless the user explicitly says not to commit.
+6. Commit verified, meaningful work slices proactively. Do not leave completed work only as dirty files unless the user explicitly pauses commits, checks fail, dirty ownership is unclear, or a security boundary prevents a clean commit; in those cases record the no-commit reason, owner, and next step in progress, handoff, or closeout notes. Never mix unrelated dirty changes into a task commit.
 
 ## Reading Matrix
 
@@ -32,7 +32,7 @@ Read the smallest context that can answer the task.
 | Local development, mocks, stubs, or cross-repo debugging | `docs/04-DEVELOPMENT/README.md`, `docs/04-DEVELOPMENT/codebase-map.md` |
 | API, event, webhook, SDK, or third-party contract | `docs/06-INTEGRATIONS/README.md` and the related contract file |
 | Tests, smoke, or regression | `docs/11-REFERENCE/testing-standard.md`, `docs/05-TEST-QA/Regression-SSoT.md` |
-| Execution, commit, PR, or release work | `docs/11-REFERENCE/execution-workflow-standard.md`, `docs/11-REFERENCE/repo-governance-standard.md`, `docs/11-REFERENCE/ci-cd-standard.md` |
+| Execution, commit, PR, or release work | `docs/11-REFERENCE/execution-workflow-standard.md`, `docs/11-REFERENCE/repo-governance-standard.md`, `docs/11-REFERENCE/pull-request-standard.md`, `docs/11-REFERENCE/ci-cd-standard.md` |
 | Creating or advancing a task | Current task directory under `docs/09-PLANNING/TASKS/`; use the Harness CLI if this project has it configured |
 | Brief, Execution Strategy, or Visual Map | Current task `brief.md`, `execution_strategy.md`, and `visual_map.md` |
 | Long-running task | `docs/11-REFERENCE/long-running-task-standard.md` |
@@ -42,37 +42,41 @@ Read the smallest context that can answer the task.
 | Documentation governance or Harness update | `docs/11-REFERENCE/docs-library-standard.md`, `.harness-capabilities.json` |
 | External source material intake | `docs/11-REFERENCE/external-source-intake-standard.md` |
 | Regression SSoT maintenance | `docs/11-REFERENCE/regression-ssot-governance.md` |
-| Walkthrough, closeout, or lessons | `docs/11-REFERENCE/walkthrough-standard.md`, `docs/10-WALKTHROUGH/Closeout-SSoT.md`, `docs/01-GOVERNANCE/Lessons-SSoT.md` |
+| Walkthrough, closeout, or lessons | `docs/11-REFERENCE/walkthrough-standard.md`, `docs/10-WALKTHROUGH/Closeout-SSoT.md`, current task `lesson_candidates.md`, `docs/01-GOVERNANCE/lessons/` |
 | Worktree operations | `docs/11-REFERENCE/worktree-standard.md` |
 
 ## Standard Execution Flow
 
 1. Confirm the request, scope, and affected files.
 2. For non-trivial work, create or update the task plan before editing code.
-3. Load only the reference documents required by the Reading Matrix.
-4. Preserve existing project facts; merge new context instead of overwriting history.
-5. Use a worktree or branch when the task requires isolation or parallel work.
-6. Implement only within the approved scope.
-7. Run the relevant checks and capture evidence in the task records.
-8. Route required review and close blocking findings.
-9. Write or update the walkthrough and closeout records.
-10. Update SSoT / ledger files that the task actually touched.
+3. Assess delegation from the user's goal; users do not need to know or ask for subagents.
+4. Load only the reference documents required by the Reading Matrix.
+5. Preserve existing project facts; merge new context instead of overwriting history.
+6. Use a worktree or branch when the task requires isolation or parallel work.
+7. Implement only within the approved scope.
+8. Run the relevant checks and capture evidence in the task records.
+9. Route required review and close blocking findings.
+10. Write or update the walkthrough and closeout records.
+11. Update SSoT / ledger files that the task actually touched.
 
 ## Coordination Rules
 
-- Reviewers are read-only unless explicitly assigned a write scope.
-- Workers may edit only their assigned branch, worktree, and file scope.
+- At task start, read the current task `execution_strategy.md` Subagent Authorization and Subagent Delegation Decision sections, then state whether reviewer or worker subagents should be used; do this even when the user only states the desired outcome.
+- Reviewer subagents are allowed by default for read-only review within the current task.
+- If a worker subagent would materially help and is not authorized, proactively ask the user once in plain language for task/scope/worktree authorization; it is fine to say "worker subagent", but do not wait for the user to know or suggest subagents.
+- If independent slices are obvious but exact file paths are not, identify the file paths first and then immediately ask for independent-execution-helper authorization before implementation.
+- Worker subagents require one user authorization recorded in `execution_strategy.md`; after that, reuse is allowed only within the same task, scope, and worktree/branch.
 - Shared ledgers, registries, and SSoT files are coordinator-owned unless a lock is explicitly assigned.
 - Worker handoff must include branch or worktree, changed files, checks, evidence, and residual risks.
 
 ## Single Sources Of Truth
 
-- Feature SSoT: `docs/09-PLANNING/Feature-SSoT.md`
 - Delivery SSoT: `docs/09-PLANNING/Delivery-SSoT.md`
 - Module Registry: `docs/09-PLANNING/Module-Registry.md`
 - Regression SSoT: `docs/05-TEST-QA/Regression-SSoT.md`
 - Cadence Ledger: `docs/05-TEST-QA/Cadence-Ledger.md`
-- Lessons SSoT: `docs/01-GOVERNANCE/Lessons-SSoT.md`
+- Lesson Candidates: current task `lesson_candidates.md`
+- Lesson Detail Docs: `docs/01-GOVERNANCE/lessons/`
 - Closeout SSoT: `docs/10-WALKTHROUGH/Closeout-SSoT.md`
 - Harness Ledger: `docs/Harness-Ledger.md`
 

package/templates/dashboard/assets/app-src/00-state.js

@@ -15,6 +15,7 @@ const state = {
   renderMode: "rendered",
   theme: localStorage.getItem("harness.theme") || "system",
   taskLayout: localStorage.getItem("harness.taskLayout") || "list",
+  taskSortOrder: localStorage.getItem("harness.taskSortOrder") === "asc" ? "asc" : "desc",
   runtime: { mode: "static", csrfToken: "", writableActions: [] },
   runtimeLoaded: false,
   runtimePoller: null,

package/templates/dashboard/assets/app-src/10-router.js

@@ -71,6 +71,7 @@ function currentRoute() {
 }
 
 function routeLink(hash, text, routeName) {
-  const active = currentRoute().name === routeName;
+  const current = currentRoute().name;
+  const active = current === routeName || (routeName === "review" && current === "reviewTask");
   return `<a class="${active ? "active" : ""}" href="${hash}">${escapeHtml(text)}</a>`;
 }

package/templates/dashboard/assets/app-src/20-overview.js

@@ -165,24 +165,29 @@ function graphSummary() {
 }
 
 function activeTaskBriefs() {
-  const tasks = activeTasks().slice(0, 8);
+  const tasks = activeTasks();
   return `<section class="task-briefs">
     <div class="section-head">
       <div>
         <p class="eyebrow">${t("currentWork")}</p>
         <h2>${t("activeBriefs")}</h2>
       </div>
-      <a href="#/tasks">${t("openTaskIndex")}</a>
+      <div class="section-actions">
+        <span class="subtle">${t("activeBriefCount").replace("{count}", tasks.length).replace("{order}", taskSortLabel())}</span>
+        <a href="#/tasks">${t("openTaskIndex")}</a>
+      </div>
+    </div>
+    <div class="brief-scroll">
+      <div class="brief-grid">${tasks.map((task) => taskBriefCard(task, { compact: false })).join("") || emptyState(t("noActiveTasks"))}</div>
     </div>
-    <div class="brief-grid">${tasks.map((task) => taskBriefCard(task, { compact: false })).join("") || emptyState(t("noActiveTasks"))}</div>
   </section>`;
 }
 
 function activeTasks() {
   const tasks = bundle.status?.tasks || [];
   const active = tasks.filter((task) => isActiveTaskState(task.state) || ["planned", "not_started"].includes(task.state));
-  if (active.length > 0) return active;
-  return tasks.filter((task) => task.briefSource === "standalone").slice(0, 6);
+  if (active.length > 0) return sortTasksByTime(active);
+  return sortTasksByTime(tasks.filter((task) => task.briefSource === "standalone"));
 }
 
 function isActiveTaskState(state) {
@@ -205,6 +210,7 @@ function taskBriefCard(task, { compact = true } = {}) {
       <p class="brief-teaser">${escapeHtml(summaryText)}</p>
     </div>
     <div class="card-actions">
+      ${taskCopyButton(task)}
       <button class="btn-drawer-trigger" data-open-drawer="${escapeAttr(task.id)}">${t("viewDetails")}</button>
     </div>
   </article>`;