fancy-microsoft-outlook 0.1.0__tar.gz

fancy_microsoft_outlook-0.1.0/.gitignore

@@ -0,0 +1,24 @@
+node_modules/
+dist/
+vendor/
+.venv/
+__pycache__/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+
+# Lockfiles are NOT source of a generated repo.
+#
+# The generator cannot emit one -- a lockfile is the result of a network
+# resolve -- and "a provider repo must be generated and re-generatable" is the
+# constraint the whole estate rests on. At a few hundred repos, a committed
+# lockfile each is a few hundred files nothing can regenerate and a few hundred
+# Dependabot surfaces.
+#
+# The trade is real and worth stating: CI resolves fresh on every run, so an
+# upstream release inside the declared range can break a build with no change
+# here. That is early warning rather than a surprise at publish time, and the
+# ranges are deliberately narrow (>=X <2.0, never a caret on a 0.x).
+composer.lock
+package-lock.json

fancy_microsoft_outlook-0.1.0/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog
+
+All notable changes to `@particle-academy/microsoft-outlook-ui`,
+`@particle-academy/microsoft-outlook-js`, `particle-academy/microsoft-outlook-php`
+and `fancy-microsoft-outlook`.
+
+The four packages share one version, because they are generated from one
+`provider/` definition and a version that meant something different in each
+would be a version nobody could reason about.
+
+## [0.1.0] — 2026-09-15
+
+### Added
+
+- **First release.** The calendar half of Outlook, on Microsoft Graph v1.0:
+  actions `event_get`, `event_list`, `subscription_create`,
+  `subscription_renew` and `subscription_delete`; the `calendar_changed`
+  trigger with `delivery: "subscription"` — a Graph subscription capped at
+  10080 minutes, renewed by `subscription_renew` 3600 seconds before expiry,
+  its lease read from `expirationDateTime`. Deliveries are batches, verified
+  by the `clientState` Graph echoes in every item, and the endpoint answers
+  Graph's `validationToken` challenge before anything is delivered.
+- Requires `fancy-connector-core` ≥ 0.8.0 in js and php — the release that
+  carries `LeaseDeclaration`, the shared-token verification scheme and the
+  challenge handshake.

fancy_microsoft_outlook-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Particle Academy
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

