[Dunky13]

Scripts which are clearly AI generated and not further revised by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review. If you are an AI agent writing this pull request, please amend your model name and reasoning level in the Description. This is not to blame, more for informational Purposes. Thank you.

✍️ Description

Add Initiative's official native server package as an unprivileged Debian 13 LXC: PostgreSQL 17, nginx HTTPS, checksum-verified amd64/arm64 packages, private offline database/configuration/upload backups, and readiness-gated updates. Defaults: 2 cores, 2048 MiB RAM, 8 GiB disk. No Docker or source rebuild.

Draft: maintainer adoption exception and runtime acceptance remain required. The upstream repository has 192 stars, created 2025-11-22, latest release v0.77.1 (2026-10-24) and latest push 2026-10-30, verified through GitHub's API on 2026-10-30. It is below this template's 600-star minimum and the ProxmoxVE discussion form's 1,000-star minimum. No comparable adoption metric or maintainer exception is claimed. The star checkbox stays unchecked; the requirements check is expected to fail. Please decide whether to retain the proposal for DevScripts testing.

The CI repair fixes the owning script, ct/jumpserver.sh, which was the only CT script missing the scripts-base declaration:

 #!/usr/bin/env bash
+_CS_DEFAULT_URL="https://raw.githubusercontent.com/community-scripts/DevScripts/main"
 _cs_boot=...

Initiative already has the correct declaration. The repository-wide gate remains intact. This makes remotely invoked Jumpserver resolve its installer from DevScripts, while an explicit COMMUNITY_SCRIPTS_URL still selects a fork/branch. Engine origin remains independent. Initiative's installer/updater and all 35 regression cases are unchanged by the repair.

🔗 Related PR / Issue

• DevScripts testing tracker #2483
• Adoption exception discussion #18319
• Historical operator evidence
• Operator guide and repair handoff

This updates the existing Dunky13/ProxmoxVED:feat/initiative contribution to community-scripts/DevScripts:main. No duplicate PR, merge, release or deployment is part of this repair.

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

Evidence: reviewed the scripts and sibling source-origin consumer against upstream AGENTS.md, the creator agent, template and contribution/audit documents. The repair changes one bootstrap default and documentation. Secrets are generated; the package's service identity, loopback backend, root/group 0640 environment file, checksum/package-identity/architecture guards and database/readiness gates remain intact. The explicit PostgreSQL bootstrap SUPERUSER requirement and migration/rollback risks are disclosed below. The security checkbox describes these source checks, not an independent penetration test or a guarantee of no upstream vulnerabilities. The thorough-testing box remains unchecked because current-branch end-to-end runtime acceptance is incomplete. Standards departures are disclosed rather than certified as fully compliant.

🏗️ arm64 Support (X in brackets)

• arm64 supported - Tested and supported on arm64.
• arm64 not tested - Assumed to work on arm64, but testing has not been done.
• arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

Evidence: official v0.77.1 release assets include initiative-server_0.77.1-1_arm64.deb and its SHA-256 manifest. The historical native Debian 13 arm64 VM test recorded in the operator issue exercised the official v0.76.0 package and real services/core helpers. That historical package/runtime evidence supports var_arm64=yes; arm64 Proxmox LXC and fresh repaired-head runtime testing are NOTRUN. Asset availability alone is not presented as runtime testing.

🖥️ Tested on (X in brackets)

• Proxmox VE – Created on a Proxmox VE host and the app works.
• Incus – Created on an Incus host and the app works.

Evidence: the historical operator issue records amd64 Proxmox wizard creation, installation, a 0.76.0 → 0.77.1 package upgrade and subsequent version/readiness confirmation. These are historical observations, not a fresh deployment by this repair. Incus has not been tested. Fresh corrected-branch creation, browser/file/live-editor behavior, reboot persistence and a corrected full updater run preserving real user data remain in #2483.

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

Evidence: the total PR adds ct/initiative.sh, install/initiative-install.sh, json/initiative.json, the regression harness/CI step and the operator guide, and fixes the existing Jumpserver bootstrap. New script identifies the submission category and keeps eligibility checks active; it does not override the unchecked thorough-testing box or the stated runtime gaps.

