Extract atrinik_bot into an MIT playtester repository

[zoeyrose]

Goal

Extract atrinik_bot/ from this GPL tools collection into a public, standalone
MIT-licensed repository named atrinik/playtester.
The project owns an autonomous ordinary-player playtester whose long-term
completion criterion is a reproducible playthrough of the complete game from a
new account and character to an explicitly defined end state.

Provenance and license boundary

• Source repository/path: atrinik/tools, atrinik_bot/
• Audited source revision: b0f27045a0491fd9d3f36d8ac63159c713a6c601
• Exact source subtree: 62ddc45bfbfb5e1a63a8333b0b501b57a61e50bb
• Bot-changing retained commits: 55d2ce6f8d09a52d3ce4b25447d187900213179c
  and 72f0bf821fb149ed4d2212cae520de6644db44b6
• Destination commits preserving those snapshots: f4c8145aeff476fcd9195d97d2307b78534ec3a5
  and 6d239437cacb9e3769b180cedecc3642712c4750
• Development process: OpenAI Codex under Zoey Rose's direct supervision and
  steering
• Corrected MIT direction and grant: authenticated issue comment
• Destination migration: atrinik/playtester#11
• Source removal: atrinik/tools#20
• Workspace registration: atrinik/atrinik#308
• GitHub desired state: atrinik/github-settings#49

Zoey Rose corrected and superseded her earlier sole-development wording. The
atrinik_bot project code in the audited boundary was generated and iteratively
developed by OpenAI Codex in a prior coding session under her direct supervision
and steering. Zoey supplied requirements and iterative direction, reviewed the
resulting code, and accepted it. She directs its MIT distribution and grants
under MIT all copyright and other licensable rights in it that she holds. This
factual record does not claim that Zoey personally wrote every line, identify
Codex or OpenAI as a copyright author or holder, or take a position on whether
machine-generated portions are independently copyrightable.

The retained Git history begins with a bulk import of an earlier local working
tree; the earlier development history was not recovered. The destination
PROVENANCE.md records that gap rather than claiming complete historical
lineage, and records the exact retained snapshots and transformations used for
the extraction.

That direction and grant are limited to the atrinik_bot project code, not
unrelated tools material, external dependencies, linked binaries, or content
inputs. In particular, legacy-libatrinik v1.1.5 remains GPL-2.0-or-later, and
its source and linked/combined binaries remain subject to that license. Other
dependencies and content retain their respective licenses, as listed in the
destination THIRD_PARTY_NOTICES.md and dependency lock.

Scope

• Create atrinik/playtester with main, issues enabled, and a public MIT
  source distribution.
• Record Codex generation under Zoey Rose's direct supervision and steering,
  her MIT direction and limited-rights grant, and the unrecovered pre-import
  history under her authenticated GitHub account.
• Import the bot source with retained snapshot history and commit a
  destination provenance manifest, MIT license, qualified rights notice,
  and third-party dependency notices.
• Give the repository standalone build, test, contribution, security, and
  operator documentation; preserve the loopback-only dashboard and
  out-of-tree credential/state boundaries.
• Run the strict native tests and complete 418-test Python regression suite
  against pinned content/runtime inputs.
• Remove atrinik_bot/ and its CI steps from atrinik/tools; update the
  tools guide and repository inventory without disturbing retained tools.
• Merge cross-repository migration, supply-chain, and GitHub desired-state
  records so atrinik/playtester is the bot policy owner.
• Seed the new repository with an ordered issue roadmap covering a
  self-provisioning runtime, account/character lifecycle, content-derived
  planning, all quests, progression/combat/economy, recovery, and a
  deterministic full-playthrough completion report.

Compatibility direction

The new repository owns playtesting policy, world knowledge, memory, and
completion reporting. It may retain a Classic direct-protocol backend while
that is the only complete headless path, behind a narrow game-client interface.
The versioned client automation API tracked by atrinik/client#18 remains a
future backend and should eventually remove duplicated transport/model code;
it must not block the standalone extraction or erase supported behavior.

Acceptance criteria

• atrinik/playtester is public, identifies as MIT on GitHub, and contains
  no mutable credentials, runtime state, caches, or downloaded dependencies.
• Every imported file and transformation is covered by the committed
  provenance record, the corrected development-process attestation, Zoey's
  grant of any rights she holds, and the third-party review; the missing
  earlier history is disclosed explicitly.
• The new repository's required validation passes from a fresh checkout.
• The source-removal and workspace/governance pull requests link this issue
  and the destination repository.
• Roadmap issues define measurable outcomes on the path from today's
  tutorial/quest/farming automation to one unattended start-to-finish run.

