@synopackageland/cli 0.7.3 → 0.9.0

package/dist/templates/native-authorization/i18n/zh-TW.json

@@ -1,37 +0,0 @@
-{
-  "authorization.title": "{package} 需要授權",
-  "authorization.purpose": "此套件執行固定的 root 操作前需要核准。密碼由 DSM 處理，套件不會看到或儲存。",
-  "authorization.reason.grant_missing": "尚未授權 root 操作。",
-  "authorization.reason.upgrade_reapproval": "套件已透過套件中心更新，先前的授權已撤銷。",
-  "authorization.reason.helper_untrusted": "無法信任特權 helper。",
-  "authorization.reason.cli_untrusted": "無法信任特權命令。",
-  "authorization.reason.grant_incompatible": "特權 helper 需要更新。",
-  "authorization.reason.package_identity_changed": "套件帳號已變更。",
-  "authorization.reason.maintenance_task_missing": "找不到維護任務。",
-  "authorization.reason.maintenance_task_mismatch": "維護任務已與授權不符。",
-  "authorization.reason.helper_health_rejected": "特權 helper 未通過健康檢查。",
-  "authorization.reason.capability_missing": "特權 helper 缺少必要的能力。",
-  "authorization.reason.unknown": "授權已遺失或不再有效。",
-  "authorization.next.install": "選擇「授權」，並以 DSM 密碼確認，即可核准此版本。",
-  "authorization.next.update": "此版本需要重新授權。請選擇「授權」，並以 DSM 密碼確認。",
-  "authorization.next.repair": "請在任務排程表中檢查此套件的任務，再重試。",
-  "authorization.authorize": "授權",
-  "authorization.authorizing": "正在等待 DSM…",
-  "authorization.failed": "授權未完成，請再試一次。",
-  "authorization.unavailable.title": "無法檢查授權",
-  "authorization.unavailable.body": "這通常是暫時的。請再試一次，{package} 不會要求輸入密碼。",
-  "authorization.credential.title": "DSM 的登入憑證尚未就緒",
-  "authorization.credential.body": "此 DSM 工作階段是還原而來，並未使用密碼登入，因此 DSM 無法為 {package} 的要求作證。請登出 DSM，以密碼重新登入，然後再開啟 {package}。",
-  "authorization.retry": "重試",
-  "authorization.next.reinstall": "安裝的檔案與此版本不符。請從可信任的來源重新安裝套件，再重試。",
-  "authorization.not_admin.title": "需要管理員處理",
-  "authorization.not_admin.body": "請 DSM 管理員開啟此套件並完成授權。",
-  "authorization.session_expired.title": "登入已逾時",
-  "authorization.session_expired.body": "請重新登入 DSM，再開啟此套件。",
-  "authorization.ready": "已授權",
-  "authorization.revoke": "撤銷授權",
-  "authorization.revoke.title": "撤銷授權？",
-  "authorization.revoke.body": "新的 helper 存取將被停用。套件資料與過往結果會保留。",
-  "authorization.cancel": "取消",
-  "authorization.checking": "正在檢查授權…"
-}

package/dist/templates/native-go/README.md

