Packet 37 — Rebuild & Replace Stored Deploy Artifact#14
Open
bugsyhewitt wants to merge 6 commits into
Open
Conversation
…guard Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…oyment slot Uploaded alienclaw-deploy-v9.zip to hPanel via Settings and redeploy → Upload new files → Save and redeploy. Managed redeploy completed 2026-05-28 16:56:59. Health returned uptime_seconds: 0, confirming fresh process start from hPanel-managed artifact. Fixes Bug #18.1: SFTP extraction and hPanel deployment slot are independent. - docs/LESSONS_FROM_THE_ARC.md: add Bug #18.1 documenting the two-slot distinction - docs/DEPLOY.md: update upload steps to match actual hPanel Settings and redeploy flow - MEMORY/WORK/: packet-37.1 PRD and working notes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3 tasks
Packet 37.1 — Close hPanel Stored-Slot Gap
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Packet 37 — Verdict
Status: GREEN
Summary
Fresh deploy artifact v9 built from corrected source, extracted to the Hostinger
server, and the app restarted from the extracted content (uptime_seconds: 0 confirms
clean start). No live SSH patch is load-bearing. Reproducible build script with
top-level-await guard committed. Deploy process documented.
Phase results
{"status":"ok","version":"1.0.0","uptime_seconds":0}post-restart{"install_id":"5b6610b71c1a31ca","status":"registered"}The key proof
The app was restarted after extracting the v9 artifact.
uptime_seconds: 0at thehealth check confirms the process started fresh from the extracted files. MySQL
connectivity and persistence were verified immediately after. No load-bearing live
patch remains.
Artifact details
/tmp/alienclaw-deploy.zipviascripts/build-deploy.shdist/main.js(26.4KB esbuild bundle),server.js(349B),package.json(178B)/home/u881291242/alienclaw-deploy-v9.zipBug caught this packet
Outstanding for Bugsy
~/alienclaw-deploy-v9.zipbut the "stored artifact" in Hostinger's deploymentsystem is still v8 (the broken one). Next hPanel session: upload v9 via
Node.js Apps → Deployments → Upload. The running app is already from v9 content
(extracted this packet). This closes the loop in Hostinger's own records.
.env.hostinger(outstanding from Packet 35)Branch note
Branched from
packet-36-cleanup-polish(not main) because PRs #12/#13 not yetmerged. Merge order: #12 → #13 → this PR.