[zoeyrose]

Repository and roadmap created

• Created public atrinik/playtester.
• Seeded clean MIT scaffolding at
  67282f9.
• Verified GitHub detects MIT and the initial
  Playtester validation
  job passes.
• Created the full-playthrough initiative
  playtester#1 and linked
  roadmap tasks fix(release): skip unavailable issue comments #2 through feat(map-checker): validate stable content identities #10 as sub-issues.
• Applied Atrinik's squash-only merge defaults.

No atrinik_bot implementation, credentials, database, runtime state, cache,
downloaded dependency, or build artifact was copied into the new repository.

Provenance hold

The deeper audit confirmed that MIT extraction must fail closed under the
current registry contract:

• The complete atrinik/tools history starts with a bulk import of the bot in
  55d2ce6f8d09a52d3ce4b25447d187900213179c, followed by the dependency URL
  correction in 72f0bf821fb149ed4d2212cae520de6644db44b6.
• Retained review/session evidence proves the bot existed before that import,
  but searches of repositories, refs, reflogs, archives, editor history, and
  retained sessions did not recover its original history.
• A recovered intermediate snapshot is also a bulk capture, not ancestry, and
  includes secret-bearing local material, so it is explicitly excluded.
• The current package links GPL-2.0-or-later pathfinding code and contains
  constants or authored-world facts derived from GPL-governed inputs; those
  boundaries need a separability/reimplementation decision as well.

Zoey Rose's corrected attestation records that OpenAI Codex generated and
iteratively developed the atrinik_bot project code under her direct
supervision and steering, and records her MIT direction and grant of any rights
she holds. That is important provenance evidence, but the current
docs/PROVENANCE.md requires complete history and fails closed on any gap. At
the time of this comment, the implementation therefore remained in
atrinik/tools unchanged.

Two safe paths remained at that point:

1. establish a separately reviewed provenance-policy exception/attestation
   mechanism, then resolve every GPL-linked or derived boundary; or
2. implement the playtester independently from documented behavior, the
   registry's default when reuse cannot be proven.

The later comments and linked pull requests record the completed migration.

[zoeyrose]

Correction: supervised Codex development and MIT direction

I, Zoey Rose (@zoeyrose), correct and supersede my earlier sole-development
wording. This statement is limited to the atrinik_bot project code.

The project code contained in
atrinik/tools@b0f27045a0491fd9d3f36d8ac63159c713a6c601:atrinik_bot/
(subtree 62ddc45bfbfb5e1a63a8333b0b501b57a61e50bb) was generated and
iteratively developed by OpenAI Codex in a prior coding session under my direct
supervision and steering. I supplied requirements and iterative direction,
reviewed the resulting code, and accepted it.

I direct release of that code under the MIT License and, to the extent I hold
copyright or other licensable rights in it, grant those rights under MIT. This
statement does not say that I personally wrote every line, does not identify
Codex or OpenAI as a copyright author or holder, and takes no position on
whether any machine-generated portion is independently copyrightable.

The retained Git history begins with bulk import commit
55d2ce6f8d09a52d3ce4b25447d187900213179c, followed by
72f0bf821fb149ed4d2212cae520de6644db44b6; the earlier history gap remains
disclosed in the destination provenance record. Git author metadata identifies
my submitting account and must not be read as proof that I personally generated
every line.

This attestation does not cover unrelated atrinik/tools material, third-party
dependencies, Atrinik game content, generated or downloaded artifacts,
credentials, runtime state, logs, or caches. It replaces my earlier
sole-development wording for the exact code boundary above.

[zoeyrose]

Completed the repository split.

• atrinik/playtester#11 preserved the two retained source snapshots, added the
  MIT license and direct-grant provenance record, pinned third-party inputs,
  standalone build/release/validation, and operator/contributor documentation.
• atrinik/tools#20 removed atrinik_bot/ and its repository-owned CI steps.
• atrinik/atrinik#308 registered the independent Classic-only playtester
  checkout, ownership, migration, and supply-chain contracts.
• atrinik/github-settings#49 recorded the repository's required checks,
  release-tag policy, and custom-property desired state.
• atrinik/playtester#1 owns the open start-to-finish campaign roadmap, with
  issues fix(release): skip unavailable issue comments #2 through feat(map-checker): validate stable content identities #10 as ordered subissues across three milestones.

Validation passed on the destination migration (strict native build and CTest,
418 Python tests, wheel install/help check, CodeQL, and post-merge validation),
the tools removal, the wrapper's 299-test integration run, and the governance
configuration.

The GitHub settings publisher is intentionally manual; merging its desired-state
record did not invoke bin/publish --apply.