fcloud-sdk 0.3.1__tar.gz → 0.4.0__tar.gz

fcloud_sdk-0.4.0/PKG-INFO

@@ -0,0 +1,13 @@
+Metadata-Version: 2.4
+Name: fcloud-sdk
+Version: 0.4.0
+Summary: Renamed to `supercomputer`; this package only depends on it
+License-Expression: Apache-2.0
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Requires-Dist: supercomputer>=0.4.0
+
+# fcloud-sdk
+
+Renamed to [`supercomputer`](https://pypi.org/project/supercomputer/). `pip install supercomputer`.
+`import fcloud` and the `fcloud` CLI keep working as aliases.

fcloud_sdk-0.4.0/README.md

@@ -0,0 +1,4 @@
+# fcloud-sdk
+
+Renamed to [`supercomputer`](https://pypi.org/project/supercomputer/). `pip install supercomputer`.
+`import fcloud` and the `fcloud` CLI keep working as aliases.

fcloud_sdk-0.4.0/fcloud_sdk.egg-info/PKG-INFO

@@ -0,0 +1,13 @@
+Metadata-Version: 2.4
+Name: fcloud-sdk
+Version: 0.4.0
+Summary: Renamed to `supercomputer`; this package only depends on it
+License-Expression: Apache-2.0
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Requires-Dist: supercomputer>=0.4.0
+
+# fcloud-sdk
+
+Renamed to [`supercomputer`](https://pypi.org/project/supercomputer/). `pip install supercomputer`.
+`import fcloud` and the `fcloud` CLI keep working as aliases.

fcloud_sdk-0.4.0/fcloud_sdk.egg-info/SOURCES.txt

@@ -0,0 +1,7 @@
+README.md
+pyproject.toml
+fcloud_sdk.egg-info/PKG-INFO
+fcloud_sdk.egg-info/SOURCES.txt
+fcloud_sdk.egg-info/dependency_links.txt
+fcloud_sdk.egg-info/requires.txt
+fcloud_sdk.egg-info/top_level.txt

fcloud_sdk-0.4.0/fcloud_sdk.egg-info/requires.txt

@@ -0,0 +1 @@
+supercomputer>=0.4.0

fcloud_sdk-0.4.0/fcloud_sdk.egg-info/top_level.txt

@@ -0,0 +1 @@
+

fcloud_sdk-0.4.0/pyproject.toml

@@ -0,0 +1,17 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+# `pip install fcloud-sdk` keeps working: this ships no code and depends on
+# the renamed package. Publish once per rename, then leave alone.
+[project]
+name = "fcloud-sdk"
+version = "0.4.0"
+description = "Renamed to `supercomputer`; this package only depends on it"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.9"
+dependencies = ["supercomputer>=0.4.0"]
+
+[tool.setuptools]
+packages = []

fcloud_sdk-0.3.1/CHANGELOG.md

@@ -1,321 +0,0 @@
-# Changelog
-
-All notable changes to the `fcloud` Python SDK and CLI are recorded here.
-The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
-versions follow [Semantic Versioning](https://semver.org/).
-
-## [Unreleased]
-
-## [0.3.1] - 2026-09-22
-
-### Fixed
-- `fcloud credits buy` no longer turns auto-refill on by default. It used to
-  consent on behalf of anyone who had never consented before, so buying less
-  than the auto-refill threshold enrolled the account and then charged the
-  saved card for the full top-up seconds later — `buy 10` against the default
-  $25 threshold cost $110. Consent is now opt-in via `--autorefill`, and
-  `--autorefill` also turns the setting back on for an account that had it
-  off, which consent alone cannot do. `--no-autorefill` is still accepted and
-  is now the default; passing both is an error.
-- Before a purchase that will trigger a top-up, the CLI now says so and names
-  the amount. What triggers one is the balance a purchase *leaves behind*,
-  not its size, and the refill is sized to clear the threshold — so $10
-  against a $200 threshold charges the card a further $195, not the $50 the
-  setting says. Both numbers are worked out and printed before anything is
-  charged, including under `--yes`, and including for an account that was
-  already armed.
-- `fcloud credits` no longer claims auto-refill "turns on with your first
-  purchase". It turns on with a purchase made with `--autorefill`, and the
-  status line now says so and names that command.
-- `fcloud credits buy` no longer sends buyers to a dead address after paying.
-  The return URL was built from a domain baked in at release time, which
-  outlived its DNS record: the charge succeeded and the browser landed on a
-  404. The CLI now names no return address and the dispatcher supplies one
-  from its own allowlist, which redeploys with the web app instead of going
-  stale in a published wheel. Setting `FCLOUD_WEB_URL` returns you to
-  `/dashboard`, the page that reads the result, rather than to
-  `/dashboard/billing`, which ignores it.
-
-### Changed
-- `resolve_web_url()` returns `None` when no web URL is configured, and
-  `DEFAULT_WEB_URL` is gone. `Client.start_credit_checkout()` takes
-  `success_url` and `cancel_url` as optional and omits them from the request
-  when unset. Set `FCLOUD_WEB_URL` only to override where a buyer is returned
-  to. **Needs a dispatcher carrying the matching server change**; against an
-  older one, set `FCLOUD_WEB_URL` or buy from the dashboard.
-
-### Added
-- `fcloud.billing_types.predicted_topup_micros()` — what auto-refill would
-  charge once a given purchase has posted. Mirrors the dispatcher's own
-  `topUpAmount` and daily-cap clamp so a confirmation can name the second
-  charge before the card is saved.
-
-## [0.3.0] - 2026-09-16
-
-### Fixed
-- `exec` no longer returns empty output for a command whose last write lands
-  at process exit. The host mirrors a process's durable log on a background
-  goroutine, so a read issued the instant the process reports "exited" can
-  beat that write and come back empty; the client was answering with that
-  empty read even though it had already drained the output off the live
-  stream. It now keeps whichever of the two saw more bytes. The symptom was
-  `stdout: ""` alongside `returncode: 0` — most often for a block-buffered
-  program, which flushes everything during interpreter teardown
-  microseconds before it dies. A training run's final `print(metrics)` is
-  exactly that shape.
-
-### Added
-- `fcloud map --no-bake` opts a sweep out of canary auto-bake. By default,
-  packages the canary pip-installs are baked into the sweep's image before
-  the fan-out; the canary pass line now names them and points at
-  `image.pip` in `fcloud.json` as the permanent home.
-- `fcloud credits`: the prepaid wallet from the terminal. `fcloud credits`
-  shows the posted balance, what is available after unbilled usage,
-  auto-refill state and the saved card; `fcloud credits buy <usd>` opens a
-  hosted checkout and waits for the purchase to post; `fcloud credits
-  autorefill on|off|set` changes the top-up rule (turning it off warns that
-  work stops at $0 and needs a confirmation); `fcloud credits statement`
-  lists ledger rows with a running balance.
-- `InsufficientCreditError` (HTTP 402, `code: insufficient_credit`) — raised
-  when the prepaid balance is exhausted, and mapped to **exit code 4** in
-  the CLI with the top-up command named. It is a sibling of `FcloudError`,
-  not of `PaymentOverdueError`: nothing is owed, so the remedy is to add
-  credit, not to settle a bill. Code that catches `PaymentOverdueError`
-  alone will not catch it.
-- `Client.credit_balance()`, `credit_ledger()`, `set_autorefill()` and
-  `start_credit_checkout()`, with typed payloads in `fcloud.billing_types`.
-- A low-balance warning before `exec`/`run`/`shell`/`create`/`job run`/`map`
-  provision anything, shown once per process and only when nothing will top
-  the account up. Best-effort: a failed billing read never blocks a run.
-
-### Changed
-- An out-of-credit refusal is no longer reported as a missed payment. Both
-  error paths now branch on the dispatcher's `code` before falling back on
-  the bare 402 status, so `payment_overdue`, `insufficient_credit` and an
-  older dispatcher's codeless 402 are told apart.
-- A session closed for want of credit says so ("stopped: out of credits")
-  and exits 4, instead of exiting 75 as if it were briefly unreachable.
-- `fcloud sweep` offers the fast lane only for waits more capacity can fix.
-  Tasks blocked on billing get a top-up hint — boosting past that block
-  buys nothing.
-- Python 3.9 is now supported (`requires-python >= 3.9`), and 3.14 is
-  tested. The README has a support grid; CI runs the suite on 3.9 through
-  3.14. The installer script falls back to `uv` instead of `pipx`/`pip`
-  when the system Python is older than 3.9.
-- The CLI no longer prints urllib3's LibreSSL warning on macOS's bundled
-  Python.
-
-## [0.2.1] - 2026-09-14
-
-### Added
-- `fcloud login`: sign in through the browser (device authorization). Shows a
-  short code, opens the approval page, and saves a key minted for this
-  machine (named `cli:<hostname>`); then installs the fcloud skill for the
-  coding agents present on the machine (`--agents auto`, the default; also
-  `all`, a list, or `none`). `--no-browser` prints the URL and code instead
-  of opening a browser. A fresh install's first command starts the same
-  login, and `fcloud setup` with no key delegates to it.
-- Spend visibility: `fcloud sessions` shows `$/HR` (the rate billed on the
-  session's open usage interval while a host is held, 0 when cold), `SPENT`
-  (compute charged so far) and `AGE` (time on its current host) per row plus
-  a "Spending now" footer; `--json` rows carry `usd_per_hour`, `spent_usd`
-  and `host_age_seconds` (SDK: `Client.session_cost`). New `fcloud usage [--since DUR|TS] [--until TS]`
-  reports what the account was charged over a window (default 30 days) by
-  resource and session (SDK: `Client.billing_usage`).
-
-### Changed
-- `fcloud job ls` shows each job's COMMAND and EXIT code (from its process
-  index; `--json` rows carry `command` and `exit_code`), so rows are
-  tellable apart and failures visible without opening each job.
-
-### Fixed
-- `fcloud logs <sid> <pid>` with a pid the dispatcher has no record of now
-  exits 1 (`process_not_found`) like `wait` and `kill`, instead of printing
-  an empty stream with exit 0 (and `status: ""` in `--json`) that a poller
-  read as a finished, silent process. A just-spawned pid gets a few seconds
-  to reach the durable index before it is called unknown.
-- `fcloud wait` with a `--timeout` shorter than the unknown-pid grace window
-  exits 1 for an unknown pid, not 75 (retry), so scripted callers stop
-  retrying a typo forever.
-- Cold starts of `run`/`exec`/`job run` no longer dump every host status
-  frame (`⟵ session_status: building (phase_change) setup_timing ...`);
-  the fresh-allocation and reconnect paths now use the same quiet printer
-  as warm attaches.
-- `fcloud sweep harvest` no longer pulls the session's virtual `_logs/`
-  directory (`_logs/processes.json`) for a results glob like `*.json`; name
-  `_logs/` in the glob to fetch logs.
-- `fcloud sessions` sizes the HOST and SKU columns to the data (27-char AWS
-  host ids overflowed the fixed width on every row).
-- `fcloud volume list` shows each volume's last update time.
-- SKILL.md documents `fcloud sessions --limit N`.
-
-## [0.2.0] - 2026-09-08
-
-### Added
-- Per-session checkpoint/restore opt-out: `--no-checkpoint` on
-  `create`/`exec`/`run`/`shell` (SDK: `checkpoint=False` on
-  `Project.session`/`cold_session`, `Client.create_session`/
-  `create_cold_session`). A preempted opt-out session is rebuilt cold on any
-  available host (`/workspace` kept, running processes lost) instead of being
-  checkpointed and restored pinned to the region its checkpoint lives in.
-  Defaults resolve `--checkpoint`/`--no-checkpoint` → `FCLOUD_CHECKPOINT` →
-  `fcloud.json` `"checkpoint"` → the new `fcloud config set checkpoint on|off`
-  user default (`~/.fcloud/config.json`) → server default (on).
-  `SessionInfo.checkpoint` and `fcloud sessions --json` expose the policy; the
-  create fails loudly against a dispatcher too old to honour the opt-out.
-- `--no-resume` on `exec`/`run`/`shell`: refuse to wake a cold (stopped)
-  session instead of transparently re-provisioning its hardware. The refusal
-  exits 1 with a typed `session_cold` error naming the session and the SKU a
-  resume would have provisioned. SDK: `Client.attach_session(...,
-  resume=False)` raises the new `fcloud.SessionColdError`.
-- Pipelines: `fcloud map --after SWEEP[,SWEEP]` (SDK: `client.map(...,
-  after=handle_or_name, after_strict=…)`) holds a sweep in the new
-  `waiting` state until the named sweeps finish, then launches it — the
-  barrier is durable server-side, so a generate → train → eval chain
-  submits up front and the client can disconnect. An upstream failure
-  fails the downstream sweep (`upstream_failed:<name>`; re-arm with
-  `fcloud sweep retry <name> --all`); a partially-succeeded upstream
-  counts as finished unless `--after-strict`.
-- `--volume NAME[:MOUNT][:ro]` (also fcloud.json `"read_only": true` or
-  the `name:/mount:ro` string form) attaches a volume read-only: the
-  session sees it, but its writes are discarded at close (no commit).
-- `fcloud autoresearch init`: scaffolds a karpathy/autoresearch-style keep/discard
-  research loop (agent setup guide + `program.md` template) that runs experiments
-  on a persistent fcloud session.
-  The loop uploads `results.tsv` to the session each experiment; the dashboard's
-  session page then shows an Autoresearch tab (metric chart + results table).
-- Skip-the-line boost: `fcloud sweep boost <name>` / pressing `s` in
-  `fcloud sweep status --watch` (offered while blocked on capacity) moves a
-  sweep to the fast claim lane; queued tasks re-lane immediately
-  (`SweepHandle.boost()` in the SDK). Freed machines alternate fast/free.
-- `fcloud sweep status` explains WHY a sweep is waiting: a `why:` line under
-  `blocked on capacity` names the line (`3 session(s) ahead in the gpu_1x_l4
-  queue (1 fast-lane)`) and/or the platform (`a new machine is being
-  provisioned`, `no capacity ... (stockout)`, `cloud quota exhausted`, ...),
-  from the new `blocked.sku/queued_reason/queued_ahead/fast_ahead` status
-  fields; a `state: waiting` (pipeline) sweep names the upstream sweeps it
-  holds for. Older dispatchers omit the fields and status reads as before.
-- Async sweep scheduling: `fcloud map --not-before WHEN` (park until), `--by WHEN`
-  (deadline; opportunistic idle-fill until `deadline - --runtime - pad`, then
-  normal launch) and `--runtime DUR` (per-task estimate, default 1h).
-  `fcloud sweep status` shows the window phase; a missed deadline marks the
-  sweep `deadline_missed` (webhook `job.deadline_missed`) but never cancels it.
-- First-run login prompt: with no API key configured, the CLI offers to open
-  the dashboard login and store the key instead of failing with a bare error.
-- CLI errors carry typed error codes and the request id; the client never
-  provisions hardware for a request the server would reject.
-
-### Changed
-- Resuming a cold session now always prints one stderr line (`session <sid>
-  is cold — resuming (provisions <sku>); pass --no-resume to refuse`), even
-  when stderr is not a TTY or `FCLOUD_QUIET` is set — waking billed hardware
-  is a spend event, and non-TTY runs used to do it silently.
-- Failed map task attempts now retry with a growing delay (45s × attempt,
-  capped at 10m) instead of relaunching immediately; preemption requeues
-  remain immediate and still don't consume the retry budget.
-
-### Fixed
-- `fcloud map --volume name:/path` sent the custom mount path under a key
-  the server ignores, silently mounting the volume at its default path.
-  Custom mount paths now apply to sweep task sessions.
-
-## [0.1.3] - 2026-08-27
-
-### Changed
-- `fcloud setup` installs the agent skill for all agents by default (Enter or
-  non-interactive stdin = `all`); `--agents none` opts out.
-
-## [0.1.2] - 2026-08-27
-
-### Changed
-- README wording.
-
-## [0.1.1] - 2026-08-27
-
-### Changed
-- README: sign up on the website and paste your API key; the editable
-  checkout install instructions are gone.
-
-## [0.1.0] - 2026-08-27
-
-### Changed
-- Renamed: the package is `fcloud-sdk`, the import is `fcloud`, the CLI is
-  `fcloud`, env vars are `FCLOUD_*`, config lives in `~/.fcloud`, project
-  files are `fcloud.json`, new keys are `fcloud_sk_…`, and the client sends
-  `X-Fcloud-Client*` headers. Everything old keeps working: `import foom`,
-  the `foom` command, `FOOM_*`, `~/.foom`, `foom.json`, `foom_sk_` keys and
-  `foom.FoomError`. Map tasks now receive `FCLOUD_TASK_ID` /
-  `FCLOUD_WORLD_SIZE` / `FCLOUD_JOB` (the `FOOM_*` names are gone).
-
-### Added
-- `foom sweep harvest <name> <remote-glob> <local-dir>` — download every
-  task's matching outputs in one command. Sessions are resolved from the
-  sweep and local paths are task-keyed (`<local-dir>/task-<index>/<path>`,
-  or `--flat`), replacing the per-sweep script that parsed status JSON for
-  session ids and ran N `foom download` calls. `--all-states` includes
-  failed and canceled tasks.
-- `foom sweep status --watch [--interval S]` — the human live view,
-  repainted in place until the sweep is terminal. Appends instead of
-  repainting when stdout is not a terminal.
-- `foom stop --wait [--timeout SECONDS]` — block until the workspace
-  manifest is durable, instead of polling `foom sessions` for `state=cold`.
-  `foom map --from <sid>` needs that manifest; the default timeout is 300s
-  and the command exits 1 if the wait expires (the stop itself stands).
-- The `foom sweep status --json` document is now a documented, versioned
-  contract (`schema_version: 1`) — see `docs/sweep-status-schema.md`.
-  Additive changes keep the version; a removal or rename bumps it.
-- Every request now carries `X-Foom-Client` / `X-Foom-Client-Version`, and a
-  client below the deployment's supported floor is rejected with HTTP 426 and
-  the new `foom.ClientTooOldError`, which names the upgrade command. This
-  replaces the previous failure mode for a stale client, an S3
-  `SignatureDoesNotMatch` on every >5 MiB upload that read as a credential
-  problem.
-
-### Changed
-- `foom upload` now names the files that take the pre-signed cloud-storage
-  path (>5 MiB) rather than only the total, and names them again in the error
-  when that path fails — so a broken large-file upload is attributable to a
-  file, not to the command. `Session.upload()` returns them as `s3_files`
-  alongside `inline_files` and `s3_threshold_bytes`.
-
-## [0.1.0] — first public release
-
-### Added
-- `foom` CLI: sessions, exec/run/shell/ssh/tunnel, background processes
-  (spawn/wait/logs/kill), file transfer (upload/download/ls/mount), volumes,
-  run-to-completion jobs, and `foom map` sweeps.
-- Python SDK: `Client`, `Project`, `Session`, `Job`, `SweepHandle`, `Image`.
-- `foom setup` installs the agent skill (`SKILL.md`) for Cursor, Claude Code
-  and Codex.
-- `foom --version` and `foom.__version__`.
-- Directory uploads skip hidden entries, dependency/cache directories and
-  symlinked files by default; `--include-hidden` / `--follow-symlinks` (CLI)
-  and `include_hidden=` / `follow_symlinks=` (SDK) opt back in.
-- `FOOM_TELEMETRY=0` disables the best-effort CLI crash report.
-
-### Removed
-Relative to the pre-release internal SDK (nothing here was ever on PyPI):
-- Public names `MigrationInfo`, `MigrationStatus`, `SyncProgress`, the
-  `FcloudError` and `JobHandle` aliases (`FoomError` / `SweepHandle` remain),
-  and the `Session.migrate()` / `Client.watch()` / `Client.list_session_files()`
-  / `Client.download_file()` helpers — the operator-initiated migration
-  surface is not part of the public client.
-- `Image.add_local_file()`, `Image.add_local_dir()`, `Image.copy()`,
-  `Image.workdir()` — use `Session.upload()` / `foom upload` for local files
-  and the `workdir=` argument on exec.
-- Legacy `~/.fcloud/token`, `~/.fcloud/url` and `fcloud.json` lookups
-  (`~/.foom/*` and `foom.json` are the supported forms). `FCLOUD_API_KEY` /
-  `FCLOUD_URL` are still accepted as aliases of `FOOM_API_KEY` / `FOOM_URL`.
-- Internal modules `foom.upload`, `foom.stream`, `foom.jobs`, `foom.client_ext`
-  and the `s3_uploader` / `websockets_transport` providers, with the
-  `websockets` dependency they pulled in.
-- `DirectClient.run_streaming()` (no callers). `DirectClient.execute()` is
-  kept — internal harnesses use it.
-
-### Security
-- Only `FOOM_*` keys from a project `.env` are imported into the process
-  environment; other keys stay reachable by name via `--secret KEY`.
-- A plaintext (`ws://`) host address is refused when the API was reached over
-  `https://`; a plaintext API URL to a non-local host warns.
-- `foom ssh` quotes its ProxyCommand and validates the session id before using
-  it in filesystem paths.

fcloud_sdk-0.3.1/CONTRIBUTING.md

@@ -1,37 +0,0 @@
-# Contributing
-
-Thanks for your interest in `fcloud`.
-
-## Development setup
-
-```bash
-cd packages/fcloud-sdk
-python3 -m venv .venv && source .venv/bin/activate
-pip install -e ".[dev]"
-```
-
-## Before you open a pull request
-
-```bash
-ruff check src tests      # lint (rule set in pyproject.toml)
-mypy                      # type-check src/fcloud (config in pyproject.toml)
-pytest                    # ~640 hermetic tests, no network or credentials needed
-```
-
-- Keep changes focused; one topic per PR.
-- New behaviour comes with a test — the tests are the spec.
-- Comments explain *why*, not *what*. Please don't reference internal ticket
-  numbers, incidents or environments in code comments.
-- Public functions and classes have docstrings.
-- Line length is 100.
-
-## Reporting bugs
-
-Open a GitHub issue with the `fcloud --version` output, the command or code you
-ran, and what you expected. For anything security-related, see
-[SECURITY.md](SECURITY.md) instead.
-
-## License
-
-By contributing you agree that your contributions are licensed under the
-Apache License 2.0 (see [LICENSE](LICENSE)).

fcloud_sdk-0.3.1/LICENSE

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

fcloud_sdk-0.3.1/MANIFEST.in

@@ -1,8 +0,0 @@
-include README.md
-include LICENSE
-include NOTICE
-include CHANGELOG.md
-include CONTRIBUTING.md
-include SKILL.md
-graft tests
-global-exclude __pycache__ *.py[cod] .DS_Store

fcloud_sdk-0.3.1/NOTICE

@@ -1,4 +0,0 @@
-fcloud
-Copyright 2026 fcloud
-
-This product includes software developed for the fcloud compute platform.