WIP: Describe dynamic-link service contracts consistently #11

Draft
erikinkinen wants to merge 5 commits from feature/dynamic-link-component-contracts into feature/registry-bound-tls-plans
Owner

Use the component documentation layout for dynamic-link inputs, ownership and remaining adoption work. Keep source-selection text aligned with main-tracking manifests and retain the actual evidence limits without obsolete process notes.

Depends on #10 (feature/registry-bound-tls-plans).

  • Keep this feature and its contract separate from the preceding changes.
  • Link matching protocol and consumer PRs.
  • Complete integrated native acceptance and regression coverage.

This branch also includes the completed downstream features from #12.

Use the component documentation layout for dynamic-link inputs, ownership and remaining adoption work. Keep source-selection text aligned with main-tracking manifests and retain the actual evidence limits without obsolete process notes. Depends on #10 (`feature/registry-bound-tls-plans`). - [x] Keep this feature and its contract separate from the preceding changes. - [ ] Link matching protocol and consumer PRs. - [ ] Complete integrated native acceptance and regression coverage. This branch also includes the completed downstream features from #12.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 15:25:36 +01:00
docs: Describe dynamic-link service contracts consistently
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 4s
CI / test (push) Failing after 39s
bb7bda7815
Use the component documentation layout for dynamic-link inputs, ownership and
remaining adoption work. Keep source-selection text aligned with main-tracking
manifests and retain the actual evidence limits without obsolete process notes.
ci: retain the public source graph on this feature branch
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 7s
CI / test (push) Successful in 2m40s
62e88451ce
Select the existing public providers without changing the feature source or its test matrix.
ci: Use shared development dependency profiles
Some checks failed
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 10s
CI / test (push) Failing after 31s
cf844bea8d
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: Select the provider policy explicitly
All checks were successful
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 1m7s
65441d1b79
Adopt the shared main/release and feature source contract. Actual CI reference metadata selects main providers for main and release builds, while feature builds retain their explicitly declared companions.
feat: Merge use shared development dependency selection
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 1m2s
332c68d9fa
Integrate the reviewed prepared history into feature/dynamic-link-component-contracts. The feature tree and
original source branch remain unchanged. Upstream work retains its own
completion requirements.

#12
Author
Owner

Merged the approved downstream work from #12. The upstream PR retains its own remaining scope and completion requirements.

Merged the approved downstream work from #12. The upstream PR retains its own remaining scope and completion requirements.
All checks were successful
CI / test (pull_request) Has been skipped
CI / markdown (pull_request) Has been skipped
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 1m2s
This pull request has changes conflicting with the target branch.
  • .github/workflows/ci.yml
  • ARCHITECTURE.md
  • README.md
  • ROADMAP.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'feature/dynamic-link-component-contracts:feature/dynamic-link-component-contracts'
git switch 'feature/dynamic-link-component-contracts'

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/registry-bound-tls-plans'
git merge --no-ff 'feature/dynamic-link-component-contracts'
git switch 'feature/dynamic-link-component-contracts'
git rebase 'feature/registry-bound-tls-plans'
git switch 'feature/registry-bound-tls-plans'
git merge --ff-only 'feature/dynamic-link-component-contracts'
git switch 'feature/dynamic-link-component-contracts'
git rebase 'feature/registry-bound-tls-plans'
git switch 'feature/registry-bound-tls-plans'
git merge --no-ff 'feature/dynamic-link-component-contracts'
git switch 'feature/registry-bound-tls-plans'
git merge --squash 'feature/dynamic-link-component-contracts'
git switch 'feature/registry-bound-tls-plans'
git merge --ff-only 'feature/dynamic-link-component-contracts'
git switch 'feature/registry-bound-tls-plans'
git merge 'feature/dynamic-link-component-contracts'
git push origin 'feature/registry-bound-tls-plans'
Sign in to join this conversation.
No description provided.