Skip to content

Migrate Wesley Method backlog to GitHub Issues #548

Closed
#599
Closed
Migrate Wesley Method backlog to GitHub Issues#548
#599
Labels
choreMaintenance / refactor / toolingdocsDocumentation changeslegend:PROCESSMethod/process workwork-in-progressMethod issue is actively being workedwork:integrityRemoves lies, drift, flake, or trust debt

Description

@flyingrobots
flyingrobots
opened on Jun 4, 2026

Hill

As a Wesley maintainer and agent collaborator, I want Wesley Method work tracked in GitHub Issues while repository files remain evidence, so that the repo follows current METHOD v2.1.0 doctrine and no longer has two live trackers.

Sponsored perspectives

  • Sponsored Human: Wesley maintainer using GitHub Issues to choose and review work.
  • Sponsored Agent: Workflow automation agent preserving issue/source provenance during migration.

Context

METHOD v2.1.0 moved live work tracking to GitHub Issues. Wesley still documents docs/method/backlog/** as the live queue and carries local backlog cards, including many cards that already mirror GitHub Issues.

Scope

  • Add Method lane and legend labels to this repository.
  • Migrate repo-only backlog cards into GitHub Issues with source-path provenance.
  • Add lane/legend labels to existing GitHub issues that were mirrored into local backlog files.
  • Update Wesley docs and templates so GitHub Issues are the live tracker and repo files are evidence.
  • Archive or mark local backlog files as migrated evidence, not active queue.

Out of scope

  • Resolving the migrated work.
  • Reprioritizing every issue beyond preserving current lane classification.
  • Changing Wesley product architecture.

Acceptance criteria

  • Wesley docs say GitHub Issues are the live Method tracker.
  • Local backlog docs are no longer presented as the active source of truth.
  • Repo-only backlog cards have GitHub issue URLs recorded in a migration manifest.
  • Existing GitHub-backed local cards are mapped to their existing issue numbers without duplicates.
  • GitHub Issues carry Method lane and legend labels for migrated work.
  • Validation evidence is recorded in the PR or migration docs.

Witness plan

Tests

Run docs checks and preflight appropriate for documentation/process changes.

Playback

Inspect GitHub issue labels and migration manifest; verify no live backlog cards remain under docs/method/backlog/** outside migration notes.

Docs

Update AGENTS.md, docs/METHOD.md, backlog README(s), issue templates, and PR template as needed.

Retro / Closeout

Use the migration manifest and PR summary as closeout evidence.

Activity

  1. flyingrobots
    added
    choreMaintenance / refactor / tooling
    docsDocumentation changes
    work:integrityRemoves lies, drift, flake, or trust debt
    lane:asap
    work-in-progressMethod issue is actively being worked
    legend:PROCESSMethod/process work
    on Jun 4, 2026

  2. coderabbitai commented on Jun 4, 2026

    @coderabbitai
    coderabbitaibot
    on Jun 4, 2026 – with coderabbitai
    🔗 Related PRs

    #43 - chore(oss): add PR template, CODEOWNERS, CHANGELOG (supersedes #22) [merged]
    #472 - [codex] Advance Continuum inspectability and METHOD closeout [merged]
    #475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
    #476 - Release/v0.1.0 [merged]
    #503 - Revise README.md for clarity and additional information [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. flyingrobots
    closed this as completedin #599on Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreMaintenance / refactor / toolingdocsDocumentation changeslegend:PROCESSMethod/process workwork-in-progressMethod issue is actively being workedwork:integrityRemoves lies, drift, flake, or trust debt

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions