Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .planning/ROADMAP.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Roadmap

## Current Focus

Maintain accurate, reproducible portfolio demo documentation.
13 changes: 13 additions & 0 deletions .planning/STATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Project State

Last activity: 2026-06-10 - Completed quick task 260610-ppt: Correct README monitor wording to match autopilot-demo

### Blockers/Concerns

None.

### Quick Tasks Completed

| # | Description | Date | Commit | Status | Directory |
|---|-------------|------|--------|--------|-----------|
| 260610-ppt | Correct README monitor wording to match autopilot-demo | 2026-06-10 | this atomic task commit | Verified | [260610-ppt-fix-pr-3-follow-up-readme-monitor-wordin](./quick/260610-ppt-fix-pr-3-follow-up-readme-monitor-wordin/) |
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
quick_id: 260610-ppt
mode: quick-full
status: complete
date: 2026-06-10
---

# Correct README monitor wording to match autopilot-demo

## Goal

Correct the PR #3 follow-up wording so the README comment names the same repository queried by the following command.

## Tasks

1. Update the README monitoring comment from `autopilot-core` to `autopilot-demo`.
2. Record the successful fix in `memory/examples/` as required by `AGENTS.md`.
3. Verify the intended wording, unchanged command target, branch, and patch formatting.

## Must Haves

- The monitoring comment says `Monitor autopilot-demo for the fix PR`.
- The following command remains `gh pr list -R Coding-Autopilot-System/autopilot-demo`.
- `git diff --check` passes.
- The work remains on `docs/portfolio-hardening-20260610`.

## Plan Check

Passed: the plan covers the requested wording correction, repo-local memory requirement, branch constraint, and explicit validation gate without unrelated changes.
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
quick_id: 260610-ppt
status: complete
date: 2026-06-10
---

# Summary

Corrected the README monitoring comment so it names `autopilot-demo`, matching the following `gh pr list` command.

## Changes

- Updated one README comment.
- Added the repo-required successful-fix memory entry.
- Bootstrapped minimal local GSD project state and recorded this validated quick task.

## Result

The PR monitoring instruction and command now consistently target `autopilot-demo`.
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
quick_id: 260610-ppt
status: passed
date: 2026-06-10
---

# Verification

## Checks

- Passed: current branch is `docs/portfolio-hardening-20260610`.
- Passed: `# Monitor autopilot-demo for the fix PR` exists exactly once.
- Passed: `# Monitor autopilot-core for the fix PR` is absent.
- Passed: `gh pr list -R Coding-Autopilot-System/autopilot-demo` remains present exactly once.
- Passed: `gsd-sdk query init.quick` detects both roadmap and planning state.
- Passed: `git diff --check`.

## Status

