Forge-Operational-Improvements-Mod

Update GitHub Repository

Standard update workflow

From the module root:

git status
git pull origin main
npm run check
git add module.json README.md HOW_TO_USE.md .github/workflows/release.yml scripts/ styles/ templates/ packs/
git commit -m "Describe your changes"
git push origin main

Pushing to main now publishes module.json and module.zip to the GitHub Release that Forge reads from the manifest URLs. Pushing to feature branches does not update Forge, because the manifest points to GitHub release assets rather than branch files. If you want Forge to detect a new update, module.json version must change before the main push.

Release workflow (Forge/GitHub latest assets)

Use the release script to bump version, commit, tag, and push in one step:

./scripts/release.ps1 -Version 2.1.0 -Message "Release"

What it does:

• Updates module.json version
• Creates a commit
• Creates tag vX.Y.Z
• Pushes main and tag to GitHub

Export procedure (local DIST only)

Use this when you want a local test/export package without publishing to GitHub:

1. Stage runtime-only package contents locally:

npm run prepare:package

2. Zip dist/staging-public/staging/ into your local test artifact if needed.
3. Do not run git add -A for export-only steps.
4. Stage only intended source/manifest/docs files with explicit paths.

Recommended safe staging command:

git add module.json README.md scripts/ styles/ templates/ packs/

Before committing, verify no build artifacts are staged:

git status --short

Expected: no dist/, release/, .zip, .sha256.txt, or .staging-local-test/ entries in staged changes.

Founder-first private manifest release

Build founders release assets (for a private GitHub repo release):

./scripts/build-founders-release.ps1 -Version 2.1.0 -PrivateRepo <owner>/party-operations-founders

Then upload dist/founders/module.json and dist/founders/module.zip to the private repo release.

Current Release Highlights (2.1.0)

• Integration sync now recovers from stale/missing ActiveEffect references instead of failing.
• Operations view uses consistent pill-style navigation and expanded single-column layout.
• Marching torchlight now supports per-actor Bright/Dim ranges with persistence and chat/export visibility.

After pushing

1. Check GitHub Actions and confirm the release workflow succeeds.
2. Confirm the latest Release has module.json and module.zip assets.
3. Forge will detect updates from the existing releases/latest manifest URL.