Fix the frontend release-gate smoke test (#187)

* Make the GitGuardex rename publishable and cheaper to load

The long-form CLI surface, installed skill/command paths, and startup templates now use GitGuardex while keeping gx as the short entrypoint and guardex as a compatibility alias. The fixed-context templates were trimmed again and the release workflow repository gate was corrected so the version bump is actually releasable from the documented repo.

Constraint: Existing gx and guardex callers must keep working during the rename

Constraint: The fixed context files must shrink without breaking setup/install expectations

Rejected: Renaming the npm package itself in the same patch | higher migration risk than the user asked for

Confidence: high

Scope-risk: moderate

Reversibility: clean

Directive: Keep gitguardex as the primary long-form surface and only remove legacy guardex aliases with an explicit migration plan

Tested: node --check bin/multiagent-safety.js; node --test test/install.test.js test/metadata.test.js; NPM_CONFIG_CACHE=/tmp/gitguardex-npm-cache npm pack --dry-run; openspec validate agent-codex-rename-guardex-to-gitguardex-and-slim-fi-2026-04-21-01-29 --type change --strict

Not-tested: Live GitHub PR merge flow and live npm publish from CI

* Keep the release path aligned with the renamed repo

GitHub redirected the pushed branch to recodeee/gitguardex, so the release workflow gate and repository metadata needed to follow the canonical repo name. README links and the metadata regression test now point at the same repo slug that PRs and releases actually use.

Constraint: The publish workflow must run in the canonical GitHub repo after the rename

Rejected: Leaving legacy repo URLs in place and relying on redirects | brittle for workflow gates and metadata assertions

Confidence: high

Scope-risk: narrow

Reversibility: clean

Directive: Keep package metadata, README badges, and release workflow repo gates on the same canonical repository slug

Tested: node --check bin/multiagent-safety.js; node --test test/install.test.js test/metadata.test.js; NPM_CONFIG_CACHE=/tmp/gitguardex-npm-cache npm pack --dry-run; openspec validate agent-codex-rename-guardex-to-gitguardex-and-slim-fi-2026-04-21-01-29 --type change --strict

Not-tested: Published npm release from GitHub Actions after merge

* Keep release verification aligned with the frontend runtime

The GitHub release run is blocked by a stale frontend smoke test that still expects next start even though the frontend package intentionally boots through server.js. The test now asserts the documented custom server entrypoint so release verification matches the shipped frontend contract.

Constraint: The release workflow depends on npm test, so stale assertions in unrelated smoke tests can block npm publication

Rejected: Changing the frontend start script back to next start | would mutate runtime behavior just to satisfy an outdated test

Confidence: high

Scope-risk: narrow

Reversibility: clean

Directive: Keep frontend smoke tests synced with the actual server entrypoint before using them as release gates

Tested: npm test; node --check bin/multiagent-safety.js; NPM_CONFIG_CACHE=/tmp/gitguardex-npm-cache npm pack --dry-run

Not-tested: Re-run of GitHub Actions release job after the corrected commit is merged

---------

Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>

Author: NagyVikt

test/frontend-how-it-works.test.js

@@ -6,14 +6,15 @@ const path = require('node:path')
 const repoRoot = path.resolve(__dirname, '..')
 const frontendRoot = path.join(repoRoot, 'frontend')
 
-test('frontend package exposes standard Next.js scripts', () => {
+test('frontend package exposes the documented Next.js plus custom server scripts', () => {
   const packageJson = JSON.parse(
     fs.readFileSync(path.join(frontendRoot, 'package.json'), 'utf8')
   )
 
   assert.equal(packageJson.scripts.dev, 'next dev')
   assert.equal(packageJson.scripts.build, 'next build')
-  assert.equal(packageJson.scripts.start, 'next start')
+  assert.equal(packageJson.main, 'server.js')
+  assert.equal(packageJson.scripts.start, 'node server.js')
 })
 
 test('how-it-works page keeps key workflow copy blocks', () => {