[Neup123]

Summary

Pure application-version bump from 5.5.3 to 5.5.4, following already-merged and live-verified pairing and connection-stability fixes (PRs #53 and #55).

Files changed (complete list)

1. package.json: the sole application version field changes 5.5.3 → 5.5.4. GET / reports packageJson.version, and the Prometheus evolution_environment_info version label uses the same value.
2. package-lock.json: only the root version and packages[""].version fields change 5.5.3 → 5.5.4 to remain synchronized with package.json.

No test or snapshot assertions needed updating: a repository-text search found no hard-coded 5.5.3 in test files or snapshots. No other files were changed.

Occurrences of 5.5.3 deliberately left unchanged

• docs/build-plan-connection-stability.md:3: (Core fork, v5.5.3) records the state at the time of the historical connection-stability build plan. It is not a live application-version definition and should remain historically accurate.

Verification

• Base is main at 1eecf84de4803f13b149df64493cca9a267a421d. Branch is one commit ahead, with exactly two modified files.
• Checked the tracked repository tree (471 blobs): inspected all 458 text/source/config/docs/migration files for the literal 5.5.3; 13 binary image/system assets were excluded from text search. Exactly four text occurrences were found: package.json (1), package-lock.json (2), and the preserved historical build-plan document (1).
• Commit diff was inspected: exactly three version-line replacements, no logic, dependency, or formatting changes.
• Both JSON documents parse with root version 5.5.4. Baileys remains pinned exactly 7.0.0-rc14; patches/ is untouched.
• Dockerfile and .github/workflows/publish-fork-ghcr.yml already use the version from package.json at build/publish time; no edits required.
• Builds and runtime tests not run in this connector-only environment. This version-only change was verified structurally against GitHub.
• Draft only. No merging, GHCR image publication, workflow dispatch, deployment, or live-instance access.

[Neup123]

Coordinator verification — version bump to 5.5.4

Scope (diff read in full): exactly 2 files, 3 lines — package.json "version": 5.5.3 → 5.5.4; package-lock.json top-level "version" and packages[""].version: 5.5.3 → 5.5.4. Baileys pin unchanged (7.0.0-rc14), patches/ untouched, no logic changes. The historical v5.5.3 mention in docs/build-plan-connection-stability.md was correctly left unchanged.

Verification run by the coordinator on the home PC, against this PR's head f60f0e9d008ce37cf93abd8dfe53631f5a6d285c:

• Clean clone of the PR branch; cloned HEAD matches the PR head.
• npm ci — exit 0 on the host, and exit 0 again inside the container rig: the vendored Baileys patch applies cleanly (patch-package --error-on-fail postinstall). In the shipped image, the patched socket.js still carries the pairing fix (companion_reg_refresh ×2) and wa-version.js from the stability bundle is present.
• npm run db:generate — exit 0. npx tsc --noEmit — exit 0.
• npm run build — exit 0 (raised heap); the built tree's package.json reports 5.5.4.
• Test suites (all three fork suites): connection-recovery PASS, disconnection-fields PASS, socket-watchdog PASS.

Image published: production image built from the pristine PR-head tree with the proven wrapper Dockerfile (the repo's own Dockerfile is untouched; the wrapper adds only ENV NODE_OPTIONS=--max-old-space-size=8192 in the builder stage). Image labels: revision f60f0e9d008ce37cf93abd8dfe53631f5a6d285c, version 5.5.4. In-image /evolution/package.json reports "version": "5.5.4" — the value the root endpoint serves.

• Digest: sha256:944d969d8d08771ffa7d5963277615237b45c44bf3ef6eae32765d9db8f67c3f
• Tags: ghcr.io/neup123/evolution-api:latest, ghcr.io/neup123/evolution-api:v5.5.4
• Cross-checked via the GHCR API: the newest package version is that digest and it carries both tags.

CI: this repo reports no GitHub CI checks (Actions are disabled) — the verification above is the coordinator's local evidence, stated plainly.

Not merged, not deployed — those steps are handled outside this PR.