chore: bound the registered kit instead of pinning it by git

[seabbs-bot]

The premise has lapsed

test/jet/Project.toml pinned EpiAwarePackageTools by git [sources]
on the premise that the kit was unregistered.
It is registered in General, and 0.4.1 is the current release.

A git pin costs three things.
It resolves an unreleased main, so the environment moves under CI
without a version bump.
It needs Julia 1.11, where [sources] is honoured — on 1.10 Pkg ignores
the entry silently and resolves the registry instead.
And a package carrying a git [sources] entry cannot be registered
itself.

Change

The kit comes from the registry, bounded as
EpiAwarePackageTools = "0.3, 0.4" under [compat].
That is the bound EpiAwarePackageTools.scaffold itself templates
(KIT_COMPAT), so a resync leaves no drift.

Comments are gone from the file, per org policy.
Pkg silently drops any comment in a Project.toml the next time it
rewrites the file, so the kit's update now warns about them.
The JET = "0.9.19, 0.11" bound is unchanged, and the reasoning behind
it is recorded here so it is not lost with the comment.
JET's 0.x minors are breaking bumps under Julia's semver, so a new minor
must not silently tighten static analysis and turn the managed check red
without a deliberate bump.
The 0.9.19 alternative sits alongside 0.11 because JET dropped Julia
1.11 support at 0.10.0 (upstream requires 1.12+ from 0.10.2 on) and this
subprocess runs under whatever Julia the outer CI leg uses.
0.9.19 is the last 0.9.x release, so it is the floor that still supports
Julia 1.11.

Verification

julia --project=test/jet -e 'using Pkg; Pkg.instantiate()' resolves
EpiAwarePackageTools v0.4.1 and JET v0.11.6 from the registry.

Every kit binding this repo calls — run_package_tests,
DocsBuild.build_docs, the QA and AD helpers — is present in 0.4.1.
src/ is byte-identical between the v0.4.1 tag and the kit's current
main for every file those bindings live in, so nothing is lost by
taking the release.

Follow-up

This was the repo's last git [sources] entry.
The root [compat] julia = "1.11" floor existed to make the pin
honoured.
Kit 0.4.x supports Julia 1.10, so the floor can now drop and the
tests.yml matrix can take its lts leg back.
That is a user-facing support change and needs its own PR.

This was opened by a bot. Please ping @seabbs for any questions.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
ad-enzyme-forward	18.21% <ø> (ø)
ad-enzyme-reverse	18.21% <ø> (ø)
ad-forwarddiff	14.86% <ø> (ø)
ad-mooncake-forward	14.86% <ø> (ø)
ad-mooncake-reverse	14.86% <ø> (ø)
ad-reversediff	14.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Try this Pull Request!

Option 1: Julia Package Manager

Open Julia and type:

import Pkg
Pkg.activate(temp=true)
Pkg.add(url="https://github.com/EpiAware/DistributionsInference.jl", rev="chore/drop-kit-git-pin")
using DistributionsInference

Option 2: Local Checkout

If you have the repo locally:

git checkout chore/drop-kit-git-pin
julia --project=. -e "using Pkg; Pkg.instantiate()"

[github-actions]

📖 Documentation preview is ready!

View the docs for this PR at: https://EpiAware.github.io/DistributionsInference.jl/previews/PR146/

This preview will be updated automatically when you push new commits.