docs: align README, DEVELOPMENT, k8s, and skill docs with current repo

- README: fix per-function ports (8081/8082), add knative-job-example
  (8083) and python-example (8084), drop stale k8s/Makefile instructions
  in favor of make skaffold-dev, switch package references from
  @constructive-io/knative-job-fn to fn-runtime/fn-app, expand project
  structure
- DEVELOPMENT: bump Node prerequisite to >= 22, add new functions to
  port maps and build-artifacts table, replace manual skaffold/
  job-service edit steps with a pointer to docs/skills/adding-functions
  (those edits are now generated by pnpm generate)
- AGENTS: each function declares its own port in handler.json; 8080 is
  the job service
- k8s/README: rewrite around the actual overlays (local-simple, local,
  ci, dev, staging); make skaffold-dev is the primary local path
- k8s/ARCHITECTURE: retitle for casablanca, fix interweb/k8s paths and
  namespace claims, add a local-simple overlay section, mark the local
  variants in "future improvements" as in place
- docs/skills/adding-functions: add actorId to documented job context

Author: Anmol1696

AGENTS.md

@@ -129,7 +129,7 @@ pnpm build        # Recompile
 
 ## Key Details
 
-- Functions run on `PORT=8080` (Knative default)
+- Each function declares its port in `handler.json` (`simple-email` 8081, `send-email-link` 8082, `knative-job-example` 8083, `python-example` 8084); the job service uses 8080
 - Email functions support dry-run via `SIMPLE_EMAIL_DRY_RUN` / `SEND_EMAIL_LINK_DRY_RUN`
 - `loadFunctionApp()` in job/service resolves modules by name (e.g. `@constructive-io/simple-email-fn`)
 - GraphQL clients require `GRAPHQL_URL` env var and `X-Database-Id` header

DEVELOPMENT.md

