Skip to content

packages devx: extract playerbots + deadmines→dungeons into the packages monorepo #94

Closed
2 of 2 issues completed

Description

@Mathih13

Spec: the packages-devx design, §2 "The extraction this implies" (public proposal: #1; the full design doc lives in the private working origin).

Move playerbots and deadmines out of core into the LyraCoreProject/packages monorepo — they stop being .gitignore exceptions and become add-able. Deadmines generalizes to a dungeons package (encounter granularity is wrong for an install unit). packages/example/ STAYS in core (CI compiles the marker registries against it).

This has teeth beyond the file move — operator-sequenced, not for the unattended loop:

  • core's bot-exercising test scripts (the deadmines bot scenario and the bot suite, private working origin) need CI to lyracore packages add first
  • the unattended work-loop must know these sources live in another repo
  • removing a package whose tables hold data is the danger-zones §1.1 operator decision on every deployed fixture

Blocked by #90
Blocked by #93

Done when: a fresh core clone has no packages/playerbots or packages/deadmines, lyracore packages add playerbots and add dungeons restore them from the monorepo, and the bot suite is green in CI via the add-first path.


Migrated 2026-08-11 from the private tracker (spacetime-core#502).

Activity

  1. Mathih13 commented on Aug 24, 2026

    @Mathih13
    ContributorAuthor

    This was generated by AI during triage.

    Human Brief

    Category: enhancement
    Summary: Coordinate private Package extraction and fixture cutover as two human-owned steps.

    Why this needs a human:
    The Package sources and bot scripts are outside the public checkout. Fixture cutover can remove populated Package tables and requires a named-target data decision.

    Current behavior:
    The public core repository has no playerbots or deadmines Package to extract. The Official Package Collection also does not exist yet.

    Desired behavior:
    After the Package CLI and official repository are available, #306 publishes playerbots and the generalized dungeons Package. Then #307 recreates disposable development fixtures and uses reviewed migrations for named persistent fixtures. Production remains out of scope unless explicitly named in a separate operation.

    Acceptance criteria:

    • Both source Packages install from the Official Package Collection.
    • Bot and dungeon CI use the supported install-first path.
    • Every fixture touched by the cutover is named and classified before mutation.
    • Persistent Package data is preserved or deliberately removed through a reviewed plan.
    • No production Realm is touched by this issue.

    Out of scope:

    • Unattended extraction from private sources
    • Direct implementation on this parent issue
  2. added
    ready-for-humanNeeds a maintainer: a decision, a maintainer's Realm, or coordination
    on Aug 24, 2026
  3. Mathih13 commented on Aug 28, 2026

    @Mathih13
    ContributorAuthor

    Closing in favor of #306 (extraction) and #307 (fixture migration, rewritten today). The dungeons half of #306 merged 2026-08-28 with a narrowed scope: the collection ships Deadmines only (#363, LyraCoreProject/packages#4). The one item from this issue that neither child named, making the unattended work-loop aware the playerbots sources live in another repository, is now in #306's acceptance criteria.

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

    P2normalenhancementNew feature or requestready-for-humanNeeds a maintainer: a decision, a maintainer's Realm, or coordination

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions