Skip to content

refactor(hooks): split hooks.py under the line cap by moving HookManager into an owner - #37859

Merged
bolichen97 merged 2 commits into
mainfrom
crew/linuxflackyguard/split-hooks-facade
Nov 16, 2026
Merged

bolichen97 merged 2 commits into
mainfrom
crew/linuxflackyguard/split-hooks-facade

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Bring src/kiro_crew/hooks.py back under the 2,000-line cap with a pure move, so the main ratchet audit stops failing on this file.

hooks.py is 2,011 lines on main, over the 2,000-line cap. The main ratchet audit has failed on every push since 11/13 (#36565), and every PR that touches hooks.py fails check_file_line_cap.py until the file is split.

Why it matters

Main stays red until both over-cap files are split, which hides real regressions behind a known red. Four open PRs edit hooks.py and cannot pass the line-cap check while it stays over the cap.

Not a goal

  • No behaviour change: no gate decision, signature, public name, logger name or __module__ of a function changes.
  • No change to src/kiro_crew/acp/kas_agents.py, the other over-cap file (split in its own PR).
  • No new owner responsibilities beyond the moved code, and no restructuring of HookManager itself.

What changed (motivation → approach → change)

hooks.py already composes its rules from hook_runtime/ owners through _facade_compose.compose, and almost everything left in it is module-level state, which must stay on the facade. The largest definition left was HookManager (about 400 lines). It stayed there only because its two gate entry points, judge and on_tool_call, are wrapped by _fail_closed_on_gate_crash when the class body runs, and compose does not reach a body held in a wrapper's closure.

  • New owner hook_runtime/hook_manager.py holds HookManager and _fail_closed_on_gate_crash, moved verbatim. Right after compose, hooks.py wraps judge and on_tool_call again around each body rebound onto the facade's globals, the same way it already rebinds ScriptHookStore._atomic_mutation. The decorator stays in the class body, so mypy still sees both entry points as Any, as on main.
  • _cu_read_only_auto_approve moves verbatim to hook_runtime/tool_identity.py, beside the other host-known read-only tests.
  • hooks.py re-exports all three names. It goes from 2,011 to 1,564 lines; hook_manager.py is 467 lines and tool_identity.py 1,092.
  • test/test_hooks_composition_contract.py: a _LATER_MOVES table records the three moved names, their owners and their shapes. _BASE_OWNERS and _BASE_SHAPE_DIGEST stay as they are, so open PRs that re-pin the digest do not conflict with this one. A new test pins the post-compose wrapping. The gate-consultation scan allows exactly the two calls HookManager makes to the gate itself (self.judge, tier.judge).
  • test/test_hooks.py: the extraction scan skips hook_runtime/hook_manager.py as it already skips hooks.py.
  • Specs: memory-skills-hooks.md (owner table, what stays and why, where new work goes), hook_runtime/__init__.py, and the citations in governance.md, acp-client.md and security-deep-dive.md now point at the new homes.

Backwards compatibility

Compatible: every name hooks.py bound on main still resolves on it, every patch through kiro_crew.hooks.<name> still reaches the moved code, and HookManager's members keep their __module__, __qualname__ and signatures. The one visible difference is HookManager.__module__, now kiro_crew.hook_runtime.hook_manager. That is the same rule every class in hook_types and script_hooks already follows, and nothing reads it (compose selects classes by it).

Removes nothing: every definition moves and stays importable from kiro_crew.hooks. No file, key, route or public function is removed.

Tests

Proof: not provable -- other: a pure move with no behaviour change, so there is no fix for prove.py to revert

  1. Names and identity (script, origin/main vs branch, separate interpreters): all 343 names hooks.py binds on main resolve on the branch, and none is missing. The one added name is _owner_hook_manager. Across the two interpreters, the only difference in (type, __module__, __qualname__) is HookManager.__module__. The 13 HookManager members are identical on both sides (type, __module__, __qualname__, signature, wrapped or not). In-process identity (hooks.X is <owner>.X) is pinned by test_every_moved_name_is_one_object_in_its_owner.
  2. Import paths: an AST scan of src/ and test/ (658 files) covers 215 names imported with from kiro_crew.hooks import ..., 17 "kiro_crew.hooks.<name>" patch strings and 104 <hooks alias>.<name> reads and writes. All of them resolve.
  3. Related backend tests: the related set run_scoped_tests.py --surface backend selects (2,971 files) is still running on a Linux DevSpace, on this branch and on clean main; the comparison will be added here. Locally, test/test_hooks*.py, test/test_gate_tiers.py and test/test_gate_crash_fail_closed.py pass (1,116 passed, 1 skipped).
  4. Line cap: scripts/check_file_line_cap.py (scoped) no longer names hooks.py. With RATCHET_SCOPE_WHOLE_TREE=1, the only failure left is acp/kas_agents.py (2,004 lines, sibling PR). hooks.py was never in .github/file-line-cap-baseline.txt.
  5. Gates: flake8, isort and mypy src/kiro_crew are clean (4,733 files). The black gate, test/test_flake_pattern_ratchet.py, test/test_facade_mirror_guards.py, test/test_facade_shared_checks.py, test/test_campaign_facades_base_public_names.py, test/test_file_line_cap.py, scripts/docs_lint.py, the comment-history gate and the brand gate all pass. semgrep scan --config semgrep/ --baseline-commit <merge-base> --error is clean (local semgrep 1.180.0, not the CI pin 1.78.0).

Updated test: test_the_gate_entry_points_are_wrapped_on_the_facade (new) pins that the wrapper and the one body it holds both run on the facade's globals. Without the post-compose wrapping, judge would read the owner's globals, and patches of hooks.GATE_TIERS and similar names would no longer reach it.

Manual verification

N/A — unit coverage sufficient: the composition contract tests pin placement, identity, globals and patch reach, and the related backend set ran on a Linux DevSpace against clean main.

Related Issues

Part of #36565

Open PRs that edit hooks.py, and what each meets after this split (git merge-tree against this branch):

PR hooks.py hunks After this split
#32830 the hook_runtime.hook_dispatch import list (stays in the facade) Clean merge
#32219 the hook_runtime.hook_dispatch import list (stays in the facade) Clean merge
#26416 HookManager._on_config_change flags and a new confirm_git_writes property Both hunks move to hook_runtime/hook_manager.py. The PR already conflicts with main in three test files
#12230 ScriptHook.from_dict (stays in the facade) Unchanged: the same one-line conflict it already has with main (main has _script_hook_enabled_from)

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 16, 2026 06:55
@bolichen97
bolichen97 requested a review from CrysisDeu November 16, 2026 06:55
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/hook_runtime/__init__.py

  • src/kiro_crew/hook_runtime/hook_manager.py

  • src/kiro_crew/hook_runtime/tool_identity.py

  • src/kiro_crew/hooks.py

  • @bolichen97 comment: does not name the current head 702b10e; post it again for this head

  • @KiroCrewCaptain: missing the ## Sensitive change review heading

How to clear this check:

  1. The PR author posts the template below as a PR comment, with
    every field filled (N/A needs a reason). Keep the
    Head commit line: it must name the current head SHA.
  2. The check turns green within a minute, with no push.
  3. A new push resets this check: post it again for the new head.

Only the author's comment counts this way. A reviewer can instead
paste the filled template into an "Approve" review on this head.
Merging still needs a reviewer's approval.

## Sensitive change review
- Head commit: 702b10e1a994d50af0f4df9d0481c35711e4354c
- What rule changed:
- Before -> after (what was allowed/blocked, now):
- Worst case if wrong (breaks commands / leaks secret / locks user out):
- Evidence checked (which sandbox result proves it):
- No regression:
  - Tools still work (which tools/commands were run, result):
  - Backward compatible (old config / old data / old callers still work, how checked):
  - Existing tests (which suites passed on this head):
- How to undo:

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 16, 2026
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 702b10e1a994d50af0f4df9d0481c35711e4354c touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 702b10e1a994d50af0f4df9d0481c35711e4354c — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: a pure move under the line cap; the re-wrap of judge/on_tool_call after compose keeps facade patches reaching both, and a new test pins it.

Notes

  • The description does not mention the PACKAGE_MODULE_CEILING bump in test_mcp_listing_import_budget.py (mcp-core 486→487). The code comment does explain it, so add one line to the description.

[DESIGN-REVIEWED] 702b10e

Description read

[DESCRIPTION-READ] 5d58bac1b35b14bd9d31dc56304cf89ec46200274bf09cf114428c28395ee3a2

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 702b10e1a994d50af0f4df9d0481c35711e4354c — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing blocks. AGENTS.md requires this split: no hand-written file may exceed 2,000 lines. The post-compose re-wrap uses the same _facade_rebind approach that already re-wraps ScriptHookStore._atomic_mutation.

What this change ships

Inventory (7 items) — 7 justified

Intent: get hooks.py back under the line cap so main's ratchet audit and the PRs that touch the file go green again. This is a FIX: a pure move that changes no behaviour.

  1. HookManager and _fail_closed_on_gate_crash move to hook_runtime/hook_manager.py and are re-exported from kiro_crew.hooks. — justified
  2. _cu_read_only_auto_approve moves to hook_runtime/tool_identity.py and is re-exported. — justified
  3. After compose, the facade wraps judge and on_tool_call again, so patches of kiro_crew.hooks.<name> still reach them. — justified
  4. HookManager.__module__ now reads kiro_crew.hook_runtime.hook_manager. — justified
  5. The composition contract gets a _LATER_MOVES table, a pin on the wrapping, and two allowed gate calls in its scan. — justified
  6. The mcp-core import-budget ceiling rises from 486 to 487 for the one new owner module. — undeclared
  7. Spec and docstring citations now point at the new homes. — justified

[FIRST-PRINCIPLES-REVIEWED] 702b10e

Description read

[DESCRIPTION-READ] db2f1573e50b5cdecf9b85742234563a4b6c211d4f7673b853a1ee1c742ad20c

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 702b10e1a994d50af0f4df9d0481c35711e4354c — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 702b10e

Verdict parsed from the review's SHA-scoped output markers for commit 702b10e1a994d50af0f4df9d0481c35711e4354c.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 702b10e1a994d50af0f4df9d0481c35711e4354c false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 702b10e1a994d50af0f4df9d0481c35711e4354c and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 702b10e

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 702b10e1a994d50af0f4df9d0481c35711e4354c false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Security Scope Review -- ✅ PASS

Which legitimate operations does 702b10e1a994d50af0f4df9d0481c35711e4354c newly refuse? Updated in place on each push. A script-confirmed regression blocks; the model proposes candidates and never decides a refusal.

Verdict basis: adjudicated, zero confirmed regressions.

Security scope review -- adjudicated candidates

  • macos-latest (platform posix): 10 classified, 0 newly refused, 10 still allowed.
  • ubuntu-latest (platform posix): 10 classified, 0 newly refused, 10 still allowed.
  • windows-latest (platform windows): 8 classified, 0 newly refused, 8 still allowed.

No candidate flipped from allowed to refused.

Scope-Verdict: PASS

Reason: This change tightens nothing. It moves HookManager and _fail_closed_on_gate_crash into hook_runtime/hook_manager.py and _cu_read_only_auto_approve into hook_runtime/tool_identity.py, with the moved bodies unchanged. It then wraps judge and on_tool_call a second time on the facade so they read the facade's globals, and no pattern, tier, argv floor or validator gets broader. I wrote 15 candidates for the gate's moved entry points as a check that this is a pure move. Nothing here confirms a regression; the harness supplies those verdicts after this review.

TIGHTENING: none. The only change on the gate path is a move: hooks.py now does for _gate_entry in ("judge", "on_tool_call"): _gate_body = _facade_rebind(vars(HookManager)[_gate_entry].__wrapped__, globals()); setattr(HookManager, _gate_entry, _fail_closed_on_gate_crash(_gate_body)). The body of judge still walks GATE_TIERS in the same order, and _cu_read_only_auto_approve is the same text. It names no threat and refuses nothing new.

ADJUDICATED: 15 candidates, 0 confirmed newly-refused

PLATFORM COVERAGE: posix, windows and any. The diff adds no new assumption about paths, separators, interpreters or the environment. Its only platform-relevant move is that every shell call now reaches judge through the facade's re-wrap.

  • posix rows: pytest through .venv/bin/python, grep, sed, a python3 -c check of where the wrapped body lives, and npm install -g for the claude adapter. Together they send a test run, a read-only search, a file read and an install through that re-wrap.
  • windows rows: the same operations in Windows spelling: .venv\Scripts\python.exe with \ separators, Select-String, Get-Content and npm.cmd. A tier body that now reads different globals would show up on the Windows tokenizer path too.
  • any rows: a scoped git diff --stat, black --check and flake8. These strings are neutral on both platforms.

No platform assumption is left without a candidate.

UNADJUDICATED: _cu_read_only_auto_approve moved into tool_identity. It is the computer-use observation auto-approve, a grant on the non-shell path that a tool call reaches through HookManager.judge, then GATE_TIERS, then the read-only classifier tier. Its inputs are computer-use tool titles, not shell command lines, so the classifier cannot give a verdict on them. The inputs I would have submitted are a screenshot or observe-class action title with the feature enabled, and the same title with the feature disabled. The function body is unchanged and it can only grant, so moving it cannot refuse anything new. The facade still binds CU_CLASS_OBSERVE, computer_use_action_classes and computer_use_action_from_title, and tool_identity now declares them under TYPE_CHECKING, so the rebound body reads the same objects.

[SCOPE-REVIEWED] 702b10e

@bolichen97

Copy link
Copy Markdown
Contributor Author

Sensitive change review

  • Head commit: b4e923c
  • What rule changed: none. This is a pure move: HookManager and _fail_closed_on_gate_crash move verbatim from src/kiro_crew/hooks.py to the new owner src/kiro_crew/hook_runtime/hook_manager.py, and _cu_read_only_auto_approve moves to hook_runtime/tool_identity.py. No tier, rule, pattern, path list or default is edited.
  • Before -> after (what was allowed/blocked, now): unchanged. HookManager.judge still walks the same GATE_TIERS table, in the same order, under the same fail-closed wrapper. After compose, the facade re-wraps judge and on_tool_call around bodies rebound onto kiro_crew.hooks's globals, so they read the same globals they read on main.
  • Worst case if wrong (breaks commands / leaks secret / locks user out): a moved body reads its owner's globals instead of the facade's. A test's patch of hooks.<name> would then stop reaching it, or a NameError in the gate would be refused as a gate crash (fail closed, so it locks calls out rather than letting them through). test_the_gate_entry_points_are_wrapped_on_the_facade and test_every_owner_function_runs_on_the_facade_globals pin against this.
  • Evidence checked (which sandbox result proves it): N/A -- the sandbox and every path list are untouched. The evidence is identity: a script compared origin/main with this head in separate interpreters, and all 343 names hooks.py binds resolve with the same type, __module__ and __qualname__ (except HookManager.__module__), and the 13 HookManager members are identical, signatures included.
  • No regression:
    • Tools still work (which tools/commands were run, result): test/test_hooks*.py, test/test_gate_tiers.py and test/test_gate_crash_fail_closed.py (1,116 passed, 1 skipped) drive the gate through judge and on_tool_call for shell, MCP, path and search calls.
    • Backward compatible (old config / old data / old callers still work, how checked): every from kiro_crew.hooks import ... (215 names), every "kiro_crew.hooks.<name>" patch string (17) and every <alias>.<name> read or write (104) in src/ and test/ still resolves (AST scan). The import path is unchanged.
    • Existing tests (which suites passed on this head): the above, plus test/test_hooks_composition_contract.py, test/test_facade_mirror_guards.py, test/test_flake_pattern_ratchet.py, test/test_file_line_cap.py and mypy src/kiro_crew (clean). The CI backend suites are running on this head.
  • How to undo: revert this one commit; nothing outside the moved code depends on the new owner.

@bolichen97
bolichen97 enabled auto-merge (squash) November 16, 2026 07:19
…ger into an owner

hooks.py had grown to 2,011 lines, over the 2,000-line cap, so the
main ratchet audit has been red on every push. Move HookManager and
its fail-closed decorator into a new hook_runtime/hook_manager.py
owner, and the computer-use observation test into tool_identity, so
hooks.py is 1,564 lines. Pure move: hooks.py stays the import path
and patch surface, compose runs the moved code on its globals, and
the facade wraps judge and on_tool_call again after compose so the
wrapped bodies read the facade's globals too.

Part of #36565
@bolichen97
bolichen97 force-pushed the crew/linuxflackyguard/split-hooks-facade branch from b4e923c to 42d1ac7 Compare November 16, 2026 07:43
@bolichen97

Copy link
Copy Markdown
Contributor Author

Backend Tests (3.12, 6): test_mcp_listing_import_budget.py::test_the_package_modules_loaded_before_the_list_stay_under_the_ceiling[mcp-core] counted 486 package modules against a ceiling of 485.

Fixed in 42d1ac7. The split adds one owner module (kiro_crew.hook_runtime.hook_manager) that the kiro_crew.hooks facade imports, so the mcp-core listing loads one more file and nothing else new. The ceiling goes from 485 to 486 with that reason written beside it, as the test's own comment asks.

self-added: yes
mechanism: one new owner module on the listing import path

@github-actions github-actions Bot added merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 16, 2026
@KiroCrewCaptain

KiroCrewCaptain commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: A person should decide

Why: the decider estimates a 7% chance that this change introduces a defect, within the 12% limit for approving on its own, but it changes 1117 lines, more than the 400 it may approve on its own.

This PR moves three definitions out of hooks.py with no edits: HookManager and _fail_closed_on_gate_crash go to hook_runtime/hook_manager.py, and _cu_read_only_auto_approve goes to hook_runtime/tool_identity.py. That brings hooks.py from 2,011 to 1,564 lines, under the 2,000-line cap. I compared the moved bodies against the removed lines and they match.

How patching keeps working. I checked the rebinding against _facade_compose.compose:

  • compose makes HookManager's methods and its _fail_closed_on_gate_crash decorator run on the facade's (hooks.py's) globals.
  • judge and on_tool_call are wrapped by that decorator, and the wrapper holds the original body in its closure. compose does not reach that body, so on its own it would still read the owner module's globals.
  • Right after compose, the new loop in hooks.py pulls each body out through __wrapped__, rebinds it onto the facade's globals and wraps it again. The decorator it wraps with is the facade's copy, so the new wrapper also runs on the facade's globals.
  • functools.wraps copies the body's __module__ and __qualname__, so the wrappers still report kiro_crew.hooks and `HookManager.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit 702b10e1a9 · 1117 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

…/split-hooks-facade

# Conflicts:
#	test/test_mcp_listing_import_budget.py
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 16, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This review checked head 702b10e against the merge-base. Removed hooks.py blocks (_fail_closed_on_gate_crash, HookManager, _cu_read_only_auto_approve) diff empty against hook_runtime/hook_manager.py and tool_identity.py, apart from imports, docstrings and TYPE_CHECKING lines. hooks.py is now 1,564 lines and is not in the line-cap baseline. The test edits re-pin values to their new true values and loosen nothing. The gate-consultation scan now pins an exact list (self.judge, tier.judge), which is tighter than main's whole-file exemption.

Security: the only new runtime code is the four-line re-wrap loop after compose (hooks.py:1499-1502). It copies the existing ScriptHookStore._atomic_mutation pattern. It rebinds each gate body onto the facade's globals and wraps it again with the facade's _fail_closed_on_gate_crash. The PlatformCompositionError re-raise and the fail-closed deny are unchanged. test_the_gate_entry_points_are_wrapped_on_the_facade pins the wrapper and body globals and checks there is no double wrap. Every CI lane keyed on the gate already covers hook_runtime/. No keystone, deny rule or fail-closed branch is weakened.

Done well: the PR handles the closure hazard (compose cannot reach a body held in a wrapper) with a minimal reused pattern and a test that goes red if any line of the loop is removed.

Optional:

  • Repost the Sensitive Change Review template naming head 702b10e1a994d50af0f4df9d0481c35711e4354c. The current one names b4e923cf, so that check stays red.
  • Add one line to the body about the PACKAGE_MODULE_CEILING["mcp-core"] re-pin (486 to 487).
  • Fix the Tests section. Post the branch-vs-main result for the related backend set, or point to CI Backend Tests instead. Note that acp/kas_agents.py is already under the cap via #37828, and add #34777 to the overlap table.

@bolichen97
bolichen97 merged commit 5cffe12 into main Nov 16, 2026
109 of 111 checks passed
@bolichen97
bolichen97 deleted the crew/linuxflackyguard/split-hooks-facade branch November 16, 2026 12:16
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants