@markjaquith/agency 2.48.0 → 2.49.0

package/src/workbase/AGENTS.md

@@ -43,7 +43,8 @@ reason to edit `agency.json` or `repos/` by hand.
 Require explicit user intent before initializing a workbase; changing repository
 aliases or applying repository setup or workbase sync changes; launching another
 agent from an active agent session; creating a pull request; archiving, restoring,
-dropping, or reopening work; or using `--force` to override readiness.
+dropping, reopening, or completing work without a pull request; or using `--force`
+to override readiness.
 
 ## Safety
 
@@ -80,7 +81,9 @@ release the claim with the current document revision.
 An execution unit remains `working` after implementation is committed and while
 its pull request is open. It becomes `done` only after its authoritative pull
 request is merged and Agency reconciles that state. Do not mark committed or
-review-ready work `done` manually.
+review-ready work `done` manually. A genuine investigation, operational action,
+or no-change result may complete without a pull request only with explicit user
+intent, `--no-pull-request`, and a durable outcome summary.
 
 At each closeout trigger (creating or updating a PR, marking it ready, completing
 a refinement loop, or pausing or handing off completed implementation work):
@@ -90,6 +93,8 @@ a refinement loop, or pausing or handing off completed implementation work):
   keep the execution unit `working` through review and merge.
 - After merge, run `agency sync --apply` to reconcile the execution unit to
   `done`.
+- For an approved non-PR outcome, finish an active claim or update unclaimed
+  status with `--no-pull-request --summary <text>` and optional supporting URL.
 - Refresh durable delivery context in `TASK.md` or `PHASE.md`, including recorded
   PR state, current head, diff summary, and verification results after later
   pushes when those details are maintained there.
@@ -100,15 +105,15 @@ a refinement loop, or pausing or handing off completed implementation work):
 `agency integration status` reports `managed`, `drifted`, `customized`, or
 `missing` generated files. Agency keeps these instructions in
 `.agency/AGENTS.md`, and its managed OpenCode config loads them automatically.
-It also installs `.opencode/command/agency.md`, which provides safe `/agency`
-workflows for active OpenCode sessions, a managed server plugin that exposes
-skills from the authoritative writable checkout, and an explicitly registered
-TUI companion providing `/agency-debug` without submitting an LLM prompt.
+It also installs a managed server plugin that exposes skills from the
+authoritative writable checkout and an explicitly registered TUI companion
+providing `/agency-debug` without submitting an LLM prompt.
 The workbase-root `AGENTS.md`, when present, belongs entirely to the workbase
 owner and composes with these instructions through OpenCode's normal discovery.
 `agency integration sync` updates only missing or checksum-safe drifted managed
-files and preserves user-customized files. `agency init` creates the managed
-files, and `agency work` reconciles them before launching an agent.
+files, removes checksum-valid retired artifacts, and preserves user-customized
+files. `agency init` creates the managed files, and `agency work` reconciles them
+before launching an agent.
 
 OpenCode can access the complete workbase tree, but this filesystem permission
 does not expand Agency write authority beyond the checkout reported by

package/src/workbase/completion.ts

@@ -0,0 +1,28 @@
+import type { CompletionRecord } from "./schemas"
+
+export interface NonPrCompletionInput {
+	readonly summary: string
+	readonly evidenceUrl?: string
+}
+
+export const buildNonPrCompletion = (
+	input: NonPrCompletionInput,
+	now: Date,
+): { readonly value: CompletionRecord } | { readonly error: string } => {
+	const summary = input.summary.trim()
+	if (!summary) return { error: "Non-PR completion summary must not be empty" }
+
+	const evidenceUrl = input.evidenceUrl?.trim()
+	if (evidenceUrl && !/^[a-zA-Z][a-zA-Z0-9+.-]*:/.test(evidenceUrl)) {
+		return { error: `Invalid completion evidence URL: ${evidenceUrl}` }
+	}
+
+	return {
+		value: {
+			mode: "non-pr",
+			completedAt: now.toISOString(),
+			summary,
+			...(evidenceUrl ? { evidenceUrl } : {}),
+		},
+	}
+}

package/src/workbase/schemas.ts

@@ -75,6 +75,13 @@ export const PullRequestRecord = Schema.Struct({
 	mergeable: Schema.optional(Schema.NullOr(Schema.Boolean)),
 })
 
