feat(docs): update docs for "import from knative service" (#49)

Author: gorillamoe

README.md

@@ -209,7 +209,7 @@ Kuba provides several commands to help you manage your configuration:
 - `completion`: Generates shell completion scripts for Kuba
 - `config`: Manages global Kuba configuration options such as:
   - `cache`: Enable or disable local caching of secrets
-- `convert`: Converts existing **dotenv** (`.env*`) files to `kuba.yaml` format
+- `convert`: Converts existing configuration sources (e.g. **dotenv** (`.env*`), **Knative Service** manifests) to `kuba.yaml` format
 - `help`: Displays help information for Kuba and its commands
 - `init`: Initializes a new `kuba.yaml` configuration file in the current directory
 - `run`: Runs an application with environment variables fetched from secrets
@@ -567,6 +567,30 @@ kuba convert --infile .env
 kuba convert --infile .env.staging --outfile my-kuba.yaml --env staging
 ```
 
+### Converting Knative Service (`ksvc`) manifests
+
+If you already have a Knative Service (for example a Cloud Run service) with all
+your environment variables defined, you can generate a `kuba.yaml` from that
+manifest:
+
+```sh
+# Convert a Knative Service manifest to kuba.yaml for the production environment
+kuba convert --from ksvc --infile service.yaml --env production
+```
+
+Kuba will:
+
+- Read the container `env` section of the Service template.
+- Convert hard-coded `value` entries into `value` mappings in `kuba.yaml`.
+- Convert `valueFrom.secretKeyRef` entries into `secret-key` mappings, using the
+  Kubernetes Secret name as the secret identifier.
+
+For Knative Services running on GCP (Cloud Run), the generated environment will
+default to:
+
+- `provider: gcp`
+- `project`: the Service `metadata.namespace` (typically the GCP project number)
+
 ### Show effective environment variables
 
 You can use the `show` subcommand to display the

web/src/routes/configuration/+page.svelte

@@ -91,6 +91,33 @@
 						</p>
 					</div>
 				</div>
+
+				<div class="divider">OR</div>
+
+				<div class="card bg-base-200 mb-6">
+					<div class="card-body">
+						<h3 class="card-title">
+							Import from Knative Service (<code>ksvc</code>)
+						</h3>
+						<p class="mb-4">
+							If you're running on Cloud Run / Knative, you can generate a <code>kuba.yaml</code>
+							from an existing Knative Service manifest. Kuba will read the container
+							<code>env</code> entries, convert hard-coded values to <code>value</code> mappings and
+							<code>valueFrom.secretKeyRef</code> entries to <code>secret-key</code> mappings.
+						</p>
+						<pre><code
+								class="language-bash"
+								data-toolbar-order="copy-to-clipboard"
+								data-prismjs-copy="📋"
+								>kuba convert --from ksvc --infile service.yaml --env production</code
+							></pre>
+						<p class="mt-4">
+							For Knative Services running on GCP, the environment will default to provider
+							<code>gcp</code> and use the Service's <code>metadata.namespace</code> as the
+							<code>project</code> (which is typically the GCP project number for Cloud Run).
+						</p>
+					</div>
+				</div>
 			</section>
 
 			<section>