Proof Portal
Omarchy
ProbeLabsviewing a historical runA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
When entered password text exceeds the field width, the lock view shall scale the password dots so the row stays inside the field.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When entered password text exceeds the field width, the lock view shall scale the password dots so the row stays inside the field. The lock view shall report the edited text to the service without an edit-feedback loop.
when password_text_overflows the lock_view shall always satisfy dots_scaled_within_field
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
An unbounded dot row lets a long password overflow the field and leak its length beyond the field edge.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- in_review
- Reviewer
- Kimi Dogfood · AI agent
- Reviewed
- Sep 12, 2026, 23:50 UTC
History
- Created
- Sep 12, 2026, 19:43 UTC · Kimi Dogfood · AI agent
- Modified
- Sep 12, 2026, 23:32 UTC · Kimi Dogfood · AI agent
Hazard review
- scenarioreviewedboundary
Worst case: an unbounded dot row overflows the field and leaks the password length beyond the field edge. boundary: the overflow threshold where measured advance exceeds usable width is the scaling trigger, and Math.min(1, ...) caps the scale at full size for short passwords. Catalog 1.11.0 re-review: input_domain not applicable, the password text is held, not parsed. concurrency_scale not applicable, view state recomputed from the current rows on each UI event: no process, timer or lock, and events are handled one at a time.
- propertyreviewedtotalityidempotency
totality: every text length yields a defined scale, with the advanceWidth>0 guard covering the pre-measure zero case. idempotency: the equality guard plus the syncingPasswordText latch break the onTextChanged to passwordTextEdited to sync feedback loop, so repeated edits converge with no re-entry.
- structuralreviewedoverflow_safety
The shrink ratio can go negative when the measured advance exceeds the usable width by enough; Math.max(1, Math.floor(...)) on the derived pixel size clamps that underflow so the field never requests a non-positive font.
- domainnot applicable
Pure view-layer layout arithmetic; no external call, trust boundary, or auth surface.
Change history
Every recorded revision of this requirement's source file — newest first, each with its commit message and the diff for that change.
Review history
Human and AI-agent approvals of this requirement — the 'why was this approved' lineage, each with the reviewer's justification and the code it cites.
- Kimi Dogfood · AI agentApprovedSpec conformanceSep 12, 2026 · 3 weeks agoREVIEW-4
Password-dot scaling branch matches the formula: when text width exceeds the field, dot scale shrinks so the row stays inside; the edited text is reported to the service untruncated. Trigger password_text_overflows is the width comparison in the view.
Cited code (1)
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
The tests that discharge each obligation aren't available for a historical run
The evidence matrix behind each obligation comes from the live audit index, which can't be rebuilt for a past commit. Nothing here means unknown — not that the requirement has no obligations.
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
when password_text_overflows the lock_view shall always satisfy dots_scaled_within_field
Witnesses· 2 scenarios total
- lock-password-overflow-test.sh:1exercises 2 condition scenarios
MC/DC truth table· 3 rows
Each row assigns the formula's conditions (T/F) and shows the Result— the formula's value for that input row, not a test pass/fail. A row proves a condition when flipping only that condition flips the outcome. The test that covers each row is linked.
mcdc:ignoreNo-actionfalse-result row satisfied by designUncoveredneeds a covering test| # | dots_scaled_within_field | password_text_overflows | Result | Proves | Covering test |
|---|---|---|---|---|---|
| 1 | F | F | T | password_text_overflows | |
| 2 | F | T | F | dots_scaled_within_field | — |
| 3 | T | T | T | dots_scaled_within_field |
Its place
How this requirement connects — what proves it, what it affects, and what it rests on. Authored links only here; automatically derived links come from the audit index.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
No findings affect this requirement
Nothing was flagged against this requirement in the pinned run.
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
Impact
Blast radius — authored trace links only (automatically derived links come from the audit index and aren't shown here).
If you change this
Files to re-check (1)
- LockView.qmlshell/plugins/lock/LockView.qml
Tests to re-run (1)
- lock-password-overflow-test.shtest/shell.d/lock-password-overflow-test.sh
What this rests on
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.