@@ -1,459 +0,0 @@
-# __DISPLAY_NAME__
-
-A native DSM package (`__PACKAGE__`): a Go backend that DSM runs as a CGI,
-and a UI that opens in its own DSM window. It installs as an **unsigned** SPK,
-runs as its own DSM package account, needs no containers, and has no root by default.
-
-```text
-DSM main menu → DSM window (ui/app.js)
-                   │  ctx.call("greeting.get")  same-origin POST + DSM session
-                   ▼
-   /webman/3rdparty/__PACKAGE__/cgi/api.cgi   (backend/, runs as package user)
-      1. transport guards: POST, JSON, same origin, ≤ 1 MiB, bounded JSON complexity
-      2. one DSM authentication (unless the route is Public)
-      3. route policy: User or Admin  → refusal before any handler
-      4. your handler (backend/internal/app)
-```
-
-## Quick start
-
-Needs Node.js with `synopkgland` installed, and Go 1.25+.
-
-```bash
-(cd backend && go test ./...)   # auth policy + route tests
-synopkgland build           # → dist/__PACKAGE__-0.1.0-0001-{x86_64,aarch64}.spk
-synopkgland inspect dist/__PACKAGE__-0.1.0-0001-x86_64.spk
-```
-
-Install: Package Center → Settings → General → Trust Level "Any publisher",
-then Manual Install with the SPK for your NAS's CPU. Open
-**__DISPLAY_NAME__** from the DSM main menu: it shows who you are signed in
-as, what the backend reports, and (for administrators) a form that stores a
-greeting in the package's data folder.
-
-## Capabilities and schema 2
-
-`dsm-package.yaml` requires `schema: 2` and `backend: {kind: go, dir: backend}`.
-Declare `capabilities.files: session` for interactive File Station access,
-`capabilities.jobs: true` for persistent package-account jobs,
-`capabilities.identity: standalone` for independent DSM login, and
-`capabilities.rootOps: true` for administrator-approved fixed executor operations.
-`init --with files,jobs,root-ops` supports plain and Vue UI; `login` and
-`delegate` need the Vue UI. `daemon` cannot be combined with `jobs`, but it can
-be combined with an until-revoked `delegate`.
-
-```sh
-synopkgland add files jobs login
-synopkgland check --json
-synopkgland status --host my-nas --json
-```
-
-`add` writes SDK overlay files and updates capabilities. Your handlers/pages and
-application entry files remain app-owned. Differing existing overlay files and
-modified SDK placeholders cause `ADD_FILE_CONFLICT` with the conflicting paths;
-resolve them before retrying. Already-declared capabilities are a no-op.
-`check`, `build`, `inspect`, `deploy`, `status` emit one stdout object with
-`--json`; failures include `code`, `message`, `hint`.
-
-## Project layout
-
-| Path | What it is | Edit it? |
-| --- | --- | --- |
-| `dsm-package.yaml` | Package identity, version/build, arches, where backend and UI come from | Yes |
-| `ui/app.js`, `ui/app.css` | The app inside the DSM window | Yes — your UI |
-| `ui/…` | Any other assets; served from `/webman/3rdparty/__PACKAGE__/app/` | Yes |
-| `i18n/messages/<locale>.json` | UI text in nine languages | Yes |
-| `i18n/glossary.json` | DSM's own UI terms, and which messages must use them | Add terms |
-| `backend/internal/app/` | Your API: routes and handlers | Yes — your backend |
-| `backend/internal/api/` | The CGI front door: guards, auth order, route policies | Rarely |
-| `backend/internal/dsm/` | DSM session check and administrators lookup | Rarely |
-| `backend/cmd/app/` | Wires the above together | Rarely |
-| `dist/` | Built SPKs (ignored by git) | No |
-
-`build` generates everything else: `INFO`, `conf/privilege`
-(`run-as: package`), no-op lifecycle scripts, icons, the DSM window wrapper
-(`ui/config`, `ui/window-<build>.js`) and the CGI at `ui/cgi/api.cgi`.
-
-## Add an API operation
-
-Add a handler in `backend/internal/app/routes.go`. Every method defaults to
-DSM administrator membership, resolved by its native SDK. All access rules live in
-`backend/internal/api/permissions.json`, including launcher access:
-
-```go
-func Routes(cfg Config) []api.Route {
-	return []api.Route{
-		api.Handle("app.status", cfg.status),
-		api.Handle("greeting.get", cfg.getGreeting),
-		api.Handle("greeting.set", cfg.setGreeting),
-		api.Handle("notes.list", cfg.listNotes),   // new: administrators by default
-		api.Handle("notes.purge", cfg.purgeNotes), // new: administrators by default
-	}
-}
-
-func (cfg Config) listNotes(ctx context.Context, caller api.Caller, params json.RawMessage) (any, error) {
-	var in struct{ Limit int `json:"limit"` }
-	if err := decodeParams(params, &in); err != nil {
-		return nil, err
-	}
-	return map[string]any{"owner": caller.User(), "notes": []string{}}, nil
-}
-```
-
-Then add the method's valid params to `sampleParams` in `routes_test.go`; the
-test fails until you do, and once you do it proves the new route refuses
-callers without a session and ordinary users without touching
-the data folder.
-
-Call it from the UI with `ctx.call("notes.list", { limit: 20 })`. Errors
-reject with `{ code, message }`, for example `session_required`,
-`admin_required`, `bad_request` or `internal`.
-
-### Who can call what
-
-The shipped policy is:
-
-```json
-{"schema": 1, "default": "administrators", "methods": {}}
-```
-
-The default must remain `administrators`. An intentional exception belongs in
-`methods`, for example `"notes.list": "authenticated"`; `"public"` explicitly
-allows anonymous calls. Such exceptions also enable ordinary-user launcher
-access. The template ships no exceptions and sets DSM `allUsers` to `false`.
-
-| JSON rule | No session | Ordinary user | Administrators group member |
-| --- | --- | --- | --- |
-| absent or `administrators` | `session_required` | `admin_required` | runs |
-| explicit `authenticated` | `session_required` | runs | runs |
-| explicit `public` | runs | runs | runs |
-| unregistered method | `session_required` | `unknown_method` | `unknown_method` |
-
-Missing or invalid JSON, duplicate keys, unknown permissions and rules for
-unregistered methods fail closed. The CLI validates the file and binds its
-SHA-256 digest to the compiled CGI, which checks it at startup before migration.
-Changing policy requires rebuilding the SPK; request parameters cannot alter it.
-Legacy `api.User`, `api.Admin` and `api.Public` constructors remain compatibility
-aliases for handler registration and do not grant access. Use `api.Handle` for
-new routes. Binary reads cannot be configured as anonymous.
-
-Every reply, error or not, is HTTP 200 with `{"success": false, "error":
-{"code", "message"}}` on failure, the same convention as DSM's own WebAPI.
-DSM's web server replaces the body of any CGI reply with status 403, 404 or
-5xx by its own HTML error page, so a status-coded error would never reach your
-UI.
-
-JSON replies include an exact `Content-Length` in bytes, including refusal and
-serialization-failure envelopes. This avoids truncated chunk framing on DSM's
-CGI bridge; serialization failures retain HTTP 200 and return `internal`.
-
-`filestation.UploadStream` streams an application-selected reader under the
-current caller's File Station session, capped at 16 GiB and twenty minutes.
-Its upload transport has a separate bounded response-header deadline; ordinary
-metadata requests retain their shorter deadline. No overwrite, retries, parent
-creation or saved credentials are added. A missing commit receipt remains
-`commit-uncertain` and requires reconciliation before another write.
-
-- Handlers get an `api.Caller` the server built after authenticating; code
-  outside `internal/api` cannot construct an authenticated one.
-- A JSON `public` exception runs with **no** DSM login; the template ships none.
-- "Administrator" is DSM's native administrator decision, including local, AD
-  and LDAP accounts. `dsm.IsAdministrator` invokes `SLIBGroupIsAdminGroupMem`
-  with real-time checking on every authenticated request. No group-name or
-  account-name comparison, UID shortcut, SDK cache, or `/etc/group` fallback
-  grants access. Unknown/error/timeout results refuse access.
-
-## How authentication works (and its limits)
-
-Before decoding JSON, the CGI parsers reject nesting deeper than 32
-containers or more than 65,536 structural bytes (`{}[],:` outside strings).
-The shared scanner uses constant memory; strings still obey the body's byte
-limit. This bounds JSON allocation amplification even for anonymous callers
-and explicitly public routes. It does not replace authentication or network
-rate limiting. Existing generated projects need to adopt the updated backend
-files; rebuilding the CLI alone does not update their source.
-
-The CGI hands only the session carriers (`Cookie`, `X-SYNO-TOKEN`, client
-address) to DSM's own `/usr/syno/synoman/webman/modules/authenticate.cgi`,
-which prints the signed-in user name. The backend never parses the session
-cookie and never takes a user name or admin flag from the request.
-
-Cross-site requests are refused: the API accepts only `POST` with
-`Content-Type: application/json` (which forces a CORS preflight DSM never
-approves), and it rejects `Sec-Fetch-Site` other than `same-origin` and any
-foreign `Origin`. The DSM window wrapper sends DSM's `SynoToken`, but when DSM
-has `enable_syno_token=no` that token proves nothing, so the same-origin
-checks are what stop cross-site requests.
-
-Known limits:
-
-- Each request reuses the browser's DSM session; it does not carry DSM's
-  per-request `X-SYNO-HASH` proof. Verifying that proof needs private,
-  version-specific DSM libraries through a C bridge, so it is not part of this
-  template.
-- Directory reachability and DSM name-service freshness affect native role
-  checks. The bridge bypasses DSM's administrator-role cache but cannot force
-  an upstream directory replica to be current. It refuses unknown results.
-- The static Go CGI embeds a minimal native bridge for Linux amd64/arm64/armv7,
-  reproduced with Zig 0.16.0 from `internal/dsm/native/admin_check.c`. The bridge
-  runs from a sealed memory file with a clean environment, a 3-second deadline
-  and bounded output; no runtime Zig, compiler, writable executable or root
-  privilege is required. The ELF files and build/source hashes are recorded in
-  `native/provenance.json`. DSM must expose the native SDK symbol; otherwise
-  authentication refuses access.
-- Kernels without `memfd_create` (DSM 7 on Linux 3.10: armv7 and the x86_64
-  `avoton`, `braswell`, `bromolow`, `grantley` and `cedarview` platforms) cannot
-  seal the bridge. Only there, the CGI stages it in the package's own
-  `/var/packages/<package>/tmp` (DSM mounts `/tmp` noexec): a fresh 0700
-  directory, a 0500 file reopened read-only and unlinked before it runs. The
-  seal guarantee is lost: between the write and the unlink, a process running
-  as the same package account could replace the bridge. That account already
-  runs the CGI, so the bridge never trusts anything that account does not
-  already control; other accounts cannot write the directory, which must be
-  owned by the package account and not group- or world-writable. Any other
-  memfd failure still refuses.
-
-## Customize the UI
-
-`ui/app.js` must register `window.DsmPackageApps[<package>].mount(root, ctx)`
-(the template shows how, using `document.currentScript.dataset.package`).
-`ctx.call(method, params)` is the only transport. `ctx.reopen(fn)` runs `fn`
-whenever DSM shows the window again and returns an idempotent unsubscribe function. Scope your CSS under your own root class:
-every DSM app shares one page.
-
-Plain JS and Vue receive the same `ctx.host` adapter. `ctx.host.platform()`
-returns a fresh frozen snapshot: `web`, `host` (`dsm`, `standalone-web` or
-`unavailable`), `dsmStandalone`, `dsmLanguage`, `appLocale`, `systemVersion`,
-`fullVersion`, and `theme`. Unknown fields are `null`; `theme` stays unknown.
-DSM launch mode is separate from plain-web fallback, and `appLocale` is the
-app's catalog locale, which may differ from DSM's UI language code.
-
-```js
-const platform = ctx.host.platform();
-const result = ctx.host.setTitle('My notes');
-if (result.status !== 'ok') showTitleStatus(result.status);
-```
-
-`setTitle` enables DSM HTML encoding or assigns standalone `document.title`.
-It returns `{status: 'ok', target: 'dsm-window' | 'document'}` on synchronous
-completion, or `unsupported`, `unavailable`, `invalid-input`, `failed` statuses.
-A missing DSM method is unsupported; it never changes the DSM desktop's title.
-Destroy disposes the adapter and clears reopen handlers; retained adapters
-return unavailable. Navigation exposes activateWindow/requestClose/openApp/openURL;
-requests do not acknowledge completion. `ctx.host.subscribe('window-resize', fn)`
-returns `{status: 'subscribed', dispose}` only for a verified DSM window with on/un.
-The callback receives no native arguments. Remove your subscriptions on unmount;
-wrapper destroy also cleans them. `host-theme-change` and `host-language-change`
-return unsupported: no third-party host event is proven. These observations do
-not authorize work.
-
-`ctx.host.openFileManager('/example-share/docs')` requests File Station folder
-navigation; `revealFile('/home/report.txt')` requests a file highlight. Both require
-a registered, enabled and launchable File Station and report requested plus action,
-not location completion or ACL success. Use canonical virtual share paths only;
-OS `/volumeN/...`, traversal, repeated/trailing slash, controls and backslash are
-invalid. No path conversion or grant is performed. `openFile`, `showFileDetails`
-and `openAppSetting` return unsupported; private preview/details/settings flows
-have no proven generic contract.
-
-File reveal adds a best-effort correction using File Station 1.4.x private
-structures. Required APIs are feature-detected; absent/throwing APIs silently
-cancel and release timers/listeners. One AppLaunch callback binds one receiver;
-only its model may be selected once. Interaction, navigation away from the reached
-parent, close/destroy, disposal and new requests cancel the correction. The named
-5000 ms total budget, 100 ms checks and 300 ms quiet interval have no device latency
-proof. `requested` still does not mean `selected`; actual effectiveness on DSM 7.4 /
-File Station 1.4.4 awaits a rebuilt-SPK device matrix. No second launch or broadcast
-setter is used, and later reloads may still clear selection.
-
-For an independent browser shell, use the SPK's generated `ui/host-0001.js`
-(the number follows the manifest build). It has no Ext or npm runtime dependency:
-
-```html
-<script src="./host-0001.js"></script>
-```
-
-```js
-// shellContext supplies your app's own auth/transport and other context members.
-const ctx = {...shellContext, host: window.DsmPackageHosts.__PACKAGE__({locale: 'en'})};
-const app = window.DsmPackageApps.__PACKAGE__.mount(root, ctx);
-// When your shell unmounts:
-ctx.host.dispose();
-app.unmount();
-```
-
-Serve the generated script with your shell (or reference its same-origin DSM
-static path). `ctx.host` does not create a standalone backend, DSM session,
-cross-origin iframe bridge, or implementations of `ctx.call/t/root/reopen`.
-Standalone title affects the document shared by that shell's mounts.
-
-To build the UI with Vite, Vue or React, point `ui` at the build output and
-give the build command as an argv list (no shell):
-
-```yaml
-ui:
-  dir: web/dist
-  build:
-    cwd: web
-    command: [npm, run, build]
-```
-
-The build must emit `app.js` (one script that registers `mount`) and
-`app.css`. The installed `@synopackageland/ui` package gives Vue components with DSM 7 styling;
-import its `themes/dsm7-embedded.css` for use inside a DSM window.
-
-## Languages
-
-The UI ships in nine of DSM's languages: `en`, `zh-TW`,
-`zh-CN`, `ja`, `ko`, `de`, `fr`, `es` and `it`. DSM's other languages show
-English. The window follows DSM's own language setting (`_S("lang")`).
-
-- **Messages**: `i18n/messages/<locale>.json`, flat `"key": "text"`. Use
-  `ctx.t("greeting.setBy", { text, user })` in the UI; `{name}` is a
-  placeholder, and `ctx.t("files", { count: 3 })` picks `files.one` or
-  `files.other`. Missing keys fall back to English, then to the key itself.
-  `build` embeds the catalogs in the DSM window script, so there is no
-  extra request.
-- **Errors**: the backend returns a `code`; the UI shows
-  `error.<code>` from the catalogs and uses the backend's English text only for
-  codes it has no message for. Add `error.<code>` for every code you return.
-- **Glossary**: `i18n/glossary.json` records DSM's own words in all nine
-  languages, each with its source (`section/key` in DSM 7.4's
-  `/usr/syno/synoman/webman/texts/<lang>/strings`). A term's `keys` lists the
-  messages that must contain it; that is how "Save" uses DSM's own word in
-  every language, the same as the rest of DSM. Product names in `untranslated`
-  stay in English everywhere.
-- **Package Center text**: `i18n.info` in `dsm-package.yaml` writes INFO
-  `displayname_<lang>` / `description_<lang>` (for example `description_cht`).
-
-`synopkgland check` and `build` refuse a language file with missing or
-extra keys, a translation that drops a `{placeholder}`, an unsupported
-language, or a listed message that drifts from the glossary.
-
-To add a message: add the key to `en.json` and to the other eight files. To
-use a DSM term, copy its `text` from the glossary and add your key to the
-term's `keys`. A Vue or React UI can keep its own i18n library; `ctx.t` and
-`ctx.locale` are there if you want them.
-
-The Vue shell (`--ui vue`) keeps its text in `frontend/src/**/i18n/<locale>.json`,
-one folder per area (status page, sign-in, files, background jobs), in the same
-nine languages. Add new text to all nine files rather than writing it into a
-`.vue` file.
-
-## Package an existing binary
-
-Keep the Go backend and call your tool from a handler (recommended: auth
-stays central), or replace the CGI with your own executable:
-
-```yaml
-arches: [x86_64]
-backend:
-  kind: binary
-  files:
-    x86_64: prebuilt/api-x86_64
-```
-
-The file must be a regular file in the project, a 64-bit Linux ELF for that
-arch, and statically linked (DSM models ship different libc versions). It is
-installed as `ui/cgi/api.cgi` (mode 0755) and runs as the package account.
-It then owns everything `backend/internal/api` does for you: bounded reads,
-POST-only JSON, same-origin checks, authentication before any work, and a
-refusal for unknown methods.
-
-## DSM Application Portal link
-
-`synopkgland add portal` adds `portal: {}` to dsm-package.yaml so
-`https://<nas>/<alias>/` opens this app right after DSM sign-in. The install
-wizard proposes the alias (the package name in lowercase by default); an
-administrator turns it on from the app's portal panel or Control Panel >
-Login Portal > Applications. Ordinary users then see the link; until then
-they see "ask an administrator". DSM owns the setting: the backend's
-`portal.status` only reads it, and nothing in the package may write it. See
-`synopkgland skill show portal`.
-
-A portal needs DSM 7.3.2-86009 or later, so `add portal` raises a lower
-`os_min_ver` and build refuses one below it. DSM 7.1.1 rejects an unsigned
-package that registers a portal (Package Center error 320); 7.3.2 and 7.4
-install it; 7.2 is untested. To keep supporting older DSM, remove `portal:`.
-
-## Data, upgrades, uninstall
-
-The backend stores data in `/var/packages/__PACKAGE__/var` (the package's
-own folder, kept across upgrades). Bump `build` for every SPK you hand out;
-bump `version` for feature releases. There are no lifecycle scripts to write:
-the CGI starts per request, so start/stop do nothing.
-
-### What an upgrade keeps
-
-An upgrade replaces the program files and keeps the data. DSM preserves `var`
-(`@appdata`), `home` (`@apphome`) and `etc` (`@appconf`) across an upgrade and
-removes `tmp` (`@apptemp`) and `target` (`@appstore`). Keep everything you need
-to keep under `var`, `home` or `etc`.
-
-### Schema migrations
-
-`backend/internal/datamigrate` applies ordered, idempotent schema migrations and
-records the result in `<var>/data-version`. `backend/cmd/app` runs `app.Migrate`
-on every start; the recorded version makes that a cheap no-op.
-
-- Versions start at 1 and never change meaning. The template ships one empty
-example in `backend/internal/app/migrations.go`; replace it with your steps.
-- Every step must be idempotent: a crash between `Apply` and the version record,
-or two CGI requests racing on the first start after an upgrade, can run one step
-twice.
-- A step that fails stops the run with the previous version still recorded, and
-the next start resumes from there. The helper never deletes or rewrites data
-itself, so a failed migration leaves your old data in place.
-- `datamigrate.Context.OldPkgVer` is the version being upgraded from:
-`SYNOPKG_OLD_PKGVER` when your environment sets it, otherwise the version the last
-successful run recorded. `NewPkgVer` is the version running now.
-
-Uninstalling keeps your data: DSM leaves `@appdata` and `@apphome` on the volume,
-and reinstalling the same package ID picks them up again. The install wizard is a
-dynamic `WIZARD_UIFILES/install_uifile.sh` that checks — read-only — whether
-`@appdata/<package>` already exists and, if it does, tells the administrator the
-install reuses the old data and how to start clean.
-
-The generated SPK ships
-an uninstall wizard (English, plus eight other languages) with one box, **Also
-delete the app data listed above** (`pkgwizard_remove_additional`), unchecked by
-default. Ticked, `postuninst` empties `@appdata/<package>`, `@apphome/<package>`
-and `@appconf/<package>` and nothing else: not Shared Folders, the package
-account or other packages. An upgrade never deletes anything. Do not write your own `postuninst`;
-`synopkgland inspect` flags a deleting script that lacks the upgrade guard
-or deletes outside the package's own folders.
-
-## Executor setup and delegation
-
-`init --with delegate` enables persistent jobs and offline file operations.
-`init --with root-ops` adds fixed `root/<name>.sh` operations for administrators.
-Both use one digest-pinned executor, with no SAS dependency. The package CGI and
-background worker run as the package account.
-
-An administrator confirms their DSM password once to create a root boot task
-and disabled control task. Exact task readback and socket status establish
-readiness. Reboot starts the protected executor without a browser session.
-Executor, policy or root-script changes require approval again; UI and package
-version changes do not. DSM 105 blocks setup without automatic retry.
-
-The Vue setup provider wraps `ctx.executor.status()`, `.authorize(password)` and
-`.control('start'|'stop'|'purge')`. Password confirmation goes to DSM; credentials
-are never persisted by the executor. Plain UI uses the window setup panel.
-Users submit downloads, choose a destination using their current DSM session,
-and revoke their own delegations. Offline writes recheck subject, UID, AppPriv,
-operation, scope and expiry, then write as the subject without overwriting.
-
-SPKs include `executor/executor` and `executor/policy.json`. Protected runtime
-and delegations live below `/usr/local/etc/synopkgland/<package>/` with root-only
-permissions. Purge removes these copies; removing DSM tasks remains an admin
-setup/lifecycle operation. Full installed-package lifecycle acceptance requires
-DSM testing.
-
-## Support matrix
-
-| | Status |
-| --- | --- |
-| Build hosts | macOS, Linux (any OS with Go and Node) |
-| Target CPUs | x86_64 and aarch64 DSM models (one SPK each). armv7 (DSM 7.2+ platforms `alpine`, `alpine4k`, `armada38x`, `monaco`) is opt-in: add it to `arches`; it covers the Go CGI (plain or Vue UI), jobs, daemon, root-ops and delegate. armv7 jobs, daemon and executor (root-ops, delegate) are built and checked locally but have not been verified on a NAS |
-| DSM | 7.1 or later declared (`os_min_ver`, change it with `init --min-dsm` or `build --min-dsm`). Installed and tested on DSM 7.4 and 7.3.2 (x86_64). armv7 was installed and tested on DSM 7.1.1 (`alpine4k`, Linux 3.10, where the bridge runs from the package tmp fallback) with administrator, AppPriv and unauthenticated requests; `armada38x` and `monaco` have not been run on a NAS. No x86_64 Linux 3.10 model has been tested. aarch64 SPKs are built the same way but have not been run on a NAS. |
-| Not supported | armv7 platforms only DSM 7.0/7.1 ship (`armada370`, `armada375`, `armadaxp`, `comcerto2k`); DSM 6, running anything as root without an administrator's approval |

