[Task]: Review orphaned main autopilot archive (archive/main-autopilot-654-sketches-2026-06)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 3
Description
Human action required
Personally review the preserved orphan tip that was formerly on main (pre–0.8.0 history repair) and decide whether anything useful remains to port, document, or discard.
Branch: archive/main-autopilot-654-sketches-2026-06
Tip: 36533ca (includes review note)
Former orphan tip (pre-doc commit): 0714dcf
Why the agent cannot safely proceed
This needs human judgment: what (if anything) in the orphan history is product-relevant vs noise, whether any ideas should become new Issues on the real tree, and whether the archive branch can eventually be deleted. An agent can inventory files, but should not unilaterally decide discard vs revive product intent.
Context and affected artifacts
During the v0.8.0 cut, main had been rewritten as an unrelated-history #654 autopilot sketch line (no merge-base with release). Those commits were not cherry-picked into the product line.
| What | Detail |
|---|---|
| Product line | main / release at post-0.8.0 + publish-pypi restore (e3e786d and later) |
| Archive | archive/main-autopilot-654-sketches-2026-06 |
| Review note on branch | docs/migration/main-orphaned-autopilot-654-review.md |
| Real #654 work | Shipped via reviewed PRs on release and packaged in v0.8.0 — do not assume the orphan tip is the product source of truth |
Post-root deltas on the orphan line were largely sketch JSON under .agentic/releases/unreleased/*-654*.json, not landable Features on top of current plate-core.
Best-effort instructions / next steps
git fetch origin archive/main-autopilot-654-sketches-2026-06
git log --oneline origin/archive/main-autopilot-654-sketches-2026-06
# Review note committed on the archive tip:
git show origin/archive/main-autopilot-654-sketches-2026-06:docs/migration/main-orphaned-autopilot-654-review.md
# What changed after the orphan root:
git diff --stat 76f03de origin/archive/main-autopilot-654-sketches-2026-06
Suggested review outcomes (pick one or mix):
- No action — archive is historical only; leave the branch; close this Task.
- Open follow-ups — turn any salvageable ideas into Feature/Research/Question issues on current
main/release(do not force-merge the orphan history). - Cleanup later — after review, optionally delete the archive branch once you are sure nothing further is needed.
Related: Release #984 cut notes, main restore to v0.7.2, alignment of release / release-* tracks to main.
Done signal
Leave a short completion comment that includes <!-- PLATE-TASK-CLOSED --> and states the decision (no salvage / issues filed / archive retained or deleted). Do not put secrets in the comment.
Closing requirements:
- This Task will close with a completion comment that includes
<!-- PLATE-TASK-CLOSED -->. - The completion comment will not include secrets, credentials, tokens, or privileged configuration values.
Related links
- Branch: https://github.com/akasper/plate/tree/archive/main-autopilot-654-sketches-2026-06
- Review note path (on archive tip):
docs/migration/main-orphaned-autopilot-654-review.md - Release PR (0.8.0): https://github.com/akasper/plate/pull/984
- Publish-pypi restore: https://github.com/akasper/plate/pull/986
- Standing Next Release: https://github.com/akasper/plate/issues/983
- Far-future roadmap stub: https://github.com/akasper/plate/issues/654
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Fetch origin/archive/main-autopilot-654-sketches-2026-06, read docs/migration/main-orphaned-autopilot-654-review.md, and inspect the log and diff from 76f03de. Decide whether to retain the archive, file follow-up issues for salvageable ideas, or delete it later. Leave a completion comment containing and the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100