Miksuu Upstream Wiki Import

Miksuu Upstream Wiki Import

This page records the import of the upstream Miksuu/a2waspwarfare GitHub wiki into the rayswaynl/a2waspwarfare developer wiki.

The import is intentionally namespaced under Miksuu-Wiki-Archive-* pages so current docs can remain canonical while still preserving every upstream page at HEAD.

Navigation policy: archive pages are preserved and linked from the tables below, but they are not all first-level sidebar entries. Use Community & Dev for cultural context, this page as the archive index, and Upstream changelog feature leads for source-checkable follow-up work.

Snapshot

Field	Value
Source wiki	https://github.com/Miksuu/a2waspwarfare.wiki.git
Imported commit	45ef3da367d65e6487de488bbe3b16a8a8b21ba3
Commit summary	Destroyed Raysway Update Notes (markdown)
Snapshot date	2026-06-03
Current tracked Markdown pages	9
Binary attachments in wiki repo	None tracked at HEAD
Machine ledger	agent-upstream-wiki-imports.jsonl

Imported pages

Upstream file	Imported archive page	Import class	Current use
Welcome.md	Miksuu Wiki Archive: Project Welcome	Summarize and archive	Lineage, CTI explanation, contribution culture.
Home.md	Miksuu Wiki Archive: Wiki Home Stub	Archive only	Original one-line upstream landing page.
Changelog.md	Miksuu Wiki Archive: Changelog	Verbatim archive	Primary 2023-2024 community release-note history.
Big-announcements.md	Miksuu Wiki Archive: Big Announcements	Verbatim archive	Donors, contributors, GPT/HC/performance/event culture.
Gameplay-videos.md	Miksuu Wiki Archive: Gameplay Videos	Archive/link	Gameplay media.
Discord-Bot.md	Miksuu Wiki Archive: Discord Bot	Archive/link	DiscordBotFramework provenance only.
LoadoutManager.md	Miksuu Wiki Archive: LoadoutManager	Archive with caveat	Tool rationale and examples; current generation scope must be rechecked.
Project-Script-Architecture-of-Chernarus-mission.md	Miksuu Wiki Archive: Chernarus Mission Script Architecture	Archive with caveat	Historical architecture checklist and external diagram/PDF links.
Development-process-(for-Miksuu's-Portfolio-return).md	Miksuu Wiki Archive: Development Process	Summarize and archive	SQF debugging, GPT, Trello, branch/test workflow, performance lessons.

History-only pages not imported as standalone pages

Historical file	Git history	Decision
Problems-and-solutions-(for-Miksuu's-Portfolio-return).md	Created 58915c8, updated, then deleted/replaced by the development-process page at b098512 on 2024-03-25.	Do not import separately; current content lineage is represented by Development process.
Big-annoucenements.md	Typo predecessor created 1076ef2, deleted/renamed by bc0d79c on 2023-12-23.	Do not import separately; represented by Big announcements.
Raysway-Update-Notes.md	Created by Ray Reijnders at 12b6fd4 and deleted ten seconds later at 45ef3da on 2026-06-02.	Do not import; the only observed content was a transient placeholder and no page remains at HEAD.
test1.md, Home-test1.md	Marty-created test pages on 2023-06-11, then deleted.	Skip as test artifacts.

External media to preserve as links

The upstream wiki does not track binary files at HEAD, but several pages link to external media:

Page	External media
Chernarus mission architecture	Discord-hosted architecture PNG and PDF.
Changelog	GitHub asset images, Discord CDN images, videos and .ogg audio links.
Gameplay videos	YouTube Live gameplay link.

Do not rewrite or mirror external media without a separate asset-preservation pass. Keep the original URLs visible so the archive remains traceable.

Current-source caveats

Upstream claim area	Why it needs caution	Current canonical route
LoadoutManager terrain propagation	Upstream pages describe broad modded-terrain copying. Current docs/source say maintained generated output is Vanilla Takistan and modded propagation is inactive or non-authoritative.	Tools and build workflow, Gear/loadout/EASA atlas
Architecture folder walkthrough	The upstream architecture page is broad and partly stale; current file names and compile ownership should be taken from source-backed atlases.	Architecture overview, SQF code atlas, Function and module index
Discord bot page	Upstream page is a stub and does not document the current in-repo .NET bot shape.	External integrations, Integration trust boundary audit
Changelog feature status	Old release notes may describe old server state, branch state or reverted work.	Feature status register, Current source status snapshot
Modded-map event notes	Upstream V9/V10/modpack sections describe event-era terrain and vehicle propagation. Current generated/release scope is not the same as those event notes.	Tools and build workflow, Content structure and maps
Server ops and HC/performance anecdotes	Upstream announcements include live host, player-count, view-distance, HC and multithreading experiments. Treat them as historical ops snapshots, not current topology or policy.	AI, headless and performance, Headless delegation/failover, Current source status snapshot
Time-variant feature notes	Some changelog entries intentionally describe temporary removals/readds, reverted features, tournament/event settings or next-restart deployments.	Feature status register, Pending owner decisions

Agent rules

1. Use these archive pages as provenance and candidate lessons.
2. Promote a claim only after checking current source, branch history or the existing source-backed docs.
3. Preserve contributor names and cultural context, but avoid converting Discord-era wording into current-role claims.
4. When an upstream page conflicts with current source-backed docs, keep both: archive the upstream claim and route implementation work to the current canonical page.
5. Do not re-add every archive page to the sidebar; this page is the click-through index for preserved upstream material.

Continue Reading

Previous: Community & Dev | Next: Developer history and upstream lessons

Related: Developer history and upstream lessons | Upstream Miksuu commit intel | agent-upstream-wiki-imports.jsonl

Candidate backlog: Upstream changelog feature leads