+export const CompletionRecord = Schema.Struct({
+	mode: Schema.Literal("non-pr"),
+	completedAt: IsoTimestamp,
+	summary: NonEmptyString,
+	evidenceUrl: Schema.optional(Url),
+})
+
 const DeliveryProvider = Schema.Struct({
 	provider: EntityId,
 	remote: Schema.optional(NonEmptyString),
@@ -141,6 +148,7 @@ const ExecutionUnit = {
 	pr: Schema.NullOr(Schema.Union(GitHubPullRequestUrl, PullRequestRecord)),
 	status: Schema.optionalWith(WorkStatus, { default: () => "open" as const }),
 	claim: Schema.optional(ClaimRecord),
+	completion: Schema.optional(CompletionRecord),
 }
 
 export const EpicFrontmatter = Schema.Struct({
@@ -187,6 +195,7 @@ export type RepositoryDeclaration = Schema.Schema.Type<
 export type WorkStatus = Schema.Schema.Type<typeof WorkStatus>
 export type ClaimRecord = Schema.Schema.Type<typeof ClaimRecord>
 export type PullRequestRecord = Schema.Schema.Type<typeof PullRequestRecord>
+export type CompletionRecord = Schema.Schema.Type<typeof CompletionRecord>
 export type EpicFrontmatter = Schema.Schema.Type<typeof EpicFrontmatter>
 export type TaskFrontmatter = Schema.Schema.Type<typeof TaskFrontmatter>
 export type PhaseFrontmatter = Schema.Schema.Type<typeof PhaseFrontmatter>

package/src/workbase/AGENCY_COMMAND.md

@@ -1,48 +0,0 @@
----
-description: Operate Agency work with safe start, status, next, validate, and finish workflows
----
-
-Operate the current Agency workbase using the managed Agency instructions.
-
-Invocation inputs:
-
-- Workflow: `$1`
-- Optional target: `$2`
-- Complete request: `$ARGUMENTS`
-
-Use `status` when the workflow is empty. Treat words after the optional target as
-additional user instructions. If the workflow is unknown, make no changes and
-list the supported workflows.
-
-Always follow these rules:
-
-- Run `agency context . --json` first when no target is provided. With a target,
-  pass that target to `agency context` instead.
-- Use the returned document paths, readiness, authority, checkout state, claim,
-  and validation result. Do not infer them from directory names.
-- Stop on validation errors, dependency blockers, an unexpected writable
-  repository, or a conflicting active claim.
-- Write code only in `authority.writable.checkoutPath`; references are read-only.
-- Never run `agency work` to start the current agent again.
-- Create a pull request only when the complete request explicitly asks for one.
-
-Dispatch the workflow as follows:
-
-- `start`: Read the returned task and phase documents, inspect the writable
-  checkout, then begin or resume the requested work in this session. Keep durable
-  decisions current and carry the work through focused verification.
-- `status`: Make no changes. Summarize the target, readiness, authority, durable
-  status, claim and PR state, checkout state, current Git changes, blockers, and
-  the most useful next action.
-- `next`: Run `agency next --json`, summarize ready and blocked execution units,
-  and recommend the highest-priority ready unit. Do not launch another agent.
-- `validate`: Run Agency validation for the discovered workbase. Explain every
-  issue and, when safe and within authority, repair requested non-structural
-  problems before validating again.
-- `finish`: Complete any remaining requested implementation first. Run focused
-  repository checks, refresh the task or phase delivery context, and run
-  `agency validate`. Finish an active claim with its current revision; otherwise
-  update unclaimed status only when the requested outcome and delivery work are
-  actually complete. Do not create a PR unless explicitly requested.
-- `help`: Make no changes. Briefly explain these workflows and the positional
-  form `/agency <workflow> [target] [additional instructions]`.

package/src/workbase/opencode-command-file.ts

@@ -1,30 +0,0 @@
-import { createHash } from "node:crypto"
-import commandTemplate from "./AGENCY_COMMAND.md" with { type: "text" }
-
-const managedHeaderPattern =
-	/^---\r?\n# agency-managed: sha256=([a-f0-9]{64})\r?\n/
-
-const checksum = (content: string) =>
-	createHash("sha256").update(content).digest("hex")
-
-const canonicalBody = commandTemplate.endsWith("\n")
-	? commandTemplate
-	: `${commandTemplate}\n`
-
-const renderManagedWorkbaseOpencodeCommand = (
-	content: string = canonicalBody,
-) =>
-	content.replace(
-		/^---\n/,
-		`---\n# agency-managed: sha256=${checksum(content)}\n`,
-	)
-
-export const managedWorkbaseOpencodeCommand =
-	renderManagedWorkbaseOpencodeCommand()
-
-export const canUpdateManagedWorkbaseOpencodeCommand = (content: string) => {
-	const match = content.match(managedHeaderPattern)
-	if (!match?.[1]) return false
-
-	return checksum(content.replace(managedHeaderPattern, "---\n")) === match[1]
-}