fix(#1): [BOUNTY $20] No issue tracker usage — 30 repos, 0 issues — problems live only in sessions

[CribaGIT]

Bootstrap GitHub Issue Tracking Substrate

Description

This PR resolves the meta-task of setting up issue tracking across the core @COMMENCINGTHESCOURGE repositories, ensuring that findings, bugs, and enhancements are properly tracked in GitHub rather than living statelessly in session transcripts and audit reports.

Changes

• Added scripts/bootstrap-issues.js: A standalone Node.js script utilizing the GitHub REST API to bootstrap our issue tracking infrastructure.
• Enabled Issues: The script automatically enables the GitHub Issue tracker across all core repositories (flux-chamber, aetherion-continuum, hyperpoly-terrain, trench-builder, and erdos-straus-solver).
• Standardized Labels: Defines and enforces a common label taxonomy (bug, enhancement, bounty, documentation, wontfix) across the core repositories with standardized colors.
• Migrated Findings: Extracted the 6 key compute infrastructure findings originally present in automation_audit.py and built them into the bootstrap script. Upon execution, these findings are filed as officially tracked issues in the erdos-straus-solver repository with the auto-generated audit-auto label.
• Updated package.json: Added the "bootstrap-issues" run script for easier execution.

Instructions for Maintainers

To apply these changes and bootstrap the issue tracker, you must execute the script with a valid GitHub Personal Access Token (PAT) that has repository (repo) permissions.

# Export your GitHub token
export GITHUB_TOKEN=ghp_your_personal_access_token

# Run the bootstrap script
npm run bootstrap-issues

Note: This script is idempotent where possible. It will patch existing labels with standard colors/descriptions and gracefully skip label creation if they already exist, but it may create duplicate issues in erdos-straus-solver if run multiple times without checking existing issues.