- CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT5
- CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY1
- CONN-NEXTCLOUD-AGENT15
- Requirementsall slices in all specs21
- Requirements not donenot VERIFIED1
- Specs not donewhole specs only1
Each spec shows its requirement count. Panel J lists every record.
Requirements (21)
Specs (3)
Each bar shows one state against all records of the same kind.
Percentages count current rows. Done means VERIFIED.
| State | Definition |
|---|---|
| SPECIFIED | The requirement is written. No code for it is on the default branch. |
| LANDED | A commit that carries its ID in a Spec trailer is on the default branch. |
| VERIFIED | It is LANDED and a test bound to its ID exists. |
A spec state is the lowest state of its rows. Done means VERIFIED.
Invalid state: 0
| Spec / title | Req. | Landed | Done | Spec state | Code references |
|---|---|---|---|---|---|
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENTCONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged content | 5 | 5/5 | 4 | LANDED | nextcloud_agent/__init__.py:6 implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified ../../nextcloud_agent/__init__.py implementation: file exists; coverage not verified |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITYCONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY — The connector is filed under its fleet name | 1 | 1/1 | 1 | ✓ VERIFIED | nextcloud_agent/__init__.py:6 implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified tests/test_fleet_name.py test: file exists; coverage not verified ../../nextcloud_agent/__init__.py implementation: file exists; coverage not verified |
| CONN-NEXTCLOUD-AGENTCONN-NEXTCLOUD-AGENT — Nextcloud business operations | 15 | 15/15 | 15 | ✓ VERIFIED | nextcloud_agent/api/__init__.py implementation: file exists; coverage not verified nextcloud_agent/api/api_client_base.py implementation: file exists; coverage not verified requirements.md documentation: file exists; coverage not verified spec.md documentation: file exists; coverage not verified tests/test_files_webdav.py test: file exists; coverage not verified ../../nextcloud_agent/api/api_client_files.py implementation: file exists; coverage not verified contracts/storage-backends.md documentation: file exists; coverage not verified nextcloud_agent/auth.py implementation: file exists; coverage not verified |
Landed counts LANDED and VERIFIED requirements. Done counts VERIFIED requirements only.
The spec state comes from the spec status file only.
Packages group specs by repository and declared component. Unassigned means no component was declared. Code links do not prove coverage. Mermaid source.
Knuckles-Team/nextcloud-agent / nextcloud-agent connector (3)
CONN-NEXTCLOUD-AGENT: no plan diagram declared.
CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT: no plan diagram declared.
CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY: no plan diagram declared.
Depends on means a declared prerequisite. Extends and references do not imply prerequisite order. Shared code never creates dependencies. External targets are source declarations, not verified delivery.
Knuckles-Team/nextcloud-agent / nextcloud-agent connector
| Spec | Relationship | Target | Evidence |
|---|---|---|---|
| CONN-NEXTCLOUD-AGENT | No relationships declared; dependencies unknown | ||
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | No relationships declared; dependencies unknown | ||
| CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY | No relationships declared; dependencies unknown | ||
Issues
0 open at capture.
Pull Requests
0 open at capture.
The build reads GitHub one time. This page makes no live API requests.
Each status file gives one spec row. Each requirement gives one more row. A record without a valid state shows INVALID. Expand a Definition to read the canonical requirement and verification text.
All documented records (24 rows)
| ID / source | Kind | Parent | State | Commit / test evidence |
|---|---|---|---|---|
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged content | spec | None | LANDED | No recorded commit/test evidence |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT-R001 Default content Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT / CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Default content.** `pyproject.toml` declares `nextcloud-mcp` as the single `scion_sdk.connector` entry point. The server lists the packaged `skill://` and `ontology://` resources and the packaged prompts with no `content=` argument. Caller chain: `nextcloud-mcp` in `pyproject.toml` runs `scion_sdk.cli:serve`, which builds the server from the `scion_sdk.connector` entry point `nextcloud_agent:connector` (`nextcloud_agent/__init__.py:6`); the SDK `Connector` then lists the packaged skills, ontology and prompts. Shape: `pyproject.toml` entry point `nextcloud-mcp` plus the `connector = Connector(.)` object in `nextcloud_agent/__init__.py`; the packaged `skills/`, `ontology/` and `prompts/` directories of `nextcloud_agent` are reused as is, with no connector-local registration code. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. Proving test (planned): `tests/test_default_content_surfaces.py::test_default_content_surfaces`. | `resources/list` includes `skill://` and `ontology://`; `prompts/list` includes each packaged prompt. | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | LANDED | 310b3be8a4f9 |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT-R002 The ontology rolls up to core Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT / CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**The ontology rolls up to core.** `nextcloud_agent/ontology/nextcloud.ttl` declares the pack classes (shares, versions, trash, office documents, calendars, address books, contact cards, Talk conversations and messages, Deck boards, stacks and cards, notes, activity, notifications, apps), each a `rdfs:subClassOf` of a core class, plus their links, with no `owl:imports`; core classes are referenced, never redeclared. Caller chain: the SDK serves the file as `ontology://nextcloud-mcp/nextcloud.ttl`. Shape: one Turtle file reusing core `:File`, `:Folder`, `:CalendarEvent`, `:PersonalTask`, `:IdentityUser`, `:IdentityGroup` and `:FileShare`. | `tests/test_content_surface.py::test_ontology_rolls_up_to_core_without_imports`: no orphan class, no import. | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | VERIFIED | 0c342adfc0fa tests/test_content_surface.py:45 |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT-R003 Each prompt is an agent definition Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT / CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Each prompt is an agent definition.** Every `nextcloud_agent/prompts/*.json` (operator, asset publisher, office coordinator, project coordinator, workspace admin, file steward) carries `identity.role`, `identity.goal` and an `agent` object (kind operator or business-role with its business role, tools, skills, data locations read and written, approval and never guardrails, outputs), and names only served tools, packaged skills, declared locations and declared roles. Caller chain: the SDK serves each as an MCP prompt; the platform builds agents from them. Shape: one JSON file per prompt under `nextcloud_agent/prompts/` in the existing prompt schema, with the `agent` object of the SDK surface standard (`SCION-CONNECTOR-CONTROL-R916.8`). | `tests/test_content_surface.py::test_prompts_are_agent_definitions_over_real_tools_and_skills`. | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | VERIFIED | 0c342adfc0fa tests/test_content_surface.py:54 |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT-R004 A skill per domain plus the asset-publishing workflow Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT / CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**A skill per domain plus the asset-publishing workflow.** `nextcloud_agent/skills/` holds files, shares, calendar, tasks, contacts, Talk, Deck, notes, office, activity, admin, ingest and `nextcloud-publish-asset` (publish a produced asset to the team folder and share it), each naming only served tools; the ingest skill describes the declared sources in `nextcloud_agent/connector_sources.py`. Caller chain: the SDK serves each as `skill://<name>`. Shape: one `SKILL.md` per skill directory under `nextcloud_agent/skills/`, and `source_meta` entries in `nextcloud_agent/connector_sources.py`. | `tests/test_content_surface.py::test_skills_and_contracts_name_only_served_tools`. | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | VERIFIED | 0c342adfc0fa tests/test_content_surface.py:74 |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT-R005 Surface contracts Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT / CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT — The connector serves its packaged contentCanonical requirement and verification source**Surface contracts.** `nextcloud_agent/connector_contracts.py` declares `CONTRACTS` (the business workflows: publish an asset, schedule a meeting, team announcement, track work, collaborate on a document, onboard a member; and one contract per domain), every served tool in at least one ordered `ToolStep` with params, result fields and refusals; `LINKS` joining every prompt, skill and tool to a task; `LOCATIONS` naming where each record family lives (store and protocol, read tool, route parameter, federation key); and `ROLES` for each business-role prompt. The SDK serves it as `ontology://nextcloud-mcp/contracts.ttl` and checks it (`SCION-CONNECTOR-CONTROL-R916`). Caller chain: `scion_sdk.surface_contracts.load_surface("nextcloud_agent")`. Shape: one module of SDK dataclass values; no connector-local rendering. Depends on: `SCION-CONNECTOR-CONTROL-R916`. | `tests/test_content_surface.py::test_contracts_cover_every_tool_prompt_and_skill`; `tests/test_content_surface.py::test_sdk_surface_check_is_clean_when_available` (the SDK self-check reports no finding). | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-CONTENT | VERIFIED | 0c342adfc0fa tests/test_content_surface.py:101 tests/test_content_surface.py:85 |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY — The connector is filed under its fleet name | spec | None | VERIFIED | No recorded commit/test evidence |
| CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY-R001 Fleet name Definition — CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY / CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY — The connector is filed under its fleet nameCanonical requirement and verification source**Fleet name.** `pyproject.toml` declares `nextcloud-mcp` as the single `scion_sdk.connector` entry point. The content pack, the manifest `connector`, the fingerprints and the ingest binding all carry `nextcloud-mcp`. Caller chain: `nextcloud-mcp` in `pyproject.toml` runs `scion_sdk.cli:serve`, which builds the server from the `scion_sdk.connector` entry point `nextcloud_agent:connector` (`nextcloud_agent/__init__.py:6`); `connector_name("nextcloud_agent")` in the SDK resolves the same entry point name for the content pack, the manifest and the ingest binding. Shape: `pyproject.toml` entry point `nextcloud-mcp`, the `connector_name` helper of the SDK and the `ConnectorContent`/`IngestBinding` calls under `nextcloud_agent/`; reuses the SDK name resolution and adds no second constant. Proving test: `tests/test_fleet_name.py::test_connector_name_is_the_fleet_name`. | Every connector name in the package is `nextcloud-mcp`. | requirement | CONN-NEXTCLOUD-AGENT-CONNECTOR-IDENTITY | VERIFIED | 2deb2e74cd94 59f4a072361d tests/test_fleet_name.py:34 |
| CONN-NEXTCLOUD-AGENT CONN-NEXTCLOUD-AGENT — Nextcloud business operations | spec | None | VERIFIED | No recorded commit/test evidence |
| CONN-NEXTCLOUD-AGENT-R001 File operations run through the SDK WebDAV backend Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**File operations run through the SDK WebDAV backend.** The methods `list_files`, `read_file`, `write_file`, `create_folder`, `delete_item`, `move_item` and `copy_item` call the path methods of the SDK `WebDavBackend` (`SCION-CENTRALIZED-CAPABILITIES-R042.5`). The duplicate alias methods are gone: each operation has one method and one tool. `list_files` asks `propfind` for the Nextcloud properties `permissions`, `favorite` and `fileid`. It returns the same entry fields as before. `write_file` creates missing parent folders, and `overwrite` false keeps the conflict error. The connector deletes its own WebDAV request and listing parser code for these methods. Caller chain: the SDK per-operation tool `nextcloud_<method>` → the file method in `nextcloud_agent/api/api_client_files.py` → `WebDavBackend`. Shape: the client holds one `WebDavBackend` built from the files root URL. Depends on: `SCION-CENTRALIZED-CAPABILITIES-R042.5`. | `tests/test_files_webdav.py::test_file_methods_route_through_sdk_webdav_backend` . A mock transport receives every file request through the SDK client. A listing keeps the three Nextcloud fields. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 9004597c0b6b tests/test_files_webdav.py:99 |
| CONN-NEXTCLOUD-AGENT-R002 Build the WebDAV backend from the connector settings Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Build the WebDAV backend from the connector settings.** `get_client` in `nextcloud_agent/auth.py` reads `NEXTCLOUD_URL`, `NEXTCLOUD_USERNAME` and `NEXTCLOUD_PASSWORD` as today. The client builds `WebDavBackend` with the files root `<NEXTCLOUD_URL>/remote.php/dav/files/<username>` and the two credential values. The SDK egress guard then applies; `NEXTCLOUD_ALLOWED_PRIVATE_HOSTS` lists hosts that may resolve to private addresses. Its starting value is empty. Caller chain: `get_client` (nextcloud_agent/auth.py:11) → `NextcloudAPI` → `WebDavBackend`. Shape: one constructor change in the client base; no new setting beyond the private-host list. | `tests/test_files_webdav.py::test_backend_uses_files_root_and_private_host_setting` . The backend base URL ends with the files root. A private host refuses unless the setting lists it. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 10bfd2f0f0bd 765c9bd89cd8 9004597c0b6b tests/test_auth.py:80 tests/test_files_webdav.py:126 tests/test_files_webdav.py:148 |
| CONN-NEXTCLOUD-AGENT-R003 Pin the SDK release with the WebDAV backend Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Pin the SDK release with the WebDAV backend.** `pyproject.toml` pins the SDK release that carries `SCION-CENTRALIZED-CAPABILITIES-R042.5`, and `uv.lock` follows. Caller chain: the package install resolves the SDK pin. Shape: edit the dependency line and relock. | `tests/test_files_webdav.py::test_sdk_pin_carries_storage_backend` . `scion_sdk.storage.WebDavBackend` imports in the test environment. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 9004597c0b6b tests/test_files_webdav.py:141 |
| CONN-NEXTCLOUD-AGENT-R004 File versions, search and trash bin Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**File versions, search and trash bin.** `NextcloudFiles` in `nextcloud_agent/api/api_client_files.py` lists a file's versions newest first (`PROPFIND /remote.php/dav/versions/{user}/versions/{fileid}`), restores one (`MOVE` to `restore/target`), searches by name substring with an optional MIME prefix (`SEARCH /remote.php/dav`, scope the account root or a folder), lists the trash bin and restores one item. `write_file` takes `encoding="base64"` for binary content such as photos and videos. Caller chain: tool `nextcloud_list_versions` / `nextcloud_restore_version` / `nextcloud_search_files` / `nextcloud_list_trash` / `nextcloud_restore_trash_item` → `NextcloudFiles`. Shape: one method per DAV operation. | `tests/test_business_surface.py::test_versions_search_and_trash_use_the_dav_endpoints`: versions sort newest first, restore targets `restore/target`, the search body carries the name and MIME filters. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:84 |
| CONN-NEXTCLOUD-AGENT-R005 Internal shares and public links Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Internal shares and public links.** `NextcloudShares` in `nextcloud_agent/api/api_client_shares.py` lists shares (all, on one path, or shared with the account), reads, creates, updates and deletes one share over OCS `files_sharing`. `create_share` takes the share type by name (`user`, `group`, `public_link`, `email`, `talk`), requires `share_with` for internal types, takes password, expiry, label, note and public upload, and sends no email unless `send_mail`. Caller chain: tool `nextcloud_create_share` and siblings → `NextcloudShares.ocs_request`. Shape: one class `NextcloudShares` in `nextcloud_agent/api/api_client_shares.py`, reusing the base `ocs_request`. | `tests/test_business_surface.py::test_shares_cover_public_links_and_internal_grants`: a public link returns its URL, an internal share without `share_with` refuses, `sendMail` is false by default. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:126 |
| CONN-NEXTCLOUD-AGENT-R006 Calendar events with draft invitations Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Calendar events with draft invitations.** `NextcloudCalendar` in `nextcloud_agent/api/api_client_calendar.py` lists calendars with their component sets, creates and deletes a calendar (`MKCALENDAR`), lists events in a time range (`REPORT calendar-query`), reads, creates, updates (etag-guarded `If-Match`) and deletes one event. Attendees are marked `SCHEDULE-AGENT=CLIENT` unless `send_invitations` is true, so the server sends no invitation. Caller chain: tool `nextcloud_create_event` and siblings → `NextcloudCalendar`. Shape: methods on `NextcloudCalendar` in `nextcloud_agent/api/api_client_calendar.py`, built with `icalendar`, reusing the base `_dav_request` and `_dav_send`. | `tests/test_business_surface.py::test_event_invites_stay_drafts_unless_asked`: a new event is written with `If-None-Match: *`, attendees carry `SCHEDULE-AGENT=CLIENT`, and `send_invitations` removes it. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:141 |
| CONN-NEXTCLOUD-AGENT-R007 Tasks (VTODO) Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Tasks (VTODO).** `NextcloudCalendar` lists open or all tasks of a task-capable calendar, creates a task with due date and priority, and updates one (summary, due, description, percent, complete or reopen) guarded by its etag. `delete_calendar_object` deletes an event or a task. Caller chain: tool `nextcloud_create_task` / `nextcloud_update_task` / `nextcloud_list_tasks` → `NextcloudCalendar`. Shape: task methods on `NextcloudCalendar` reusing its `_query` and `_put` helpers. | `tests/test_business_surface.py::test_tasks_are_vtodos_and_complete_with_etag`: completing a task writes `STATUS:COMPLETED` with `If-Match`. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:166 |
| CONN-NEXTCLOUD-AGENT-R008 Contacts (vCard) Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Contacts (vCard).** `NextcloudContacts` in `nextcloud_agent/api/api_client_contacts.py` lists address books, lists contacts with parsed name, emails, phones and organization (`REPORT addressbook-query`), reads, creates, updates (etag-guarded) and deletes one contact; deletes refuse a URL outside the account's address books. Caller chain: tool `nextcloud_create_contact` and siblings → `NextcloudContacts`. Shape: one class `NextcloudContacts` in `nextcloud_agent/api/api_client_contacts.py`, built with `vobject`, reusing `_dav_request` and `_dav_send`. | `tests/test_business_surface.py::test_contacts_round_trip_as_vcards`: the created vCard carries the fields; a delete outside the address books refuses. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:185 |
| CONN-NEXTCLOUD-AGENT-R009 Talk conversations and chat Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Talk conversations and chat.** `NextcloudTalk` in `nextcloud_agent/api/api_client_talk.py` lists, reads, creates (private group, public or one-to-one), renames and deletes conversations; lists, adds and removes participants; reads chat history and posts and deletes messages over the spreed OCS API. Tokens are validated. Caller chain: tool `nextcloud_send_message` and siblings → `NextcloudTalk`. Shape: one class `NextcloudTalk` in `nextcloud_agent/api/api_client_talk.py`, reusing `ocs_request`. | `tests/test_business_surface.py::test_talk_conversations_and_messages`: a group conversation posts `roomType` 2, a message returns its id, an invalid token refuses. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:196 |
| CONN-NEXTCLOUD-AGENT-R010 Deck boards, stacks and cards Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Deck boards, stacks and cards.** `NextcloudDeck` in `nextcloud_agent/api/api_client_deck.py` lists, reads, creates and deletes boards; lists, creates and deletes stacks; creates, reads, updates, moves (the `reorder` route on the target stack), assigns and deletes cards. Caller chain: tool `nextcloud_move_card` and siblings → `NextcloudDeck._app_json`. Shape: one class `NextcloudDeck` in `nextcloud_agent/api/api_client_deck.py`, reusing the base `_app_json`. | `tests/test_business_surface.py::test_deck_move_uses_the_target_stack_route`: a move calls `/stacks/{target}/cards/{id}/reorder`. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:211 |
| CONN-NEXTCLOUD-AGENT-R011 Notes Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Notes.** `NextcloudNotes` in `nextcloud_agent/api/api_client_notes.py` lists (by category), reads, creates, updates and deletes notes over the Notes API. Caller chain: tool `nextcloud_create_note` and siblings → `NextcloudNotes._app_json`. Shape: one class `NextcloudNotes` in `nextcloud_agent/api/api_client_notes.py`, reusing `_app_json`. | `tests/test_business_surface.py::test_notes_crud_uses_the_notes_api`: create returns the note; an empty update refuses. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:218 |
| CONN-NEXTCLOUD-AGENT-R012 Activity and notifications Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Activity and notifications.** `NextcloudActivity` in `nextcloud_agent/api/api_client_activity.py` reads the activity stream (optionally for one object), lists notifications and dismisses one. A `304 Not Modified` activity answer reads as an empty list. Caller chain: tool `nextcloud_list_activities` and siblings → `NextcloudActivity`. Shape: one class `NextcloudActivity` in `nextcloud_agent/api/api_client_activity.py`, reusing `ocs_request`. | `tests/test_business_surface.py::test_activity_not_modified_reads_as_empty`. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:226 |
| CONN-NEXTCLOUD-AGENT-R013 User, group and app administration Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**User, group and app administration.** `NextcloudAdmin` in `nextcloud_agent/api/api_client_admin.py` reads the connected account; lists, reads, creates (password or email invite, groups, quota), updates one field of, disables, enables and deletes accounts; lists, creates and deletes groups, lists members, adds and removes members; lists installed apps by status, reads one, enables and disables one, over the provisioning API. Caller chain: tool `nextcloud_create_user` and siblings → `NextcloudAdmin`. Shape: one class `NextcloudAdmin` in `nextcloud_agent/api/api_client_admin.py`, reusing `ocs_request`. | `tests/test_business_surface.py::test_admin_creates_users_into_groups`: a user without password or email refuses; groups post as `groups[]`; an id with `/` refuses. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:239 |
| CONN-NEXTCLOUD-AGENT-R014 Office documents and collaborative editing Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**Office documents and collaborative editing.** `NextcloudOffice` in `nextcloud_agent/api/api_client_office.py` lists the creatable document types and templates (`apps/files/api/v1/templates`), creates a document from the extension or a template, and opens a one-time editor URL: Nextcloud Office (`richdocuments`) for office files, Text direct editing for markdown. The server needs the richdocuments app with a document server; the deployment declares it. Caller chain: tool `nextcloud_create_document` / `nextcloud_open_document` → `NextcloudOffice`. Shape: one class `NextcloudOffice` in `nextcloud_agent/api/api_client_office.py`, reusing `ocs_request` and `get_properties`. | `tests/test_business_surface.py::test_office_documents_open_in_the_matching_editor`: a `.docx` opens through richdocuments, a `.md` through Text. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:250 |
| CONN-NEXTCLOUD-AGENT-R015 One typed tool per operation Definition — CONN-NEXTCLOUD-AGENT / CONN-NEXTCLOUD-AGENT — Nextcloud business operationsCanonical requirement and verification source**One typed tool per operation.** The connector declares no action-routed tools: `nextcloud_agent/mcp_server.py` is gone and the SDK serves one `nextcloud_<method>` tool per public client method, typed from the signature, with destructive operations confirmation-gated. Caller chain: `Connector(api=NextcloudAPI)` in `nextcloud_agent/__init__.py` → SDK method tools. Shape: `nextcloud_agent/__init__.py` declares `Connector(api=NextcloudAPI, get_client=make_client)` with no `tools` module; the SDK method-tool builder is reused. | `tests/test_business_surface.py::test_every_operation_is_its_own_typed_tool`: the business tools are listed, none takes `action`, no duplicate alias remains. | requirement | CONN-NEXTCLOUD-AGENT | VERIFIED | 0c342adfc0fa tests/test_business_surface.py:58 |