Skip to content

official Packages: extract playerbots and dungeons into the collection #306

Closed

Description

@Mathih13

This was generated by AI during triage.

Human Brief

Category: enhancement
Summary: Move the private playerbots and dungeon Package sources into the Official Package Collection.

Why this needs a human:
The sources and bot test scripts are not in the public checkout. A maintainer must provide them, decide their public ownership, and review their history and licensing.

Current behavior:
The public core tree contains neither Package. Maintainer-side Package sources and test scripts cannot be extracted by an unattended agent.

Desired behavior:
Publish playerbots and dungeons as separate top-level Packages in the Official Package Collection. Generalize the existing Deadmines work into the dungeons install unit. Update Package CI and private bot-test setup so tests install the required Packages before running.

Acceptance criteria:

  • playerbots and dungeons install independently from the Official Package Collection.
  • The dungeons boundary is documented and is not limited to one encounter.
  • Core-tip CI compiles and tests both Packages.
  • Bot test setup installs its Packages before running.
  • The unattended work-loop knows the playerbots sources live in another repository (carried from packages devx: extract playerbots + deadmines→dungeons into the packages monorepo #94).
  • No private source, credential, or client binary enters the public repositories accidentally.

Out of scope:

  • Changing deployed fixtures
  • Production Realm changes

Activity

  1. added
    enhancementNew feature or request
    P2normal
    ready-for-humanNeeds a maintainer: a decision, a maintainer's Realm, or coordination
    on Aug 24, 2026
  2. Mathih13 commented on Aug 28, 2026

    @Mathih13
    ContributorAuthor

    Status 2026-08-28: the dungeons half is done, with the scope narrowed by the maintainer to Deadmines only.

    Remaining here: the playerbots half. The private sources and bot-test scripts still need a maintainer to provide them, the bot-test setup must install its Packages before running, and the work-loop awareness item carried from #94 is now in the acceptance criteria.

    Related: fixture migration is #307 (rewritten today), production cutover is #365, live verification of Deadmines is #366.

  3. Mathih13 commented on Aug 28, 2026

    @Mathih13
    ContributorAuthor

    The playerbots half is now spec'd as a clean-room build in the Official Package Collection (design session 2026-08-28). The private sources will not be extracted; the public spec is the wire-harness scenario suite plus core's existing seams, which pin the table, reducer, and file names.

    Plan of record, in order:

    1. LyraCoreProject/wire-harness adapter repairs and Package install step: wire-harness adapter: repair preflight and install Packages before bot scenarios #372. This closes this issue's "bot test setup installs its Packages" criterion and the work-loop awareness criterion (the adapter becomes the whole public entrypoint).
    2. Package config seam: packages config: Operator key-values for installed Packages #369 (module table and reducer), packages CLI: config verb sets Package key-values across the topology #370 (CLI verb, pin bump deferred to the chain head).
    3. Party slice: playerbots: party slice (spawn, kits, brains, follow, auto-accept) packages#5 (spawn surface, kits, brains, follow, auto-accept).
    4. Cross-Shard travel: playerbots: session-less Shard crossing via transfer intents #371 (intent row and Gateway orchestration) plus playerbots: cross-Shard travel (transfer arms and arrival adoption) packages#6 (transfer arms, grouped-follow trigger). Acceptance is deleting test-bot-deadmines's sharded SKIP.
    5. Quester slice: playerbots: quester slice (goal loop on fixture and imported node) packages#7, then the observed imported-node session Confirm on a real client that a standing population of bots reads as believable players #373.

    Deferred by name: bot-initiated serendipity invites (core seams stay parked), solo crossings such as boats (gated on #4), Lua personalities (#18), auto-populate, and Package config files (superseded by the #369 key-value design).

  4. Mathih13 commented on Aug 30, 2026

    @Mathih13
    ContributorAuthor

    This was generated by AI during triage.

    Plan-of-record status after the 2026-08-30 orchestration session — all eight issues are implemented and merged:

    Still without a live verdict (the local realm was never touched): the six bot scenarios on a fresh single-topology stack, the sharded Deadmines crossing, and the imported-node chained quest. These are the #373 session plus one sanctioned wire-suite run.

    Follow-ups filed: #378 (collapse the four accept-gate copies; make quest_is_complete pub(crate); missing abandon/sell verbs), packages#11 (stall-clock reporting gaps). Deferral list unchanged: serendipity, boats (#4), Lua personalities (#18), auto-populate, config files (superseded by #369).

  5. Mathih13 commented on Sep 1, 2026

    @Mathih13
    ContributorAuthor

    This was generated by AI during triage.

    Closing as complete (maintainer, 2026-09-01). Every acceptance criterion is met:

    • playerbots and dungeons install independently from the Official Package Collection (both on the collection's main).
    • The dungeons boundary is documented and generalized past one encounter.
    • Collection CI compiles and tests both Packages against core tip on every PR.
    • Bot test setup installs its Packages before running (wire-harness#2, closing wire-harness adapter: repair preflight and install Packages before bot scenarios #372).
    • The work-loop awareness item is satisfied: the wire-harness adapter is the whole public entrypoint.
    • No private source was extracted — the playerbots half shipped as a clean-room build (the 2026-08-30 plan of record, all eight issues merged).

    The remaining live verdicts (six bot scenarios on a fresh stack, the sharded Deadmines crossing, the imported-node chained quest) are the #373 session plus one sanctioned wire-suite run — tracked there, not here. The milestone done-when stays on #42.

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