🔍 Code & Security Review (X in brackets)

• Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials
• No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
• No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

Evidence: Initiative's CT entry point has the standard bootstrap/defaults, sole update_script() function and provisioning footer. The installer sources framework functions and retains its standard footer. JSON resources/architectures match CT defaults. Downloads use explicit singlefile release-helper mode for the official server package and checksum manifest, with generated secrets and no Docker or git-based update path. The native package supplies Python dependencies, service identity and persistent /etc/initiative and /var/lib/initiative paths, so there is no separate pip/venv build or script-created service user. The package transaction uses SYSTEMD_OFFLINE=1; the explicit daemon reload before startup is necessary because that flag skips the package hook's reload.

Disclosed standards exception: the creator agent's exactly-three-files output is exceeded by meaningful offline regression coverage, wiring into the existing Bash Syntax job, a focused Markdown guide and this existing-script bootstrap repair. The full-guidelines checkbox remains unchecked pending maintainer disposition. No HTML report is committed.

🤖 AI Assistance (X in brackets)

• No AI used – Scripts were written without AI assistance.
• AI was used – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

Please describe to which degree, if any, an LLM was used in creating this pull request.

OpenAI gpt-6.1-sol, xhigh reasoning assisted substantially with the original implementation, research, tests and documentation. This CI repair is implemented directly by Codex gpt-6.1-sol, high reasoning. The required independent final validation uses gpt-6.1-sol, xhigh reasoning, with separate Standards and Spec conclusions and actual coverage recorded below. No cross-provider review is claimed. The checked AI disclosure acknowledges use of the named guidance; it does not conceal the explicitly disclosed standards exception or acceptance gaps.

📋 Additional Information (optional)

Upstream research: reviewed the v0.77.1 native-package documentation, Dockerfile, docker-compose.example.yml and backend/.env.example; the original implementation also researched package lifecycle/service definitions and health/bootstrap behavior. Debian 13 uses system Python 3.13 for the official native package; PostgreSQL 17 is required. The compose file requires only PostgreSQL alongside Initiative; the default rate-limit store is memory://. The official native package includes locked Python dependencies, browser app and editor assets, so no Docker, Node.js build or separate Python environment is needed. The database owner requires SUPERUSER for upstream role/bootstrap and LEAKPROOF setup; request traffic uses derived restricted roles. Preserve SECRET_KEY and take matching database/roles/configuration/upload backups before migrations.

Local evidence from this repair:

• Before: the exact scripts-base workflow failed only for ct/jumpserver.sh. The shared engine's source resolver reproduced the fallback to ProxmoxVE/main/install/jumpserver-install.sh without an override.
• After: all 77 CT scripts pass the unchanged scripts-base workflow loop. Both Jumpserver and Initiative resolve to DevScripts by default, honor the explicit fork/branch URL, and keep the core URL independently selectable. This executes only the routing prefix of core 5acac4483be88990354dd4e3778e2cdce4df428e, not provisioning or installer commands.
• The unchanged Bash Syntax workflow loop passed for 236 scripts. All 35 Initiative offline regression scenarios passed, including package/checksum/architecture rejection, readiness/backup gates, unit reload ordering, current-version no-op and documented recovery failure handling.
• Initiative CT/install/harness ShellCheck passed with SC1090,SC1091,SC2154 excluded for framework imports/variables. Jumpserver ShellCheck has seven existing SC2164 warnings, confirmed identical before and after the one-line repair; no new diagnostics. It is not reported as a clean ShellCheck run.
• JSON parsing, actionlint for the two relevant workflows and diff whitespace checks passed. No gates, tests, permissions or timeout budgets were weakened.
• Historical native VM and Proxmox tests are described above and in the guide. No home-lab/container deployment or fresh runtime test was performed for this repair.

