fix: preserve wrapped method metadata in require_authentication

[Olen]

The bug

You're right — the function-level docstrings on https://olen.github.io/Spond/spond/spond.html are wrong, but the cause isn't in the docstrings themselves. The `require_authentication` decorator was missing `@functools.wraps(func)`, so every method it decorated lost its metadata:

```python

before

@staticmethod
def require_authentication(func: Callable):
async def wrapper(self, *args, **kwargs):
...
return wrapper
```

Without `functools.wraps`, `Spond.get_profile` was internally just a copy of `wrapper`. `inspect.signature` saw `(self, *args, **kwargs)`. `inspect.getdoc` saw nothing (or the wrapper's docstring leaked through, depending on Python's exact resolution). pdoc reads both, so every decorated method on the live site rendered as:

```
async def get_profile(self, *args, **kwargs):
# source: the wrapper's body, not get_profile's
```

instead of:

```
async def get_profile(self) -> JSONDict:
"""Retrieve the authenticated user's profile.

The profile dict includes at least the user's \`id\`, \`firstName\`, and
\`lastName\`...
"""

```

All my docstring work from #237 / #241 landed in source but pdoc never saw it for decorated methods.

The fix

Two lines: `import functools` + `@functools.wraps(func)` on the inner wrapper. After this fix, decorated methods expose their real signatures and docstrings:

```
get_profile(self) -> 'JSONDict'
→ Retrieve the authenticated user's profile.
get_posts(self, group_id: 'str | None' = None, max_posts: 'int' = 20, ...
→ Retrieve posts from group walls.
get_events(self, group_id: 'str | None' = None, subgroup_id: 'str | None' = None, ...
→ Retrieve events visible to the authenticated user.
```

Regression tests

New `TestRequireAuthenticationDecorator` class with three tests that each fail if `functools.wraps` is removed:

• `test_decorator_preserves_signature` — `get_posts` exposes its real parameter list, not `*args, **kwargs`.
• `test_decorator_preserves_docstring` — `get_profile` exposes its real docstring, not the wrapper's.
• `test_decorator_preserves_name` — `get_events.name` is `"get_events"`, not `"wrapper"`.

Why this only surfaced now

Before #241 expanded the docstrings, all decorated methods had thin one-line docstrings. The wrapper's "leaked" appearance was less obvious because the user-facing docs were already terse. After #241 dropped substantial docstrings on each method, the bug became loud: I had carefully written content for, say, `get_events`, and pdoc kept showing a generic `(self, *args, **kwargs)` shim instead.

Test plan

• Local `pytest` — 30 tests pass (27 inherited from fix: correct send_message and update_event return contracts (closes #238, closes #239) #243 + 3 new wraps regression tests)
• Local `ruff check` — clean
• Local `ruff format --check` — clean
• Local `pdoc -o /tmp ./spond` — decorated methods now render with real signatures and docstrings
• CI: 4-version matrix green
• Post-merge: GitHub Pages rebuilds; visit https://olen.github.io/Spond/spond/spond.html and confirm the function-level docs render correctly

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds @functools.wraps(func) to the require_authentication decorator so wrapped async methods retain their original signature, name, and docstring. This restores correct rendering on the pdoc-generated GitHub Pages site and improves IDE/inspect introspection.

Changes:

• Import functools and apply @functools.wraps(func) to the inner wrapper in require_authentication.
• Add a new TestRequireAuthenticationDecorator test class covering signature, docstring, and __name__ preservation.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
spond/base.py	Add functools import and @functools.wraps(func) on the require_authentication wrapper.
tests/test_spond.py	Add three regression tests asserting the decorator preserves signature, docstring, and name.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.