fancy_microsoft_outlook-0.1.0/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.5
+Name: fancy-microsoft-outlook
+Version: 0.1.0
+Summary: Microsoft Outlook for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK.
+Project-URL: Homepage, https://github.com/Fancy-Friends/microsoft-outlook
+Project-URL: Issues, https://github.com/Fancy-Friends/microsoft-outlook/issues
+Project-URL: Source, https://github.com/Fancy-Friends/microsoft-outlook
+Author: Particle Academy
+License-Expression: MIT
+License-File: LICENSE
+Keywords: api,calendar,connector,fancy-flow,microsoft_outlook,particle-academy
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+
+# Microsoft Outlook
+
+[![Fancified](art/fancified.svg)](https://particle.academy)
+
+Microsoft Outlook for [fancy-flow][flow] — as **four imported, versioned packages**, one
+per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs
+change.
+
+[flow]: https://github.com/Particle-Academy/fancy-flow
+
+| Runtime | Package | Install |
+|---|---|---|
+| Authoring surface (every host) | `@particle-academy/microsoft-outlook-ui` | `npm install @particle-academy/microsoft-outlook-ui` |
+| Node | `@particle-academy/microsoft-outlook-js` | `npm install @particle-academy/microsoft-outlook-js` |
+| PHP 8.4+ | `particle-academy/microsoft-outlook-php` | `composer require particle-academy/microsoft-outlook-php` |
+| Python 3.11+ | `fancy-microsoft-outlook` | `pip install fancy-microsoft-outlook` |
+
+The `ui` package is the editor surface and is React on every host — a PHP or
+Python project installs it *and* its own runtime package, and never the `js` one.
+
+## What it costs you
+
+One dependency: `@particle-academy/fancy-connector-core` (or
+`particle-academy/fancy-connector-core` on Composer), which the `js` and `php`
+packages pull in themselves. The Python package has **zero** runtime
+dependencies.
+
+**No Microsoft Outlook SDK.** Plain HTTP, deliberately: a vendor SDK is third-party code
+subject to the kit's full approval bar, and one per provider is hundreds of
+dependencies nobody is tracking.
+
+## Setting it up
+
+Everything below is generated from `provider/manifest.json`, so it cannot disagree with what the packages do.
+
+### Credentials
+
+A Microsoft Outlook connection holds 5 values.
+
+**Two kinds of value, and mixing them up matters.** A `provider` credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An `account` credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.
+
+| Field | Scope | Secret | Where it comes from |
+|---|---|---|---|
+| **Application (client) ID** | per installation | not secret | From the Microsoft Entra admin center -> App registrations. ONE value for the whole installation, not per connected account. |
+| **Client secret** | per installation | **secret** | A client secret of the same app registration. One value for the whole installation; Entra expires them, so record the expiry. |
+| **Access token** | per connected account | **secret** | Per connected Microsoft account, and it expires after about ONE HOUR. The host refreshes it with the refresh token. |
+| **Refresh token** | per connected account | **secret** | Per connected Microsoft account; issued only when the consent request includes offline_access. Every refresh answers with a NEW one -- persist it -- while the old one keeps working until it expires. |
+| **Client state** | per connected account | **secret** | A secret the host chooses per connected account and sends as `clientState` on every subscription. Graph echoes it inside every notification, and that echo is the ONLY thing that authenticates a delivery -- Graph does not sign them. At most 128 characters. |
+
+### Authorising
+
+Microsoft Outlook uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.
+
+- **Authorize URL** — https://login.microsoftonline.com/common/oauth2/v2.0/authorize
+- **Token URL** — https://login.microsoftonline.com/common/oauth2/v2.0/token
+- **Scopes** — `Calendars.Read`, `offline_access`
+- **Access token lifetime** — 3600 seconds (1 hours). A host that never refreshes works all afternoon and is broken by morning.
+
+The refresh tokens do **not** rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.
+
+### The estate
+
+Microsoft Outlook has a test estate on the same host, reached with credentials from a SEPARATE test account you register. Selecting sandbox mode uses those credentials.
+
+> Microsoft's test estate is a Microsoft 365 Developer Program sandbox: a separate E5 tenant with its own users, its own calendars and its own OAuth consent, on the SAME host. Eligibility is limited -- Visual Studio Professional or Enterprise subscribers, ISV Success / Microsoft AI Cloud Partner Program members, or Premier/Unified Support customers -- and the tenant expires after 90 days of no development activity. Without one, every call reaches a real mailbox.
+
+## What it can do
+
+### Actions
+
+#### `event_get` — Outlook calendar event
+
+Read one event from the connected account's Outlook calendar.
+
+`GET /v1.0/me/events/{id}` · reads only — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The event's id, as published by a notification's resourceData.id or by event_list. |
+
+#### `event_list` — Outlook calendar events
+
+List events from the connected account's Outlook calendar.
+
+`GET /v1.0/me/events` · reads only — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `top` | no | Events per page. An @odata.nextLink in the response means there are more. |
+| `filter` | no | An OData $filter. Leave blank for everything. |
+| `orderby` | no | An OData $orderby. Leave blank for Graph's default order. |
+| `select` | no | An OData $select, comma separated. Leave blank for Graph's default set. |
+
+#### `subscription_create` — Outlook subscription
+
+Subscribe to change notifications on the connected account's calendar events. The host's subscription machinery calls this; it is not a node most workflows need.
+
+`POST /v1.0/subscriptions` · **unsafe to replay** — a retried durable run does it TWICE
+
+| Input | Required | What it is |
+|---|---|---|
+| `changeType` | no | Which changes raise a notification. Graph accepts a comma-separated combination. |
+| `resource` | yes | The Graph resource to watch, without the base URL. `me/events` is the connected account's calendar events. |
+| `notificationUrl` | yes | The HTTPS URL the host mounts for this trigger. Graph validates it with a validationToken challenge before creating the subscription, then POSTs change notifications to it. |
+| `lifecycleNotificationUrl` | no | Where Graph sends `reauthorizationRequired`, `subscriptionRemoved` and `missed` events. May be the notification URL itself. Optional, but without it a subscription Graph removed is one nobody hears about. |
+| `expirationDateTime` | yes | When the subscription expires, as an ISO 8601 instant in UTC. The host computes now + the trigger's lifetime; Graph caps an event subscription at 10080 minutes (under seven days) and raises anything under 45 minutes to 45. |
+| `clientState` | yes | The connection's clientState. The host fills this from the connection -- never type a value here. Graph echoes it inside every notification, and that echo is how a delivery is verified. At most 128 characters. |
+
+#### `subscription_delete` — Outlook subscription removal
+
+Delete a change-notification subscription. The host's subscription machinery calls this when a trigger is removed.
+
+`DELETE /v1.0/subscriptions/{id}` · idempotent — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The id subscription_create answered with. |
+
+#### `subscription_renew` — Outlook subscription renewal
+
+Extend a change-notification subscription before it expires. The host's subscription machinery calls this when the lease is due.
+
+`PATCH /v1.0/subscriptions/{id}` · idempotent — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The id subscription_create answered with. |
+| `expirationDateTime` | yes | The new expiry, as an ISO 8601 instant in UTC. The host computes now + the trigger's lifetime, capped at 10080 minutes for events. |
+
+### Triggers
+
+#### `calendar_changed` — Outlook calendar change
+
+Start a run when an event is created, updated or deleted on a subscribed Outlook calendar.
+
+A SUBSCRIPTION: Microsoft Outlook delivers to your endpoint only while a subscription it issued is alive, at most 168 hours at a time. Its expiry is read from the `subscription_create` response (`expirationDateTime`); 3600 seconds before it, the host renews it (`subscription_renew`). A lease that lapses is re-listed AND re-subscribed, because notifications during the gap are gone. Every delivery: the token Microsoft Outlook echoes back is compared with the connection's `clientState` before anything runs. Microsoft Outlook sends a `validationToken` challenge before it delivers anything, and the endpoint must echo it as plain text.
+
+**You have to set this up with the provider first:**
+
+The host calls subscription_create with its own URL for this trigger, an expiry of now plus this lifetime, and the connection's clientState, and must answer Graph's validationToken challenge on that URL as plain text within 10 seconds or the subscription is refused. It stores the returned id and expirationDateTime. 3600 seconds before expiry it calls subscription_renew; a 404 there means the subscription is gone and it re-lists (event_list) and creates again, because notifications during the gap are gone. Every notification is a batch: the host compares each item's clientState with the connection's clientState, answers 202, and then processes the items. A `missed` lifecycle event means re-list; `reauthorizationRequired` means renew; `subscriptionRemoved` means create again and re-list.
+
+## Run it before you have credentials
+
+Every operation ships a **faker**, whether or not Microsoft Outlook has a sandbox. Set a
+node's mode to `fake` and it returns the shape Microsoft Outlook actually publishes — the
+same field names, deterministically — so you can wire the downstream nodes before
+touching an account, a key, or a network.
+
+## This repository is generated
+
+`provider/` is the source. Everything under `packages/` is emitted from it and
+**must not be hand-edited** — CI regenerates and diffs on every push, and the
+next protocol sync destroys anything it finds. See [`AGENTS.md`](AGENTS.md).
+
+## Two namespaces, which do not match on purpose
+
+The repo is `github.com/Fancy-Friends/microsoft-outlook`; the packages publish under
+`particle-academy`. Nothing derives one from the other — the names come from
+weaver's `friends.json` and nowhere else.
+
+## Licence
+
+MIT.

fancy_microsoft_outlook-0.1.0/README.md

@@ -0,0 +1,163 @@
+# Microsoft Outlook
+
+[![Fancified](art/fancified.svg)](https://particle.academy)
+
+Microsoft Outlook for [fancy-flow][flow] — as **four imported, versioned packages**, one
+per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs
+change.
+
+[flow]: https://github.com/Particle-Academy/fancy-flow
+
+| Runtime | Package | Install |
+|---|---|---|
+| Authoring surface (every host) | `@particle-academy/microsoft-outlook-ui` | `npm install @particle-academy/microsoft-outlook-ui` |
+| Node | `@particle-academy/microsoft-outlook-js` | `npm install @particle-academy/microsoft-outlook-js` |
+| PHP 8.4+ | `particle-academy/microsoft-outlook-php` | `composer require particle-academy/microsoft-outlook-php` |
+| Python 3.11+ | `fancy-microsoft-outlook` | `pip install fancy-microsoft-outlook` |
+
+The `ui` package is the editor surface and is React on every host — a PHP or
+Python project installs it *and* its own runtime package, and never the `js` one.
+
+## What it costs you
+
+One dependency: `@particle-academy/fancy-connector-core` (or
+`particle-academy/fancy-connector-core` on Composer), which the `js` and `php`
+packages pull in themselves. The Python package has **zero** runtime
+dependencies.
+
+**No Microsoft Outlook SDK.** Plain HTTP, deliberately: a vendor SDK is third-party code
+subject to the kit's full approval bar, and one per provider is hundreds of
+dependencies nobody is tracking.
+
+## Setting it up
+
+Everything below is generated from `provider/manifest.json`, so it cannot disagree with what the packages do.
+
+### Credentials
+
+A Microsoft Outlook connection holds 5 values.
+
+**Two kinds of value, and mixing them up matters.** A `provider` credential is ONE value for the whole installation — an OAuth app's client secret serves every connected account. An `account` credential is one per connected account. A host that stores the second where it stores the first lets one account's credentials reach another's.
+
+| Field | Scope | Secret | Where it comes from |
+|---|---|---|---|
+| **Application (client) ID** | per installation | not secret | From the Microsoft Entra admin center -> App registrations. ONE value for the whole installation, not per connected account. |
+| **Client secret** | per installation | **secret** | A client secret of the same app registration. One value for the whole installation; Entra expires them, so record the expiry. |
+| **Access token** | per connected account | **secret** | Per connected Microsoft account, and it expires after about ONE HOUR. The host refreshes it with the refresh token. |
+| **Refresh token** | per connected account | **secret** | Per connected Microsoft account; issued only when the consent request includes offline_access. Every refresh answers with a NEW one -- persist it -- while the old one keeps working until it expires. |
+| **Client state** | per connected account | **secret** | A secret the host chooses per connected account and sends as `clientState` on every subscription. Graph echoes it inside every notification, and that echo is the ONLY thing that authenticates a delivery -- Graph does not sign them. At most 128 characters. |
+
+### Authorising
+
+Microsoft Outlook uses OAuth2 (authorization_code). The package DECLARES the exchange; the HOST performs it — a consent screen needs a browser, a redirect URI and somewhere to persist the result, and all three belong to the host.
+
+- **Authorize URL** — https://login.microsoftonline.com/common/oauth2/v2.0/authorize
+- **Token URL** — https://login.microsoftonline.com/common/oauth2/v2.0/token
+- **Scopes** — `Calendars.Read`, `offline_access`
+- **Access token lifetime** — 3600 seconds (1 hours). A host that never refreshes works all afternoon and is broken by morning.
+
+The refresh tokens do **not** rotate: the same one is reusable, so a refresh may safely be retried and may run concurrently. Stated rather than assumed, because the opposite — a provider that spends the token and revokes the grant on a replay — looks identical until it happens.
+
+### The estate
+
+Microsoft Outlook has a test estate on the same host, reached with credentials from a SEPARATE test account you register. Selecting sandbox mode uses those credentials.
+
+> Microsoft's test estate is a Microsoft 365 Developer Program sandbox: a separate E5 tenant with its own users, its own calendars and its own OAuth consent, on the SAME host. Eligibility is limited -- Visual Studio Professional or Enterprise subscribers, ISV Success / Microsoft AI Cloud Partner Program members, or Premier/Unified Support customers -- and the tenant expires after 90 days of no development activity. Without one, every call reaches a real mailbox.
+
+## What it can do
+
+### Actions
+
+#### `event_get` — Outlook calendar event
+
+Read one event from the connected account's Outlook calendar.
+
+`GET /v1.0/me/events/{id}` · reads only — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The event's id, as published by a notification's resourceData.id or by event_list. |
+
+#### `event_list` — Outlook calendar events
+
+List events from the connected account's Outlook calendar.
+
+`GET /v1.0/me/events` · reads only — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `top` | no | Events per page. An @odata.nextLink in the response means there are more. |
+| `filter` | no | An OData $filter. Leave blank for everything. |
+| `orderby` | no | An OData $orderby. Leave blank for Graph's default order. |
+| `select` | no | An OData $select, comma separated. Leave blank for Graph's default set. |
+
+#### `subscription_create` — Outlook subscription
+
+Subscribe to change notifications on the connected account's calendar events. The host's subscription machinery calls this; it is not a node most workflows need.
+
+`POST /v1.0/subscriptions` · **unsafe to replay** — a retried durable run does it TWICE
+
+| Input | Required | What it is |
+|---|---|---|
+| `changeType` | no | Which changes raise a notification. Graph accepts a comma-separated combination. |
+| `resource` | yes | The Graph resource to watch, without the base URL. `me/events` is the connected account's calendar events. |
+| `notificationUrl` | yes | The HTTPS URL the host mounts for this trigger. Graph validates it with a validationToken challenge before creating the subscription, then POSTs change notifications to it. |
+| `lifecycleNotificationUrl` | no | Where Graph sends `reauthorizationRequired`, `subscriptionRemoved` and `missed` events. May be the notification URL itself. Optional, but without it a subscription Graph removed is one nobody hears about. |
+| `expirationDateTime` | yes | When the subscription expires, as an ISO 8601 instant in UTC. The host computes now + the trigger's lifetime; Graph caps an event subscription at 10080 minutes (under seven days) and raises anything under 45 minutes to 45. |
+| `clientState` | yes | The connection's clientState. The host fills this from the connection -- never type a value here. Graph echoes it inside every notification, and that echo is how a delivery is verified. At most 128 characters. |
+
+#### `subscription_delete` — Outlook subscription removal
+
+Delete a change-notification subscription. The host's subscription machinery calls this when a trigger is removed.
+
+`DELETE /v1.0/subscriptions/{id}` · idempotent — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The id subscription_create answered with. |
+
+#### `subscription_renew` — Outlook subscription renewal
+
+Extend a change-notification subscription before it expires. The host's subscription machinery calls this when the lease is due.
+
+`PATCH /v1.0/subscriptions/{id}` · idempotent — safe to replay
+
+| Input | Required | What it is |
+|---|---|---|
+| `id` | yes | The id subscription_create answered with. |
+| `expirationDateTime` | yes | The new expiry, as an ISO 8601 instant in UTC. The host computes now + the trigger's lifetime, capped at 10080 minutes for events. |
+
+### Triggers
+
+#### `calendar_changed` — Outlook calendar change
+
+Start a run when an event is created, updated or deleted on a subscribed Outlook calendar.
+
+A SUBSCRIPTION: Microsoft Outlook delivers to your endpoint only while a subscription it issued is alive, at most 168 hours at a time. Its expiry is read from the `subscription_create` response (`expirationDateTime`); 3600 seconds before it, the host renews it (`subscription_renew`). A lease that lapses is re-listed AND re-subscribed, because notifications during the gap are gone. Every delivery: the token Microsoft Outlook echoes back is compared with the connection's `clientState` before anything runs. Microsoft Outlook sends a `validationToken` challenge before it delivers anything, and the endpoint must echo it as plain text.
+
+**You have to set this up with the provider first:**
+
+The host calls subscription_create with its own URL for this trigger, an expiry of now plus this lifetime, and the connection's clientState, and must answer Graph's validationToken challenge on that URL as plain text within 10 seconds or the subscription is refused. It stores the returned id and expirationDateTime. 3600 seconds before expiry it calls subscription_renew; a 404 there means the subscription is gone and it re-lists (event_list) and creates again, because notifications during the gap are gone. Every notification is a batch: the host compares each item's clientState with the connection's clientState, answers 202, and then processes the items. A `missed` lifecycle event means re-list; `reauthorizationRequired` means renew; `subscriptionRemoved` means create again and re-list.
+
+## Run it before you have credentials
+
+Every operation ships a **faker**, whether or not Microsoft Outlook has a sandbox. Set a
+node's mode to `fake` and it returns the shape Microsoft Outlook actually publishes — the
+same field names, deterministically — so you can wire the downstream nodes before
+touching an account, a key, or a network.
+
+## This repository is generated
+
+`provider/` is the source. Everything under `packages/` is emitted from it and
+**must not be hand-edited** — CI regenerates and diffs on every push, and the
+next protocol sync destroys anything it finds. See [`AGENTS.md`](AGENTS.md).
+
+## Two namespaces, which do not match on purpose
+
+The repo is `github.com/Fancy-Friends/microsoft-outlook`; the packages publish under
+`particle-academy`. Nothing derives one from the other — the names come from
+weaver's `friends.json` and nowhere else.
+
+## Licence
+
+MIT.

fancy_microsoft_outlook-0.1.0/art/fancified.svg

@@ -0,0 +1,26 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="128" height="28" role="img" aria-label="Fancified — built with Fancy UI">
+  <title>Fancified · built with Fancy UI</title>
+  <defs>
+    <linearGradient id="fcdBg" x1="0" y1="0" x2="1" y2="1">
+      <stop offset="0" stop-color="#6d28d9"/>
+      <stop offset=".5" stop-color="#9333ea"/>
+      <stop offset="1" stop-color="#d946ef"/>
+    </linearGradient>
+    <linearGradient id="fcdGloss" x1="0" y1="0" x2="0" y2="1">
+      <stop offset="0" stop-color="#ffffff" stop-opacity=".30"/>
+      <stop offset=".55" stop-color="#ffffff" stop-opacity="0"/>
+    </linearGradient>
+    <clipPath id="fcdClip"><rect width="128" height="28" rx="7"/></clipPath>
+  </defs>
+  <g clip-path="url(#fcdClip)">
+    <rect width="128" height="28" fill="url(#fcdBg)"/>
+    <rect width="34" height="28" fill="#3b0764" fill-opacity=".5"/>
+    <rect width="128" height="13" fill="url(#fcdGloss)"/>
+    <g fill="#fff">
+      <path transform="translate(17 14)" d="M0 -7 C.6 -2.2 2.2 -.6 7 0 C2.2 .6 .6 2.2 0 7 C-.6 2.2 -2.2 .6 -7 0 C-2.2 -.6 -.6 -2.2 0 -7 Z"/>
+      <path transform="translate(25.5 7.5) scale(.34)" fill-opacity=".85" d="M0 -7 C.6 -2.2 2.2 -.6 7 0 C2.2 .6 .6 2.2 0 7 C-.6 2.2 -2.2 .6 -7 0 C-2.2 -.6 -.6 -2.2 0 -7 Z"/>
+    </g>
+    <text x="81" y="18.5" fill="#ffffff" text-anchor="middle" font-family="'Segoe UI',Verdana,'DejaVu Sans',sans-serif" font-size="12" font-weight="700" letter-spacing=".3">Fancified</text>
+  </g>
+  <rect x=".5" y=".5" width="127" height="27" rx="6.5" fill="none" stroke="#ffffff" stroke-opacity=".22"/>
+</svg>

fancy_microsoft_outlook-0.1.0/pyproject.toml

@@ -0,0 +1,87 @@
+[build-system]
+requires = ["hatchling>=1.27"]
+build-backend = "hatchling.build"
+
+[project]
+name = "fancy-microsoft-outlook"
+version = "0.1.0"
+description = "Microsoft Outlook for Python — the service descriptor, its faker, its webhook verification, and one function per operation. Plain HTTP; no vendor SDK."
+readme = "README.md"
+# 3.11 matches fancy-flow-py's floor: 3.10 reaches end of life on 2026-10-31,
+# and a floor that dies before the package's second release is not a floor.
+requires-python = ">=3.11"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "Particle Academy" }]
+keywords = ["microsoft_outlook", "calendar", "connector", "api", "fancy-flow", "particle-academy"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Libraries",
+    "Typing :: Typed",
+]
+
+# ZERO runtime dependencies, and that is a design constraint rather than an
+# accident. There is no Python twin of fancy-connector-core to depend on, and a
+# vendor SDK is third-party code subject to the kit's full approval bar — one
+# SDK per provider is hundreds of dependencies nobody is tracking. The HTTP is
+# stdlib `urllib`; the HMAC is stdlib `hmac`.
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/Fancy-Friends/microsoft-outlook"
+Issues = "https://github.com/Fancy-Friends/microsoft-outlook/issues"
+Source = "https://github.com/Fancy-Friends/microsoft-outlook"
+
+[dependency-groups]
+# Not optional. A package with no way to run its tests reports green by doing
+# nothing, which is the one defect that hides itself.
+test = ["pytest>=8.0"]
+lint = ["ruff>=0.16"]
+typecheck = ["mypy>=1.11"]
+dev = [{ include-group = "test" }, { include-group = "lint" }, { include-group = "typecheck" }]
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/fancy_microsoft_outlook"]
+
+[tool.hatch.build.targets.sdist]
+include = ["/src", "/tests", "/art", "/README.md", "/CHANGELOG.md", "/LICENSE"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+# importlib mode pairs with src-layout: the working tree is never on sys.path,
+# so the tests exercise the INSTALLED package. Under the default mode a missing
+# py.typed or an unshipped file passes locally and breaks for every user.
+addopts = "--import-mode=importlib -ra"
+
+[tool.ruff]
+line-length = 100
+src = ["src", "tests"]
+target-version = "py311"
+
+[tool.ruff.lint]
+# `S` — flake8-bandit — is ON, and it is the one addition worth arguing for: this
+# package handles a credential, builds an HMAC, and opens a URL. Security lint
+# belongs on exactly this code.
+#
+# It also makes the two `# noqa: S310` in _runtime.py MEANINGFUL. Without `S`
+# selected, ruff reports them as unused directives (RUF100) and the obvious fix
+# is to delete them — which quietly removes a security annotation because a
+# linter was not looking for it.
+select = ["E", "F", "I", "UP", "B", "SIM", "RUF", "N", "C4", "PT", "S"]
+
+[tool.ruff.lint.per-file-ignores]
+# pytest's whole idiom is bare `assert`. S101 would fail every test file.
+"tests/*" = ["S101"]
+
+[tool.mypy]
+python_version = "3.11"
+packages = ["fancy_microsoft_outlook"]
+mypy_path = "src"
+strict = true
+disallow_any_expr = false
+disallow_any_explicit = false

fancy_microsoft_outlook-0.1.0/src/fancy_microsoft_outlook/__init__.py

@@ -0,0 +1,47 @@
+# GENERATED FILE — do not edit.
+#
+# Emitted from provider/manifest.json by weaver's generator.
+# A hand-edit here is destroyed by the next protocol sync, which is worse than
+# being rejected, because it works until it silently does not. Fix
+# provider/manifest.json (or weaver's template/) and regenerate:
+#
+# npm run provider -- microsoft_outlook
+
+"""Microsoft Outlook for Python.
+
+The service descriptor, its faker, its delivery contract, and one function
+per operation — plain HTTP on the stdlib, no vendor SDK and no runtime
+dependency.
+"""
+
+from __future__ import annotations
+
+from ._fake import FakeValues
+from .actions.event_get import event_get
+from .actions.event_list import event_list
+from .actions.subscription_create import subscription_create
+from .actions.subscription_delete import subscription_delete
+from .actions.subscription_renew import subscription_renew
+from .faker import respond
+from .service import BASE_URLS, CONNECTOR_API_VERSION, REQUIRES, SANDBOX, SERVICE, TITLE, descriptor
+from .triggers import calendar_changed
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "BASE_URLS",
+    "CONNECTOR_API_VERSION",
+    "REQUIRES",
+    "SANDBOX",
+    "SERVICE",
+    "TITLE",
+    "FakeValues",
+    "calendar_changed",
+    "descriptor",
+    "event_get",
+    "event_list",
+    "respond",
+    "subscription_create",
+    "subscription_delete",
+    "subscription_renew",
+]