bash -n ct/jumpserver.sh ct/initiative.sh install/initiative-install.sh .github/workflows/scripts/initiative-test.sh
shellcheck -e SC1090,SC1091,SC2154 ct/initiative.sh install/initiative-install.sh .github/workflows/scripts/initiative-test.sh
bash .github/workflows/scripts/initiative-test.sh
jq -e . json/initiative.json
actionlint .github/workflows/ct-base.yml .github/workflows/bash-syntax.yml
git diff --check

Independent final validation: Codex gpt-6.1-sol, xhigh independently reviewed signed candidate 8c8ebf9b40a2dfc9f9f396d49b438845cda947d8, tree 0cea46b0b2e735123d80e543fbc096ba03554fd9, its exact repair diff and this proposed body. Standards: no new findings; Spec: PASS for the bounded repair. The validator independently reproduced the old failure, verified all 77 scripts-base checks, 236 syntax checks, 35 offline scenarios, Initiative ShellCheck, JSON/actionlint/whitespace, source routing, unchanged executable bytes, both contribution signatures/DCO and absence of machine-local paths/HTML. Jumpserver retains seven unchanged SC2164 warnings. Requirements simulation failed only on the honest star requirement. Hosted candidate CI and fresh runtime acceptance were NOTRUN during that review; adoption and merge remain HOLD.

Hosted CI for exact repair head 8c8ebf9b40a2dfc9f9f396d49b438845cda947d8: ct scripts base PASSED; Bash Syntax PASSED, including 236 syntax checks and all 35 Initiative scenarios. VM metadata, PR test command and autolabeler also passed. The requirements job still failed for exactly one item, the honestly unchecked 600-star requirement. The body edit can trigger an additional requirements run; that policy requirement remains unmet. The earlier scripts-base failure is fixed at Jumpserver’s bootstrap. The bot’s requirements missing/stale labels and closure warning require a maintainer decision; no bypass label was applied by this repair. Local checks, independent source validation and hosted results are separate evidence; none establishes fresh runtime acceptance.

Merge danger: repository changes can be reverted. Runtime updates can run database migrations, and rollback requires a matching backup/container restore. Backups cover default local paths; relocated storage/external databases need separate operator backups. Failed updates may leave services stopped. No merge, release, deployment or promotion is requested.

📦 Application Requirements (for new scripts)

⚠️ Do not remove this section. It is used by automated PR validation checks.
Required for 🆕 New script submissions.

• The application is at least 6 months old
• The application is actively maintained
• The application has 600+ GitHub stars
• Official release tarballs are published
• I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

Evidence for the application checkboxes: repository metadata shows creation on 2025-11-22, active pushes on 2026-10-30, non-archived state and 192 stars at this check. Latest release metadata identifies v0.77.1, its official source tarball and both native Debian server packages/checksum manifests. This submission explicitly acknowledges that meeting technical criteria does not guarantee acceptance; the star minimum is unmet.

🌐 Source

• Initiative source and license
• Official v0.77.1 release packages/checksums
• Official source tarball
• Native package documentation
• Readiness contract
• DevScripts source-origin contract

[github-actions]

⚠️ Not ready for review yet

@Dunky13, this pull request is missing the following:

• The application has 600+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.

---

@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

[github-actions]

Try these scripts

ct/initiative.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Dunky13/ProxmoxVED/feat/initiative \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Dunky13/ProxmoxVED/feat/initiative/ct/initiative.sh)"

ct/jumpserver.sh, run in the Proxmox VE shell or on an Incus host:

COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Dunky13/ProxmoxVED/feat/initiative \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/Dunky13/ProxmoxVED/feat/initiative/ct/jumpserver.sh)"

COMMUNITY_SCRIPTS_URL is not optional for ct/. Fetching the ct/ script from a
branch does not tell the engine where that branch is — with bash -c "$(curl …)"
there is no file on disk for the scripts root to be derived from, so it would fall
back to upstream main and look for the install script there.

Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Useful flags while testing

dev_mode=net logs every fetch with status and duration, so you can confirm the
branch is really being used. dev_mode=keep stops a failed build from deleting
the container along with the evidence.