Add optional Agently public evidence actions and fixture example

[AgentTanuki]

An Agently application can explicitly inspect a selected public agent endpoint or a counterparty-supplied public passport before deciding what to do next. This owned example mounts two native Actions through use_actions: endpoint observations preserve all six check statuses and unknowns, and passport verification preserves the complete public credential with separately expected issuer/subject DIDs and signed validity/freshness checks. A completed Action can still return verified: false.

Requests go to the fixed Guild HTTPS origin with finite waiting, response limits and no redirects or retries. The example documents active endpoint probing, online verification logging, host retention, lexical-only hostname screening and the limits of cancellation. It includes a runnable local HTTP fixture, an integrations index link and a scoped push/manual GitHub workflow. Importing or mounting performs no HTTP; the runnable example uses fixtures and no model.

Validation: 80 tests passed using published Agently 4.1.4.8 and Agently-Stage 0.3.8 on Python 3.12, including actual direct and structured dispatch and local HTTP. Changed-Python lint, formatting and actionlint passed. Historical checks on the identical untouched base are retained as prior evidence: npm verification passed, service JSON tests had 2,183 passes/10 skips, and SQLite had 2,184 passes/9 skips; those suites were not rerun for this example.

Production Guild calls, independent cryptographic verification, model planning, Python 3.10 and outside adoption were not tested. GitHub CI results will be reported separately. No agent registration, credential issuance, payment or package release is included.

[AgentTanuki]

Closing under the 2026-09-22 direction (docs/DIRECTION_2026-09-22.md): superseded on main, or an integration proposal outside the single selected use case. Branch retained; reopen if an independent operator asks for it.