@@ -4,7 +4,7 @@ Local development setup for running functions against real infrastructure (Postg
 
 ## Prerequisites
 
-- Node.js >= 18.17.0
+- Node.js >= 22.0.0
 - pnpm >= 10
 - Docker Desktop
 
@@ -60,7 +60,8 @@ After this you should have built artifacts in:
 |---------|--------|
 | `generated/send-email-link/dist/` | Send-email-link function server |
 | `generated/simple-email/dist/` | Simple-email function server |
-| `generated/example/dist/` | Example function server |
+| `generated/example/dist/` | knative-job-example function server |
+| `generated/python-example/dist/` | Python example function server |
 | `job/service/dist/` | Knative job service (worker + scheduler) |
 | `packages/fn-runtime/dist/` | Function runtime library |
 | `packages/fn-app/dist/` | Function app framework |
@@ -113,6 +114,8 @@ This runs `scripts/dev.ts` which spawns local Node processes with env vars point
 | **job-service** | 8080 | `job/service/dist/run.js` |
 | **simple-email** | 8081 | `generated/simple-email/dist/index.js` |
 | **send-email-link** | 8082 | `generated/send-email-link/dist/index.js` |
+| **knative-job-example** | 8083 | `generated/example/dist/index.js` |
+| **python-example** | 8084 | `generated/python-example/...` (python entrypoint) |
 
 To start a single function:
 
@@ -175,6 +178,8 @@ make dev-down          # Stop Docker infrastructure
 | Job Service | 8080 |
 | simple-email | 8081 |
 | send-email-link | 8082 |
+| knative-job-example | 8083 |
+| python-example | 8084 |
 
 ## Architecture
 
@@ -280,6 +285,8 @@ Changes to runtime packages (`packages/fn-runtime`, `packages/fn-app`) or `packa
 |---------|------------|
 | simple-email | 8081 |
 | send-email-link | 8082 |
+| knative-job-example | 8083 |
+| python-example | 8084 |
 | Job Service | 8080 |
 | PostgreSQL | 5432 |
 | Constructive Server | 3002 |
@@ -295,61 +302,15 @@ Changes to runtime packages (`packages/fn-runtime`, `packages/fn-app`) or `packa
 
 ## Adding a New Function
 
-1. **Create the function source:**
-
-   ```bash
-   mkdir functions/my-function
-   ```
-
-   Add `functions/my-function/handler.json`:
-   ```json
-   {
-     "name": "my-function",
-     "version": "1.0.0",
-     "type": "node-graphql",
-     "description": "What this function does",
-     "dependencies": {}
-   }
-   ```
-
-   Add `functions/my-function/handler.ts` with your function logic.
-
-2. **Generate the workspace package:**
-
-   ```bash
-   pnpm generate
-   pnpm install
-   ```
-
-   This creates `generated/my-function/` with the full package, Dockerfile, and k8s manifests (including `k8s/local-deployment.yaml`).
-
-3. **Register in Skaffold** — edit `skaffold.yaml`, add to the `local-simple` profile:
-
-   ```yaml
-   rawYaml:
-     - generated/simple-email/k8s/local-deployment.yaml
-     - generated/send-email-link/k8s/local-deployment.yaml
-     - generated/my-function/k8s/local-deployment.yaml  # <- add this
-   ```
-
-   And add a port-forward entry:
-   ```yaml
-   portForward:
-     - resourceType: service
-       resourceName: my-function
-       namespace: constructive-functions
-       port: 80
-       localPort: 8083  # pick an unused port
-   ```
-
-4. **Register in job-service** — edit `k8s/overlays/local-simple/job-service.yaml`, add to `JOBS_SUPPORTED` and `INTERNAL_GATEWAY_DEVELOPMENT_MAP`.
-
-5. **Test:**
-
-   ```bash
-   make skaffold-dev        # deploy
-   pnpm test:e2e            # run e2e tests
-   ```
+The canonical, end-to-end workflow lives in [docs/skills/adding-functions.md](./docs/skills/adding-functions.md). Quick summary:
+
+1. Create `functions/<name>/handler.json` and `functions/<name>/handler.ts`.
+2. Register the function with the job service in `job/service/src/types.ts` (`FunctionName` union) and `job/service/src/index.ts` (`functionRegistry` entry).
+3. Run `pnpm generate && pnpm install && pnpm build`.
+
+`pnpm generate` automatically updates `skaffold.yaml` (per-function profile + port-forwards), `k8s/overlays/local-simple/job-service.yaml` (`JOBS_SUPPORTED` and `INTERNAL_GATEWAY_DEVELOPMENT_MAP`), and `generated/functions-manifest.json`. No manual edits to those files are needed.
+
+Then test with `make skaffold-dev` and `pnpm test:e2e`. See the skill doc for the unit-test, e2e-test, and CI checklist.
 
 ## E2E Tests
 

README.md

@@ -1,125 +1,109 @@
 # constructive-functions
 
-Functions playground for Constructive — isolated workspace for building, testing, and deploying Knative-style HTTP functions.
+Functions playground for Constructive — a workspace for building, testing, and deploying serverless HTTP functions backed by a Postgres-backed job queue.
+
+Functions are authored in `functions/<name>/` (a `handler.ts` plus a `handler.json` manifest), generated into runnable workspace packages by `pnpm generate`, and dispatched by the job service in `job/service/`. Templates live in `templates/` (`node-graphql` and `python` are supported today).
 
 ## Quick Start
 
 ```bash
-# Install dependencies
-pnpm install
-
-# Build all functions
-pnpm build
+pnpm generate     # generate workspace packages from handler.json manifests
+pnpm install      # install dependencies (including generated packages)
+pnpm build        # build all packages and functions
 
-# Build Docker images locally
-make docker-build
-
-# Build individual function images
-make docker-build-simple-email
+make docker-build                        # build all function Docker images
+make docker-build-simple-email           # build a single function image
 make docker-build-send-email-link
 ```
 
 ## Functions
 
-### `@constructive-io/simple-email-fn`
+| Function | Port | Type | Image |
+|----------|------|------|-------|
+| `simple-email` | 8081 | node-graphql | `ghcr.io/constructive-io/constructive-functions/simple-email:latest` |
+| `send-email-link` | 8082 | node-graphql | `ghcr.io/constructive-io/constructive-functions/send-email-link:latest` |
+| `knative-job-example` | 8083 | node-graphql | `ghcr.io/constructive-io/constructive-functions/knative-job-example:latest` |
+| `python-example` | 8084 | python | `ghcr.io/constructive-io/constructive-functions/python-example:latest` |
 
-Simple email function that sends emails directly from job payload.
+Port `8080` is reserved for the job service.
 
-- **Port**: `8080`
-- **Docker image**: `ghcr.io/constructive-io/constructive-functions/simple-email:latest`
-- **Environment**:
-  - `SIMPLE_EMAIL_DRY_RUN` — If `true`, logs email payload without sending
-  - `MAILGUN_API_KEY`, `MAILGUN_KEY` — Mailgun credentials
-  - `MAILGUN_DOMAIN`, `MAILGUN_FROM`, `MAILGUN_REPLY` — Mailgun email config
+### `simple-email`
 
-### `@constructive-io/send-email-link-fn`
+Sends emails directly from a job payload.
 
-Email link function for invite, password reset, and verification emails.
+- `SIMPLE_EMAIL_DRY_RUN` — if `true`, logs the payload instead of sending
+- `MAILGUN_API_KEY`, `MAILGUN_KEY`, `MAILGUN_DOMAIN`, `MAILGUN_FROM`, `MAILGUN_REPLY` — Mailgun config
 
-- **Port**: `8080`
-- **Docker image**: `ghcr.io/constructive-io/constructive-functions/send-email-link:latest`
-- **Environment**:
-  - `SEND_EMAIL_LINK_DRY_RUN` — If `true`, logs email payload without sending
-  - `DEFAULT_DATABASE_ID` — Default database UUID
-  - `GRAPHQL_URL` — GraphQL API endpoint
-  - `META_GRAPHQL_URL` — Meta GraphQL API endpoint (optional)
-  - `GRAPHQL_AUTH_TOKEN` — Optional Bearer token for GraphQL requests
-  - `LOCAL_APP_PORT` — Local port for dashboard links (e.g., `3000`)
-  - `MAILGUN_*` — Same Mailgun config as `simple-email`
+### `send-email-link`
 
-## Development
+Sends invite, password reset, and verification emails (rendered via MJML).
 
-This repo includes full Kubernetes manifests for deploying functions to any cluster.
+- `SEND_EMAIL_LINK_DRY_RUN` — if `true`, logs the payload instead of sending
+- `DEFAULT_DATABASE_ID` — default database UUID
+- `GRAPHQL_URL`, `META_GRAPHQL_URL` — GraphQL API endpoints
+- `GRAPHQL_AUTH_TOKEN` — optional Bearer token for GraphQL requests
+- `LOCAL_APP_PORT` — local port for dashboard links (e.g. `3000`)
+- `MAILGUN_*` — same Mailgun config as `simple-email`
 
-### Local Kubernetes (kind/minikube)
+### `knative-job-example` / `python-example`
 
-```bash
-cd k8s
+Reference implementations for the `node-graphql` and `python` templates.
 
-# Install Knative Serving + Kourier only (no CNPG)
-make operators-knative-only
+## Development
 
-# Apply local overlay (single Postgres, single MinIO, functions)
-make kustomize-local
+The full local-dev guide lives in [DEVELOPMENT.md](./DEVELOPMENT.md). Two paths:
 
-# Port-forward to local services
-make proxy-server   # GraphQL API -> localhost:8080
-make proxy-explorer # GraphQL explorer UI -> localhost:8081
-make proxy-web      # Dashboard UI -> localhost:3000
-```
+- **Docker Compose + local Node** (fastest iteration) — `make dev` for infrastructure, `make dev-fn` to run functions as local Node processes.
+- **Skaffold on local k8s** (production-like, with hot reload) — `make skaffold-dev` deploys the full stack to the `constructive-functions` namespace and watches handler files.
 
-See `k8s/DEVELOPMENT_LOCAL.md` for detailed local setup.
+For the Knative variant of the k8s setup, see `k8s/DEVELOPMENT_LOCAL.md`.
 
 ### CI/CD
 
-The `CI Test K8s` workflow (`.github/workflows/test-k8s-deployment.yaml`) runs on every PR/push to `main` that touches `k8s/**`. It:
-
-1. Spins up a `kind` cluster
-2. Installs Knative via `make operators-knative-only`
-3. Applies the `k8s/overlays/ci` overlay
-4. Waits for workloads to be ready
+The `CI Test K8s` workflow (`.github/workflows/test-k8s-deployment.yaml`) runs on PRs and pushes to `main` that touch `k8s/`, `tests/e2e/`, or `functions/`. It spins up a `kind` cluster, applies the `k8s/overlays/ci` overlay, and runs the per-function e2e tests.
 
 ## Project Structure
 
 ```
 .
-├── functions/
-│   ├── send-email-link/
-│   │   ├── src/
-│   │   ├── package.json
-│   │   ├── Dockerfile
-│   │   └── tsconfig.json
-│   └── simple-email/
-│       └── (same structure)
+├── functions/             # User-authored handler.ts + handler.json (git tracked)
+├── templates/             # Template definitions (node-graphql, python, shared, k8s)
+├── generated/             # Generated workspace packages (gitignored)
+├── packages/
+│   ├── fn-runtime/        # createFunctionServer, GraphQL clients, FunctionContext
+│   └── fn-app/            # Express app factory with job callbacks
+├── job/
+│   ├── service/           # Orchestrator (loads functions + worker + scheduler)
+│   ├── server/            # Callback receiver
+│   └── worker/            # Job dispatcher
 ├── k8s/
-│   ├── base/
-│   ├── overlays/
-│   ├── scripts/
-│   └── Makefile
-├── types/
-│   └── (custom type definitions for external packages)
+│   ├── base/              # Shared manifests
+│   └── overlays/          # local-simple, local, ci, dev, staging
+├── tests/                 # integration + e2e suites
+├── scripts/               # generate.ts, dev.ts, docker-build.ts
+├── skaffold.yaml
 ├── package.json
-├── pnpm-workspace.yaml
 └── Makefile
 ```
 
 ## Notes
 
-- Functions use `@constructive-io/knative-job-fn` for the Express/Knative HTTP wrapper
-- Email providers use `@constructive-io/postmaster` (Mailgun) and `@launchql/mjml` (styled-email templates via MJML)
-- No `docker-compose` — this repo is Kubernetes-focused for functions deployment
-- Root workspace manages shared linting/formatting configs; each function has its own build config
+- Functions use `@constructive-io/fn-runtime` (runtime + GraphQL clients) and `@constructive-io/fn-app` (Express wrapper).
+- Email providers are wired through `@constructive-io/postmaster` (Mailgun) and `@launchql/mjml` / `@launchql/styled-email` for templating.
+- Both Node (`node-graphql`) and Python (`python`) templates are supported — pick via the `type` field in `handler.json`.
+- The `generated/` directory is entirely gitignored; rerun `pnpm generate` after changing any `handler.json`.
+- Root workspace manages shared linting/formatting; each generated function ships its own build config and Dockerfile.
 
 ## Pushing Images
 
-To push to GitHub Container Registry:
+Images are tagged with the GHCR prefix automatically:
 
 ```bash
 docker push ghcr.io/constructive-io/constructive-functions/simple-email:latest
 docker push ghcr.io/constructive-io/constructive-functions/send-email-link:latest
+docker push ghcr.io/constructive-io/constructive-functions/knative-job-example:latest
+docker push ghcr.io/constructive-io/constructive-functions/python-example:latest
 ```
 
-Images are built with the correct registry prefix via the Makefile:
-- `make docker-build` — Builds all functions with `ghcr.io/constructive-io/constructive-functions/<name>:latest`
-- `make docker-build-simple-email` — Builds `ghcr.io/constructive-io/constructive-functions/simple-email:latest`
-- `make docker-build-send-email-link` — Builds `ghcr.io/constructive-io/constructive-functions/send-email-link:latest`
+- `make docker-build` — builds all function images
+- `make docker-build-<name>` — builds a single function image

docs/skills/adding-functions.md

@@ -59,7 +59,7 @@ const handler: FunctionHandler<MyPayload> = async (params, context) => {
   // context provides: { client, meta, job, log, env }
   //   client — GraphQL client for the database's API
   //   meta — GraphQL client for metadata API
-  //   job — { jobId, workerId, databaseId }
+  //   job — { jobId, workerId, databaseId, actorId }
   //   log — structured logger (info, error, warn, debug)
   //   env — process.env