Skip to content

ArchKeel 4.0.1 — Exact dependency rules and typed controls

Latest

Choose a tag to compare

@ake2l ake2l released this 18 Oct 00:32
· 926 commits to main since this release
006bc08

Declare narrower component APIs and check more native source evidence.

Highlights

  • Exact dependency intent. Opt-in contract 3.4.0 adds exact module
    selectors; 3.5.0 can forbid an import namespace even after its module has
    been removed. Contract 3.6.0 adds caller-scoped Python module-object grants without
    publishing named symbols. requires.through also checks exact module:Symbol
    ports. Unexpanded wildcard names remain UNKNOWN when an exact symbol is required.
  • Substantive responsibilities. Architect-attributed components containing
    only TODO, TBD or placeholder markers now receive
    responsibility.missing. Validation exits 2; agent drafts remain accepted.
    Non-placeholder prose still does not prove that a responsibility is correct.
  • More precise native controls. Python observes supported literal equality,
    membership, match, stable imported constants and guarded Enum values at their
    actual lexical owners, preserving physical source lines. TypeScript/JavaScript
    observes written string comparisons and switch cases as PARTIAL evidence:
    witnessed violations can FAIL, while an empty inventory cannot prove PASS.
    Dart local callables retain lexical precedence over imported names.
  • Shared control types. Covered Core, collector and browser boundaries use
    owned nominal vocabularies, checked ingress and native regression guards.
    This is a bounded migration; remaining string-control work in
    #542 stays open.
  • Less repeated collector work. Python member-escape propagation indexes
    dotted prefixes once per convergence pass and preserves live binding updates.
    This removes repeated per-import scans; it does not guarantee a runtime budget
    on every project or runner.
  • Report and review corrections. Published browser assets include the current
    runtime. Module views reuse the report graph already derived by their caller.
    Direct UML scopes use more edge spacing. Repeated-logic review
    candidates can distinguish complete, resolved call sequences; ambiguous
    evidence retains the candidate and proves no runtime equivalence.

Release verification

The 4.0.0 tag did not reach PyPI: the full gate caught a Windows checkout failure
before the collector-safety tests ran. Fetching all branch refs tried to create
an aux/... path; Windows reserves the name AUX. Those jobs now fetch only the requested
ref. Both Python versions, collector-safety tests and the publication gate remain
required. Native TypeScript mutation fixtures also read and write UTF-8 explicitly
instead of depending on the Windows locale. Flow source and runtime assets retain
LF line endings so packaged source checksums remain valid on Windows.
The public 4.0.0 tag is retained.

Upgrade from 3.0.1

uv tool upgrade archkeel

Upgrade strict readers and collectors together. New TypeScript observations
can include a constructs section that the 3.0.1 report reader rejects. This is
an incompatible profile expansion and requires the new package major. SourceFacts
and protocol remain 3.0.0, ArchitectureIR/Delta 2.0.0, and command-result
8.0.0; unchanged version numbers do not make the new profile readable by an
older Core. Existing legacy TypeScript receipts remain supported by this release.

CLI options, configuration and documented archkeel.api exports retain their
interfaces. Existing contract versions remain supported; older releases reject
the new opt-in contract fields. Analyzer corrections can change findings and
identities: re-observe both revisions with the same package before comparing
snapshots. Saved reports retain their original evidence.

Static evidence still does not establish compiler parity, runtime correctness or
complete language coverage. See known limits,
dependency rules and the compatibility policy.

All changes since 3.0.1

Plugin asset correction

The plugin ZIP was corrected on 2026-10-19. Its original backfill incorrectly reused the 3.0.1 archive because both plugin manifests in the 4.0.1 tag still declared 3.0.1. The replacement uses the 4.0.1 tag content and changes only the two manifest version fields to 4.0.1; the skill and other payloads are unchanged. The Git tag and Python release are unchanged. Download the corrected ZIP and verify SHA256SUMS.