package/dist/templates/native-go/backend/THIRD_PARTY_NOTICES.txt

@@ -1,61 +0,0 @@
-Native Go package build dependencies
-
-github.com/godbus/dbus/v5 v5.2.3-0.20260924123156-0ea052abeb82 (BSD-2-Clause)
-Pinned upstream commit: 0ea052abeb820894f944095b3c2dc125cef0df85
-Fix panic in DecodeMessageWithFDs on read error (not yet in a tagged release).
-
-Copyright (c) 2013, Georg Reinke (<guelfey at gmail dot com>), Google
-All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-
-1. Redistributions of source code must retain the above copyright notice,
-this list of conditions and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the above copyright
-notice, this list of conditions and the following disclaimer in the
-documentation and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
-TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-golang.org/x/sys v0.27.0 (BSD-3-Clause)
-
-Copyright 2009 The Go Authors.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are
-met:
-
-   * Redistributions of source code must retain the above copyright
-notice, this list of conditions and the following disclaimer.
-   * Redistributions in binary form must reproduce the above
-copyright notice, this list of conditions and the following disclaimer
-in the documentation and/or other materials provided with the
-distribution.
-   * Neither the name of Google LLC nor the names of its
-contributors may be used to endorse or promote products derived from
-this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/dist/templates/native-go/backend/cmd/app/main.go