Passed. All task must-haves are satisfied.
36 changes: 28 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,15 @@
[![Demo CI](https://github.com/Coding-Autopilot-System/autopilot-demo/actions/workflows/demo-ci.yml/badge.svg?branch=main)](https://github.com/Coding-Autopilot-System/autopilot-demo/actions/workflows/demo-ci.yml)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

**Demo target for the Coding-Autopilot-System AI repair pipeline** triggers intake workflows when CI fails, demonstrating end-to-end agentic fix from failure detection to pull request.
**Demo target for the Coding-Autopilot-System AI repair pipeline** - triggers intake workflows when CI fails, demonstrating the end-to-end path from failure detection to pull request.

Part of the [Coding-Autopilot-System](https://github.com/Coding-Autopilot-System) autonomous CI repair platform. The control plane lives in [autopilot-core](https://github.com/Coding-Autopilot-System/autopilot-core).
Part of the [Coding-Autopilot-System](https://github.com/Coding-Autopilot-System) autonomous CI repair platform. The control plane lives in [autopilot-core](https://github.com/Coding-Autopilot-System/autopilot-core), and the runner-hosted worker/runtime pattern lives in [ci-autopilot](https://github.com/Coding-Autopilot-System/ci-autopilot).

## Repo boundary

- `autopilot-demo` is not the operator and not the worker host. It is the demonstration target repo.
- `autopilot-core` owns queue scanning, Codex invocation, and PR creation.
- `ci-autopilot` shows the worker/runtime implementation used to process queued repair tasks.

## How the demo works

Expand Down Expand Up @@ -35,20 +41,34 @@ gh workflow run demo-ci.yml -R Coding-Autopilot-System/autopilot-demo
# Watch for the intake issue to be created
gh issue list -R Coding-Autopilot-System/autopilot-demo --label autofix --label queued

# Monitor autopilot-core for the fix PR
# Monitor autopilot-demo for the fix PR
gh pr list -R Coding-Autopilot-System/autopilot-demo
```

## Demo runbook

1. Trigger [`.github/workflows/demo-ci.yml`](.github/workflows/demo-ci.yml) to produce a known failure signal.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Make the runbook produce an actual failure signal

When a reviewer follows this newly added runbook, dispatching demo-ci.yml cannot produce the promised failure signal: .github/workflows/demo-ci.yml:12-14 only echoes a message and exits successfully, while .github/workflows/autopilot-create-issue.yml:16 creates an issue only when the workflow conclusion is failure. As a result, the runbook stops at step 2 and cannot demonstrate the documented end-to-end repair flow; either provide an explicit failure-triggering mechanism or document the prerequisite needed to make the workflow fail.

Useful? React with 👍 / 👎.

2. Confirm [`.github/workflows/autopilot-create-issue.yml`](.github/workflows/autopilot-create-issue.yml) creates an `autofix + queued` issue.
3. Watch `autopilot-core` pick up the issue and open a PR back into this repo.
4. Use this repo's issue, branch, and PR history as the audit trail for the demo.

## Enterprise proof points

- Demonstrates bounded blast radius: the platform proposes a fix in a dedicated target repo before broader rollout.
- Produces an auditable story for reviewers: failure event, queued issue, operator pickup, and PR are visible artifacts.
- Keeps the demo reproducible with workflow-dispatch entry points rather than hidden local steps.

## Workflows

| Workflow | Purpose |
|----------|---------|
| `ci.yml` | Portfolio CI YAML validation (always passes) |
| `demo-ci.yml` | Demo trigger simulates CI activity to test intake flow |
| `autopilot-create-issue.yml` | Intake creates autofix+queued issue on workflow failure |
| `ci.yml` | Portfolio CI - YAML validation (always passes) |
| `demo-ci.yml` | Demo trigger - simulates CI activity to test intake flow |
| `autopilot-create-issue.yml` | Intake - creates `autofix + queued` issue on workflow failure |

## Documentation

- [Wiki](https://github.com/Coding-Autopilot-System/autopilot-demo/wiki) — setup guide, architecture, configuration reference
- [autopilot-core](https://github.com/Coding-Autopilot-System/autopilot-core) — operator control plane
- [Wiki](https://github.com/Coding-Autopilot-System/autopilot-demo/wiki) - setup guide, architecture, configuration reference
- [autopilot-core](https://github.com/Coding-Autopilot-System/autopilot-core) - operator control plane
- [ci-autopilot](https://github.com/Coding-Autopilot-System/ci-autopilot) - worker/runtime reference
- [Coding-Autopilot-System org](https://github.com/Coding-Autopilot-System)
8 changes: 8 additions & 0 deletions memory/examples/20260610_autopilot-demo_boundary-readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# 20260610_autopilot-demo_boundary-readme

Issue Description: README did not strongly frame the repo as the demo target in a three-repo story.
State: The demo flow was present, but the target-only role and audit value were underexplained.
Action: Added repo boundary language, a concise demo runbook, and enterprise proof points in `README.md`.
Result: The repo now reads as a bounded demonstration target with a clear audit trail.
Diff Patch: Updated `README.md` only.
Rationale: Hiring reviewers should understand why the demo repo exists and how to reproduce the story quickly.
8 changes: 8 additions & 0 deletions memory/examples/20260610_readme-monitor-target.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# 20260610_readme-monitor-target

Issue Description: The README said to monitor `autopilot-core`, but the command listed PRs from `autopilot-demo`.
State: The prose and command target disagreed.
Action: Changed the monitoring comment to name `autopilot-demo`.
Result: The README now accurately describes the command that follows.
Diff Patch: Updated one comment in `README.md`.
Rationale: Operational documentation should name the repository actually queried by the command.
Loading