BattleReport — collaboration and attribution
What can be attributed accurately
The repository history records an original personal-report direction, combat and recovery exploration, moving quick reports, frozen pre-fight baselines, a strict combat-only pivot and the Octo Battle Report → Battle Report rename. These are the creator's project identity and implementation history.
Source commits do not automatically reveal which earlier code lines were written by a human or an AI, the detailed motives for every UI adjustment, or which private proposals the creator approved. This document will not invent those conversations or claim the assistant conceived the original product.
The archived Blizzard 1.12.1 GlobalStrings.lua test fixture belongs to its upstream source and is intentionally gitignored. Historical release assets and game interfaces are not original AI-authored images.
What AI contributed on October 26, 2026
- Inspected current GitHub tree, README, GUIDE, TOC, Core, Average, Resources, Parser, UI, and Python/PowerShell tests.
- Reviewed September source diffs and verified the public v1.6.5 release metadata, ZIP asset and checksum listing.
- Distinguished strict combat-only behavior from superseded early buffering, current Nampower-aware vs fallback cast counting, statistical baselines, bounded history and source-label limitations.
- Reconciled old-owner release URLs and README slash aliases with current GitHub releases/source.
- Created/revised eleven Markdown documentation files with narrative evolution and a test roadmap, without changing runtime code.
That is research, technical analysis, editorial and Git documentation work. It is not proof of successfully running original WoW, of test results in this session, of authorship of earlier code, or of creator acceptance of optional new features.
Record future iterations faithfully
For each substantial change, preserve human direction, AI suggestions/alternatives, iteration and corrections, explicit user acceptance/rejection/deferral, exact file/commit/release evidence and tests actually executed. Mark statements as source-observed, historically reported in release notes, independently verified or proposed.
Write public-safe summaries, not raw private conversations. Do not include personal game saves, private account data or other players' identifying combat logs. A missing LICENSE cannot be supplied silently on the creator's behalf.
This documentation-only pass updates public records and leaves application behavior untouched.
Document information
Human creator and creative director: Babuni.dev.