@@ -1,95 +0,0 @@
-// Command app is the package backend. DSM runs it as a CGI (ui/cgi/api.cgi in
-// the package) under the package account, once per request.
-//
-//line dsmapp/cmd/app/main.go:1
-package main
-
-import (
-	"fmt"
-	"log"
-	"net/http"
-	"net/http/cgi"
-	"os"
-
-	"dsmapp/internal/api"
-	"dsmapp/internal/app"
-	"dsmapp/internal/dsm"
-	"dsmapp/internal/filestation"
-	standaloneidentity "dsmapp/internal/identity"
-)
-
-// Set by `synopkgland build-spk` through -ldflags -X; never read from a request.
-var (
-	delegateScope            = ""
-	delegateOperationsJSON   = ""
-	delegateDestinationsJSON = ""
-	delegateLifetime         = ""
-	executorDigest           = ""
-	policyDigest             = ""
-	packageID                = "dev"
-	version                  = "0.0.0"
-	// "session" when the project opted into the interactive File Station adapter.
-	fileStation = ""
-	// "standalone" enables the SDK identity adapter; the runtime owns authentication.
-	identity = ""
-	// dsm-package.yaml entry: "admin-only" or "app-privilege"; empty keeps the route policy alone.
-	entry = ""
-	// "on" when dsm-package.yaml declares portal: serves portal.status.
-	portal = ""
-)
-
-func main() {
-	log.SetFlags(0)
-	log.SetPrefix(packageID + ": ")
-	if os.Getenv("GATEWAY_INTERFACE") == "" {
-		fmt.Fprintf(os.Stderr, "%s %s: this program runs as the package's DSM CGI; open the app from the DSM main menu.\n", packageID, version)
-		os.Exit(2)
-	}
-	cfg := app.Config{
-		DelegateScope:            delegateScope,
-		DelegateOperationsJSON:   delegateOperationsJSON,
-		DelegateDestinationsJSON: delegateDestinationsJSON,
-		DelegateLifetime:         delegateLifetime,
-		ExecutorDigest:           executorDigest, PolicyDigest: policyDigest,
-		PackageID: packageID,
-		Version:   version,
-		DataDir:   "/var/packages/" + packageID + "/var",
-		Portal:    portal == "on",
-	}
-	if _, err := app.ParseDelegateConfig(cfg); err != nil {
-		log.Fatal(err)
-	}
-	if app.SessionFilesEnabled(fileStation) {
-		cfg.SessionFiles = filestation.Local(cfg.DataDir)
-	}
-	// Kernels without memfd_create stage DSM's bridges in the package's own temp.
-	dsm.SetBridgeFallbackDir("/var/packages/" + packageID + "/tmp")
-	var auth api.Authenticator = dsm.NewAuthenticator()
-	var standalone *standaloneidentity.Service
-	if identity == "standalone" {
-		var err error
-		standalone, err = app.StandaloneIdentity(cfg, os.Getenv("SCRIPT_NAME"))
-		if err != nil {
-			log.Fatal("identity configuration unavailable")
-		}
-		auth = standalone
-	}
-	auth, err := dsm.NewEntryGate(auth, entry, packageID, cfg.DataDir)
-	if err != nil {
-		log.Fatal(err)
-	}
-	srv, err := api.NewServer(auth, app.Routes(cfg)...)
-	if err != nil {
-		log.Fatal(err)
-	}
-	if err := app.Migrate(cfg); err != nil {
-		log.Fatalf("schema migration failed: %v", err)
-	}
-	var handler http.Handler = srv
-	if standalone != nil {
-		handler = standalone.Wrap(handler)
-	}
-	if err := cgi.Serve(api.WithRequestDeadline(handler)); err != nil {
-		log.Fatal(err)
-	}
-}