WIP: Relay permission evidence on original metadata endpoints #47

Draft
erikinkinen wants to merge 3 commits from feature/vfs-permission-evidence into feature/owned-exact-deliveries-through-provider-retirement
Owner

Relay permission snapshots and ACL pages only through original job-lifetime READ_METADATA directory endpoints. Retain the provider route and fresh private correlation; validate object, kind, revision and page range. Rewrite only public response correlation and clear refused staging. Owned result custody prevents refetch after completion refusal.

Refs #5. Depends on #46, erix/lib-ipc#62 and erix/integration#786.

  • Implement the original permission-evidence relay.
  • Cover authority, correlation, refused staging and owned completion behavior.
  • Complete formatting and component checks with the matching public suppliers.
Relay permission snapshots and ACL pages only through original job-lifetime READ_METADATA directory endpoints. Retain the provider route and fresh private correlation; validate object, kind, revision and page range. Rewrite only public response correlation and clear refused staging. Owned result custody prevents refetch after completion refusal. Refs #5. Depends on #46, erix/lib-ipc#62 and erix/integration#786. - [x] Implement the original permission-evidence relay. - [x] Cover authority, correlation, refused staging and owned completion behavior. - [x] Complete formatting and component checks with the matching public suppliers.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 16:27:22 +01:00
feat: Relay permission evidence on original metadata endpoints
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 8s
CI / test (push) Failing after 1m47s
d25b26083e
Admit only original job-lifetime directory metadata records before forwarding permission snapshots or ACL pages through their retained provider route. Check fresh private correlation, object, kind, revision and page range. Rewrite only the response prefix to VFS object correlation; clear refused staging and preserve owned result custody without refetching after completion refusal.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / test (push) Has been cancelled
CI / markdown (push) Has been cancelled
b14010b66c
Keep authored manifests on main and select coordinated providers through Integration. Resolve branches once per run, retain the frozen snapshot and helper identity as artifacts, and use shared source checks instead of copied tests and guides.
ci: Declare policy helper and output boundaries
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 1m35s
322c83b9f8
Select a disjoint operation parent for policy evidence and explicitly identify the helper checkout excluded from original component input. Keep the complete dependency policy and existing acceptance commands.
Author
Owner

Prepared b5923865bda1a8b6c800efe0390b642856f0b886 on feature/vfs-permission-evidence-merge-ready-b5923865 follows the single-feature #46 history and uses the matching companion profile from erix/integration#786. Original source and earlier proof histories remain available. Review should use this commit.

Prepared `b5923865bda1a8b6c800efe0390b642856f0b886` on `feature/vfs-permission-evidence-merge-ready-b5923865` follows the single-feature #46 history and uses the matching companion profile from erix/integration#786. Original source and earlier proof histories remain available. Review should use this commit.
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 6s
CI / test (push) Failing after 1m35s
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/vfs-permission-evidence:feature/vfs-permission-evidence'
git switch 'feature/vfs-permission-evidence'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge --no-ff 'feature/vfs-permission-evidence'
git switch 'feature/vfs-permission-evidence'
git rebase 'feature/owned-exact-deliveries-through-provider-retirement'
git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge --ff-only 'feature/vfs-permission-evidence'
git switch 'feature/vfs-permission-evidence'
git rebase 'feature/owned-exact-deliveries-through-provider-retirement'
git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge --no-ff 'feature/vfs-permission-evidence'
git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge --squash 'feature/vfs-permission-evidence'
git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge --ff-only 'feature/vfs-permission-evidence'
git switch 'feature/owned-exact-deliveries-through-provider-retirement'
git merge 'feature/vfs-permission-evidence'
git push origin 'feature/owned-exact-deliveries-through-provider-retirement'
Sign in to join this conversation.
No description provided.