Bug Tracker

Forgejo Issues are the live source of truth for defects and work. This page defines the taxonomy and summarizes preservation-critical gaps that should never disappear in a closed issue list.

Labels

The following labels are configured in Forgejo:

Label	Meaning
type/bug	Reproducible incorrect behavior.
type/preservation-gap	Missing, unverified, or at-risk artifact/knowledge.
type/finding	Reverse-engineering investigation.
type/modernization	Compatibility, maintainability, or safety improvement.
area/server	Server runtime/build/database work.
area/client	Client snapshot, launcher, patch, or user-data work.
area/archive	Mirrors, metadata, checksums, backups, or recovery.
area/tooling	Game Server Manager or supporting tool problem.
risk/destructive	Data loss or irreversible action is possible.
risk/security	Security-sensitive; use a private reporting path when disclosure would create risk.
status/needs-evidence	Cannot progress without a reproducible record or artifact.
status/blocked-upstream	Depends on an upstream decision or unavailable source.
priority/high	High preservation priority.
priority/medium	Medium preservation priority.
baseline/trinitycore-335	First TrinityCore 3.3.5 vertical baseline.

Use milestones for a baseline or preservation campaign, such as Meteor P3 baseline or 2026 Q3 restore drill.

Severity

Severity	Definition
S0	Active security/privacy incident or loss of an irreplaceable only copy. Handle privately first.
S1	Corruption, destructive behavior, or complete failure of a verified baseline.
S2	Major function broken; workaround is risky or incomplete.
S3	Limited defect with a safe workaround.
S4	Documentation, metadata, ergonomics, or low-risk cleanup.

Preservation-critical tracklist

Gap ID	Area	Description	Priority	Issue
GAP-001	All servers	Exact server/client compatibility matrix needs independent verification records.	High	#1
GAP-002	Mirrors	Complete LFS/submodule checks, remaining bundles, and restore tests.	High	#2
GAP-003	Project Meteor	Legacy build/runtime dependencies and client-derived script assets need complete capture and provenance.	High	#3
GAP-004	Sapphire	Pinned server revision → ffxivgame.ver mapping needs verified baselines.	High	#4
GAP-005	Aura Kingdom	Dead/missing historical release sources need explicit availability records and lawful recovery attempts.	High	#5
GAP-006	Backups	Complete an isolated Forgejo plus artifact-store restore drill.	High	#6
GAP-007	LandSandBoat	First pinned P3 client/server baseline and extracted-data manifest are missing.	Medium	#7
GAP-008	TrinityCore master	Time-series retail client/server mapping and a retained known-good baseline are missing.	Medium	#8

Do not delete a gap row when its issue closes. Mark it resolved and retain the durable evidence link.

Active baseline

Issue #13 tracks Baseline TC335-001. It is explicitly blocked on an authorized WoW 3.3.5a build-12340 snapshot and a Linux verification environment.

Definition of ready

A bug is ready for implementation when it includes affected baseline/artifact IDs, environment, reproduction steps, expected and actual results, logs or evidence with sensitive data removed, severity, and rollback/data-loss considerations.

Definition of done

• The root cause or preservation gap is documented.
• A fix, recovery, or explicit accepted limitation is recorded.
• Regression or smoke-test evidence is attached.
• Derived artifacts point to their inputs and checksums.
• Documentation and affected baseline/profile are updated.
• Backup/rollback is tested for destructive changes.

Use Template — Bug when opening an issue.