From 980e3952f094a98183c505f365d5cdff540d8bc4 Mon Sep 17 00:00:00 2001 From: Robert Gruen Date: Mon, 2 Nov 2026 23:08:22 -0700 Subject: [PATCH] docs: record verified automation pilot milestones Record selected completion-receipt live tests, owner acceptance/build acknowledgments, and successful Issue #75 App publication followed by human fixes, review, and merge. Preserve the original automated evidence, existing assessment snapshots, default-off activation, separate budgets, and unverified-path limitations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- AUTOMATION.md | 101 +++++++++++++++++++++++++++++++++++--------- OWNER-CHEATSHEET.md | 60 ++++++++++++++++---------- README.md | 33 ++++++++++----- 3 files changed, 142 insertions(+), 52 deletions(-) diff --git a/AUTOMATION.md b/AUTOMATION.md index 00ce17ac..6a491b65 100644 --- a/AUTOMATION.md +++ b/AUTOMATION.md @@ -20,7 +20,7 @@ is available today. ## Status and implementation history -**Last updated: 2026-11-01 (UTC).** The read-only +**Last updated: 2026-11-03 (UTC).** The read-only [Backlog assessment workflow](https://github.com/microsoft/TypeChat/actions/workflows/backlog-assessment.lock.yml) is available for manual dispatch on `main`. The [latest run](https://github.com/microsoft/TypeChat/actions/runs/40997369231) @@ -38,10 +38,17 @@ reviews are now enabled through a separate repository rule; broader autonomy is not enabled. The [owner-approved discussion pilot](#second-pilot-owner-approved-discussion-drafts) has verified Issue draft-only, direct-reply, and duplicate-free reply retry runs. -Manual response publication and the Discussion path remain unverified live. +Selected Issue and Discussion draft receipts, invalid-command reporting, and +controller-only no-op retries are now +[live-verified](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916). +Manual response publication, Discussion replies, and Discussion acceptance +remain unverified live. [Exact owner work acceptance](#exact-work-acceptance) and its no-op retry are -live-verified on an Issue. [Completion receipts](#completion-receipts) are -prepared for review, not activated or live-verified. +live-verified on an Issue. The separately owner-authorized +[Issue implementation pilot](#third-pilot-owner-triggered-issue-implementation) +published [#513](https://github.com/microsoft/TypeChat/pull/513), which received +normal CI, Copilot review, owner-approved follow-up fixes, and human approval +and merge. Its activation flag is unset; broader autonomy is not enabled. | Implemented | Change | Current state | | --- | --- | --- | @@ -68,8 +75,10 @@ prepared for review, not activated or live-verified. | 2026-10-30 | [Owner-approved issue and Discussion drafts](#second-pilot-owner-approved-discussion-drafts) | Merged through [#493](https://github.com/microsoft/TypeChat/pull/493), [#494](https://github.com/microsoft/TypeChat/pull/494), and [#495](https://github.com/microsoft/TypeChat/pull/495). The Issue draft-only path passed in [run 41147057482](https://github.com/microsoft/TypeChat/actions/runs/41147057482) on 2026-10-31 (UTC); this does not verify publication or the Discussion path. | | 2026-10-31 | Conversational responses and `/typechat reply` | Merged through [#498](https://github.com/microsoft/TypeChat/pull/498). [Run 41226698016, attempt 1](https://github.com/microsoft/TypeChat/actions/runs/41226698016/attempts/1) posted one checked Issue response. [Attempt 2](https://github.com/microsoft/TypeChat/actions/runs/41226698016/attempts/2) skipped inference and posting, preserving the original reply. Discussion and manual publication remain unverified live. | | 2026-10-31 | [Exact owner work acceptance](#exact-work-acceptance) | Merged through [#503](https://github.com/microsoft/TypeChat/pull/503). [Run 41339605658, attempt 1](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/1) posted the exact Issue acceptance on 2026-11-01 (UTC); [attempt 2](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/2) skipped the write and preserved the original record. Discussion acceptance remains unverified live. | -| Prepared | [Completion receipts](#completion-receipts) | Close the loop for eyes-acknowledged draft/reply requests without publishing private previews or granting acceptance. Review, merge, and live verification are pending. | -| Not yet | Human-approved agent implementation | Planned with a future 1,000-credit implementation allowance; no build command, implementation workflow, or implementation spending is enabled. | +| 2026-11-02 | [Completion receipts](#completion-receipts) | Merged through [#506](https://github.com/microsoft/TypeChat/pull/506). [Owner-authorized live checks](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916) verified Issue/Discussion input-needed draft receipts, an invalid-command receipt, and controller-only no-op retries; other outcomes and uncertain-write recovery are not claimed live-verified. | +| 2026-11-02 | [Owner-triggered Issue implementation](#third-pilot-owner-triggered-issue-implementation) | Merged through [#507](https://github.com/microsoft/TypeChat/pull/507), default-off. The separately authorized [#220 run](https://github.com/microsoft/TypeChat/actions/runs/41493733655) correctly blocked a candidate that failed strict Pyright checks; manual recovery did not change that failed result. | +| 2026-11-02 | Acceptance and build acknowledgments | Merged through [#510](https://github.com/microsoft/TypeChat/pull/510). A thumbs-up on the [#75 acceptance command](https://github.com/microsoft/TypeChat/issues/75#issuecomment-6592727753) confirmed recorded acceptance; a rocket on the [build command](https://github.com/microsoft/TypeChat/issues/75#issuecomment-6592903964) acknowledged startup, not success. Discussion acknowledgment remains unverified live. | +| 2026-11-03 | [Successful App publication and human review](#successful-app-publication-and-human-review) | [Run 41559378978](https://github.com/microsoft/TypeChat/actions/runs/41559378978) created [#513](https://github.com/microsoft/TypeChat/pull/513). Normal CI and Copilot reviews ran, human follow-up fixes were verified, and the owner approved and merged the PR. Original automated evidence remains bound to its original commit; activation is again unset. | | Not yet | Selective automatic adoption | Future work, after public criteria and maintainer approval. | These are implementation dates, not activation dates. Update this history, @@ -488,13 +497,15 @@ human-review enforcement remain a separate owner decision. ## Second pilot: owner-approved discussion drafts -**Issue direct replies and no-op retries verified on 2026-10-31 (UTC).** +**Issue direct replies and no-op retries verified on 2026-10-31 (UTC); +selected completion receipts verified on 2026-11-02 (UTC).** This pilot provides GitHub-native previews and owner-requested replies for Issues -and Discussions; the Discussion and manual response-publication paths still need -live verification. Issue work acceptance and its no-op retry were verified on -2026-11-01 (UTC). Completion receipts are prepared for review and need a separate -post-merge live check. No command changes labels, -closes threads, starts an implementation run, creates PRs, or merges changes. +and Discussions. Input-needed Issue and Discussion draft outcomes and their +receipts were verified in [the owner-authorized checks](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916). +Discussion replies, Discussion acceptance, and manual response publication +still need live verification. Issue work acceptance and its no-op retry were +verified on 2026-11-01 (UTC). These discussion commands do not change labels, +close threads, start an implementation run, create PRs, or merge changes. Existing Copilot PR review remains a separate capability. ### Owner commands @@ -504,7 +515,7 @@ command in a **new comment**, with no additional text: | Command | Authorization and result | | --- | --- | -| `/typechat draft` | Prepare a conversational reply and, when ready, a work-acceptance preview; do not post either. After receipt rollout, report the operational outcome separately. | +| `/typechat draft` | Prepare a conversational reply and, when ready, a work-acceptance preview; do not post either. Report the operational outcome separately through a trusted receipt. | | `/typechat publish :` | Approve and post that exact reviewed draft. | | `/typechat reply` | Authorize one checked advisory reply to be posted without a second approval command. | | `/typechat accept :` | Approve and record the exact proposed scope and criteria. No implementation run or merge is authorized. | @@ -560,12 +571,21 @@ Unclear scope or an item under consideration requires an owner decision. ### Completion receipts -**Prepared for review; not live-verified.** Eyes acknowledge that a draft or -reply request has started. The separate +**Merged through [#506](https://github.com/microsoft/TypeChat/pull/506); +selected outcomes live-verified on 2026-11-02 (UTC).** Eyes acknowledge that a +draft or reply request has started. The separate [outcome workflow](./.github/workflows/discussion-status.yml) waits for the full response workflow to finish, including failures and cancellations, then records one short, trusted operational outcome for the original command. +The [verification report](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916) +records input-needed Issue and Discussion draft receipts, an invalid-command +receipt, and controller-only retries that preserved comment IDs, text hashes, +update timestamps, and counts without another model run. Cancellation, +uncertain-network-write recovery, acceptance-ready wording, and direct-reply +reuse were not exercised live in those checks; offline coverage is not live +evidence for those paths. + The receipt links the owner request and run/preview. Its fixed messages distinguish a prepared proposal, additional input, outdated or unavailable evidence, rejected syntax, failure/cancellation, and an unconfirmed reply. It does not publish the @@ -606,7 +626,7 @@ Delivery is fail-closed, not a guarantee of commenting despite lost permissions or unavailable evidence. Withdrawn/edited requests, closed/locked targets, older run-name formats, and superseded attempts do not receive new comments. If the controller cannot authenticate or verify its inputs, Actions remains the error -channel. Use a new owner command after rollout; rerunning old workflow revisions +channel. Use a new owner command on the current workflow revision; rerunning old workflow revisions does not add the new request binding or receipt behavior. ### Exact work acceptance @@ -642,6 +662,9 @@ before posting one top-level **Accepted work** comment. After confirming that exact record, the publisher adds a thumbs-up reaction to the owner's `/typechat accept` comment, on either an Issue or a Discussion. The reaction confirms recorded acceptance, not merely receipt of the command. +The [#75 owner acceptance command](https://github.com/microsoft/TypeChat/issues/75#issuecomment-6592727753) +received this reaction after its exact record was confirmed on 2026-11-03 (UTC). +Discussion acknowledgment remains unverified live. Rejected approvals and unconfirmed publication outcomes do not receive it. An unchanged, already-published record can also confirm a subsequent valid approval command without creating another acceptance comment. @@ -893,7 +916,7 @@ decisions should be clear and visible. ## Third pilot: owner-triggered Issue implementation -**Default-off; successful automated PR publication is not yet live-verified.** The +**Default-off; successful App PR publication verified on 2026-11-03 (UTC).** The [accepted agreement for #504](https://github.com/microsoft/TypeChat/issues/504#issuecomment-6562465109) authorizes development of this workflow, not an automated coding run. The new [workflow](./.github/workflows/issue-implementation.md) requires @@ -930,6 +953,40 @@ blocked, and the temporary activation flag was removed. Native usage was of a failing candidate, not successful automated PR creation. Manual recovery of that candidate does not change the failed run's outcome. +### Successful App publication and human review + +On 2026-11-03 (UTC), the separately owner-authorized +[#75 run](https://github.com/microsoft/TypeChat/actions/runs/41559378978) +completed preparation, coding, full-patch detection, isolated checks, and +trusted publication. It created the App-authored +[#513](https://github.com/microsoft/TypeChat/pull/513) from the exact +[accepted record](https://github.com/microsoft/TypeChat/issues/75#issuecomment-6592736337). +That run used **124.05274 main credits plus 16.76878 detection credits = +140.82152 AI credits**, within the separate 1,000/400 limits. + +Original automated commit +[adcfc932](https://github.com/microsoft/TypeChat/commit/adcfc9323fc2b5afa1130ed6a121c78a5d02a0a8) +remains the revision bound by the original context, candidate, patch, scan, and +isolated-check evidence. Its new metadata tests compiled but were omitted from +the default test selector. Owner-approved human follow-ups registered those +tests, fixed filtered-response error privacy and token-total overflow, and +shipped the metadata guide with a README link. Later test runs actually +executed the metadata suite. The original scan is not claimed to cover those +human changes. + +Normal PR CI and Copilot reviews ran on the original and follow-up revisions. +All 12 checks passed at final head +[1c1abe6](https://github.com/microsoft/TypeChat/commit/1c1abe6f9566ecd7d691596344911ce1f30f83bd); +the owner approved and merged it as +[488c8ef](https://github.com/microsoft/TypeChat/commit/488c8efdcfbb41e44f31c420c84ba2a499f90e20). +Post-merge Node, Python, and Pages runs succeeded. Human review and fixes were +part of this pilot, not automatic approval or merging. + +The temporary activation flag was removed after the authorized run and was +confirmed unset at repository and inherited organization scope on 2026-11-03 +(UTC). This verifies one bounded TypeScript publication path, not broader +autonomy, Discussion implementation, or permission for another coding run. + ### Frozen authorization and bounded spending Preflight verifies owner identity, default-branch workflow code, the current @@ -1022,7 +1079,9 @@ an unpublished or partially published branch requiring human inspection. ### Activation and first live verification -Review and merge the workflow through the ordinary owner process first. +The workflow was merged through the ordinary owner process in +[#507](https://github.com/microsoft/TypeChat/pull/507). Each later activation +still requires a separate owner decision. The existing default token permissions, PR-creation/approval setting, Dependabot workflow, library behavior, and discussion commands stay unchanged. Compiler safe-update approval of the existing App binding is a code-review step, not @@ -1039,8 +1098,10 @@ Record whether the resulting App-created PR actually starts normal CI and receives Copilot review. Neither is claimed successful in advance; both remain separate from human approval and merging. The CI sandbox smoke test uses a synthetic TypeScript/Python patch and no inference or App credentials. It verifies -container behavior, not a live coding run. Discussion-path verification and -receipt rollout remain their separate milestones. +container behavior, not a live coding run. The +[successful #75 publication](#successful-app-publication-and-human-review) +and [selected receipt checks](#completion-receipts) supply separate live +evidence; unverified Discussion paths and receipt outcomes remain separate. ## Existing issues and contributions diff --git a/OWNER-CHEATSHEET.md b/OWNER-CHEATSHEET.md index 75067ce5..dc1fd82b 100644 --- a/OWNER-CHEATSHEET.md +++ b/OWNER-CHEATSHEET.md @@ -1,6 +1,6 @@ # TypeChat owner cheat sheet -**For @robgruen. Last checked: 2026-11-01 (UTC).** +**For @robgruen. Last checked: 2026-11-03 (UTC).** [Issues](https://github.com/microsoft/TypeChat/issues) | [Discussions](https://github.com/microsoft/TypeChat/discussions) | @@ -11,10 +11,17 @@ **Verified:** backlog assessment, automatic Copilot PR reviews, Issue draft generation, Issue `/typechat reply` delivery, and exact Issue `/typechat accept`, including -duplicate-free reruns. -**Awaiting review and live verification:** completion receipts for draft/reply requests. -Manual publication and the Discussion path still need live verification. -**Still human decisions:** work acceptance, implementation handoff, merging, and releases. +duplicate-free reruns. Selected Issue/Discussion draft receipts, invalid-command +reporting, and controller-only no-op retries are +[live-verified](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916). +The separately authorized [#75 coding pilot](./AUTOMATION.md#successful-app-publication-and-human-review) +created [#513](https://github.com/microsoft/TypeChat/pull/513), followed by CI, +Copilot review, human fixes, approval, and merge. +**Still unverified live:** manual response publication, Discussion replies and +acceptance, and receipt cancellation, uncertain-write recovery, +acceptance-ready wording, and direct-reply reuse. +**Coding activation is off. Still human decisions:** work acceptance, each +implementation run, merging, and releases. ## What do I do next? @@ -26,7 +33,7 @@ Manual publication and the Discussion path still need live verification. | Post the proposed response | Review the exact draft, then copy its publish command into the same thread. | One Actions-bot comment, not approval to build. | | Accept an agent-prepared proposal | [Review and approve its exact terms](#accept-an-exact-proposal), or [record a human decision manually](#accept-work-manually). The Issue path is live-verified. | A visible scope agreement; no coding agent starts automatically. | | Move an existing PR forward | [Review the latest revision](#review-and-merge-manually); support the existing contributor rather than duplicate their PR. | A human decision to request changes or merge. | -| Prepare one bounded coding run | After review/rollout, [prepare its exact build command](#prepare-an-implementation-run-disabled-by-default). | A copyable command, not spending or merge approval. | +| Prepare one bounded coding run | [Prepare its exact build command](#prepare-an-implementation-run-disabled-by-default), then obtain separate owner authorization for that run. | A copyable command, not spending or merge approval. | | Resolve unclear or out-of-scope work | Pause dependent work. If changing direction, approve and merge a [policy PR](./GOALS.md#who-decides) first. | An explicit scope decision; popularity or a label is not approval. | ## Refresh the backlog (live) @@ -66,11 +73,12 @@ doing anything else. Do not delete its intent artifact or retry blindly. ## Draft and publish -**Draft generation is live-verified on Issues; manual publication is not.** +**Issue drafts and selected input-needed Discussion draft outcomes are +live-verified; manual publication is not.** Follow the [rollout checklist](./AUTOMATION.md#first-live-verification) for an owner-approved publication test. -Once enabled, use your **@robgruen** account on an **open, unlocked issue or +Use your **@robgruen** account on an **open, unlocked issue or Discussion**, not a PR. Each command must be a **new comment containing only the command**, with no leading text. Editing an old comment does not trigger it. @@ -84,8 +92,8 @@ The Actions bot acknowledges the command comment with an `eyes` reaction when the workflow starts processing it. This is not a success or acceptance signal; check Actions for progress and errors. -After completion-receipt rollout, a short status comment will link the run and -say whether the draft is prepared, needs input, is outdated, or failed. The +A short operational receipt links the run and says whether the draft is +prepared, needs input, is outdated, or failed. The receipt is not the drafted response and is not acceptance. It is safe to review the original frozen preview after a canonical receipt appears. @@ -130,9 +138,11 @@ separate check.** This is a real scope decision, not a test acknowledgment. 4. Follow **Publish approved response or work acceptance** to the **Accepted work** comment. Confirm it records the terms you approved. -After acknowledgment rollout, a thumbs-up on your command confirms that the +A thumbs-up on your command confirms that the exact acceptance was recorded; it is not an acknowledgment of merely receiving -the command. This works for both Issues and Discussions. If the reaction fails +the command. The [#75 Issue acknowledgment](https://github.com/microsoft/TypeChat/issues/75#issuecomment-6592727753) +was live-verified; Discussion acknowledgment still needs a separate live check. +The behavior supports both Issues and Discussions. If the reaction fails after recording acceptance, inspect the publisher's error before retrying the still-valid command. An unchanged confirmed record is not posted twice. @@ -162,8 +172,10 @@ This is not approval to merge. Material scope changes return to discussion. ``` This remains an ordinary human comment, not an automation command. It does not -assign a coding agent. Exact-proposal acceptance is also available on Issues; -**no `/typechat build` command or implementation workflow is enabled**. +assign a coding agent. Exact-proposal acceptance is also available. The +default-off Issue implementation pilot consumes only canonical automated +acceptance records, not this free-form comment, and always requires a separate +[owner build authorization](#prepare-an-implementation-run-disabled-by-default). ## Review and merge manually @@ -180,8 +192,10 @@ assign a coding agent. Exact-proposal acceptance is also available on Issues; ## Prepare an implementation run (disabled by default) The [#504 implementation pilot](./AUTOMATION.md#third-pilot-owner-triggered-issue-implementation) -is prepared for review, not activated or live-verified. Do not post build commands -yet. After review and merge, and a separate decision to activate: +is merged and has [one successful App publication](./AUTOMATION.md#successful-app-publication-and-human-review) +on #75, followed by human fixes and merge of [#513](https://github.com/microsoft/TypeChat/pull/513). +The activation flag is currently unset. Preparing a command does not authorize +another run; a separate owner decision is still required: 1. Choose supported, explicitly accepted Issue work with no competing PR. The workflow requires the exact public `/typechat accept` record and hash, @@ -193,14 +207,14 @@ yet. After review and merge, and a separate decision to activate: variable `TYPECHAT_IMPLEMENTATION_ENABLED=true`, then post the generated `/typechat build :` as a fresh Issue comment. This authorizes one run with **1,000 main credits plus 400 detection credits**. -4. Follow Actions, then the resulting PR. After acknowledgment rollout, a rocket +4. Follow Actions, then the resulting PR. A rocket reaction on the build command acknowledges startup, not successful validation or completion. No start comment is posted. The PR links the agreement, exact patch origin, checks, usage, and limitations. Verify normal PR CI and Copilot review actually ran before review and any separate merge decision. -Do not use #504 itself as the first coding target: generated changes to the +Do not use #504 or other automation/control work as a coding target: generated changes to the agent's own automation are forbidden. Dependency/configuration changes, binary files, Discussions, and inline notes are outside this first pilot. @@ -209,7 +223,9 @@ budget exhaustion, failed checks, or an incomplete scan stop the run. Reruns do not spend again. Inspect failures before posting new authorization, and never delete retained intents or overwrite a partial branch to force recovery. To stop an active run, cancel it or withdraw the command as well as disabling -the activation variable. No activation or live coding run was performed here. +the activation variable. The temporary #75 activation was removed after that +run; repository and inherited gates were confirmed unset on 2026-11-03 (UTC). +This sheet does not activate or authorize another run. ## Website deployments @@ -234,7 +250,7 @@ failure. No artifact deletion or coding-pilot activation is needed. | Acceptance says "already accepted" | Follow the existing record. No second acceptance comment is needed. | | No acceptance preview or wrong acceptance hash | Resolve the questions or scope, then request and review a new draft. Do not substitute the response hash or edit artifacts. | | A reply command says "already answered" | Follow the existing reply link. No new model execution or comment is needed. | -| Eyes are present but no completion message appears | Receipt rollout must be merged and live-verified first. After rollout, check **Report TypeChat discussion outcome**. Existing public replies count as completion; removed/edited commands and closed/locked targets do not receive another comment. | +| Eyes are present but no completion message appears | Check the source run and **Report TypeChat discussion outcome** for errors or rejected evidence. Existing public replies count as completion; removed/edited commands and closed/locked targets do not receive another comment. | | A completion receipt reports an unconfirmed reply or uncertain write | Inspect the run and thread before retrying. A newer attempt cannot bypass an unresolved update to the same receipt. Do not delete the intent. Receipt mutations stop seven days after the original command; use a fresh request after inspection. | | A receipt was edited or removed | Automation will not overwrite edited text or blindly recreate a missing receipt. Use the existing run evidence and inspect any retained intent before recovery. | | Workflow code changed | After merge and CI, use a new command. Old runs retain their original code, and older sealed artifacts may be stale. | @@ -244,8 +260,8 @@ failure. No artifact deletion or coding-pilot activation is needed. **Spending reminder:** main assessment **400 AI credits/run**; main drafting/reply generation **50/run**. Each has a **separate detection budget, default 400**, so those main-agent limits are not whole-workflow caps. Publishing and acceptance use no -model. Copilot PR reviews are billed separately. The prepared implementation -configuration proposes **1,000 main credits plus 400 detection credits**; the +model. Copilot PR reviews are billed separately. The reviewed implementation +configuration limits each authorized run to **1,000 main credits plus 400 detection credits**; the activation gate remains **off**. Per-run budget overrides are **not enabled**. Keep this sheet's date and availability notes aligned with the diff --git a/README.md b/README.md index e4b215af..b4642ca9 100644 --- a/README.md +++ b/README.md @@ -72,7 +72,7 @@ proposals progress from discussion to accepted, reviewed changes with less manual coordination. Read about the [automation experiment](./AUTOMATION.md) and how to participate. -**Status as of 2026-11-01 (UTC):** The +**Status as of 2026-11-03 (UTC):** The [latest backlog assessment](https://github.com/microsoft/TypeChat/actions/runs/40997369231) completed successfully after the control hardening merged through [#491](https://github.com/microsoft/TypeChat/pull/491). It inventories 20 issues @@ -91,19 +91,31 @@ acceptance of work, GitHub Copilot code reviews, or merge approval. The [owner-approved discussion pilot](./AUTOMATION.md#second-pilot-owner-approved-discussion-drafts) has verified Issue draft generation, conversational `/typechat reply` delivery, and a duplicate-free reply retry after [#498](https://github.com/microsoft/TypeChat/pull/498) -merged. Manual publication and Discussions still need live verification. +merged. Manual response publication, Discussion replies, and Discussion +acceptance still need live verification. `/typechat draft` remains preview-only, with exact-text response approval through `/typechat publish`. Owner-only `/typechat accept` and its no-op retry have also been verified on an Issue after [#503](https://github.com/microsoft/TypeChat/pull/503) -merged. Completion-only operational receipts are prepared for review; they do -not publish draft content or accept work. Generation keeps its 50-credit main budget and -separately budgeted detection. Acceptance does not launch a coding agent or -enable the future implementation budget. +merged. Completion-only operational receipts were merged through +[#506](https://github.com/microsoft/TypeChat/pull/506); +[selected live checks](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916) +verified Issue/Discussion input-needed draft receipts, invalid-command +reporting, and controller-only no-op retries. Cancellation, uncertain-write +recovery, acceptance-ready receipt wording, and direct-reply reuse remain +unverified live. Receipts do not publish draft content or accept work. +Generation keeps its 50-credit main budget and separately budgeted detection. +Acceptance does not launch a coding agent or activate implementation spending. The [owner-triggered implementation pilot](./AUTOMATION.md#third-pilot-owner-triggered-issue-implementation) implements the workflow accepted in [#504](https://github.com/microsoft/TypeChat/issues/504) as a separate, disabled-by-default extension. Review, activation, and a fresh -owner build command remain distinct; no coding run or merge happens automatically. +owner build command remain distinct. The separately authorized +[#75 run](https://github.com/microsoft/TypeChat/actions/runs/41559378978) created +the App-authored [#513](https://github.com/microsoft/TypeChat/pull/513), followed +by normal CI, Copilot review, human fixes, and owner approval and merge. +Original automated evidence remains bound to the original commit, not the +human follow-ups. The activation flag is again unset; no coding run or merge +happens automatically. | Milestone | Implemented | Current status | | --- | --- | --- | @@ -126,9 +138,10 @@ owner build command remain distinct; no coding run or merge happens automaticall | Stricter human-review enforcement | Not enabled | Existing branch-review protections are retained at the owner's request. Copilot reviews do not replace human approval. | | Owner-approved issue and Discussion drafts | 2026-10-30 | Merged through [#495](https://github.com/microsoft/TypeChat/pull/495); [run 41147057482](https://github.com/microsoft/TypeChat/actions/runs/41147057482) verified the Issue draft-only path. Publication and Discussion-path verification remain separate. | | Owner-commanded direct replies | 2026-10-31 | Merged through [#498](https://github.com/microsoft/TypeChat/pull/498). [Attempt 1](https://github.com/microsoft/TypeChat/actions/runs/41226698016/attempts/1) posted one Issue reply; [attempt 2](https://github.com/microsoft/TypeChat/actions/runs/41226698016/attempts/2) skipped inference and posting, preserving the original comment. Other paths remain unverified live. | -| Exact owner work acceptance | 2026-10-31 | Merged through [#503](https://github.com/microsoft/TypeChat/pull/503). [Attempt 1](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/1) recorded the approved Issue scope; [attempt 2](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/2) preserved one unchanged record. No coding run or budget was activated; Discussion verification remains pending. | -| Completion receipts | Prepared | [Close the loop after eyes acknowledgment](./AUTOMATION.md#completion-receipts) without publishing model drafts or duplicating existing replies. Review, merge, and live verification pending. | -| Agent implementation | Not yet | A separate human authorization and future 1,000-credit implementation allowance are documented, not enabled. | +| Exact owner work acceptance | 2026-10-31 | Merged through [#503](https://github.com/microsoft/TypeChat/pull/503). [Attempt 1](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/1) recorded the approved Issue scope; [attempt 2](https://github.com/microsoft/TypeChat/actions/runs/41339605658/attempts/2) preserved one unchanged record. Those acceptance commands did not start coding or activate spending; Discussion acceptance remains unverified live. | +| Completion receipts | 2026-11-02 | Merged through [#506](https://github.com/microsoft/TypeChat/pull/506). [Selected Issue/Discussion outcomes and controller retries](https://github.com/microsoft/TypeChat/discussions/508#discussioncomment-19342916) are live-verified; other outcomes remain unverified live. | +| Acceptance and build acknowledgments | 2026-11-02 | Merged through [#510](https://github.com/microsoft/TypeChat/pull/510). Issue #75 received a thumbs-up confirming exact acceptance and a rocket acknowledging build startup; Discussion acknowledgment remains unverified live. | +| Owner-triggered Issue implementation | 2026-11-02 | Merged through [#507](https://github.com/microsoft/TypeChat/pull/507), default-off. The [#75 run](https://github.com/microsoft/TypeChat/actions/runs/41559378978) published [#513](https://github.com/microsoft/TypeChat/pull/513) on 2026-11-03 (UTC); normal CI and Copilot reviews ran, human fixes were verified, and the owner approved and merged it. Original automated evidence and later human verification remain distinct; activation is again unset. | | Selective automatic adoption of community proposals | Not yet | Future work, subject to public criteria and maintainer approval. | Implementation dates do not mean a feature is enabled on GitHub. Existing