> For the complete documentation index, see [llms.txt](https://newmishka.gitbook.io/newmishka-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newmishka.gitbook.io/newmishka-docs/razrabotka/istoriya-izmenenii.md).

# История изменений

## Unreleased

* Для неактивных SSSD и CUPS standard JSON дополнен полями `*_result`, `*_error_count` и `*_likely_cause`; причины обезличены и не содержат сырых строк журнала.
* Stage 4 базового отчёта: стандартная диагностика разделена на `collectors → normalized snapshot → checks/scoring → TXT/JSON`.
* Disk scoring, network status и пороговая классификация вынесены из collector в evaluator без изменения действующих порогов.
* Нормализованный снимок накопителей дополнен фактами, необходимыми для воспроизводимого scoring, включая NVMe spare/threshold.
* Архитектурный regression test запрещает scoring/checks внутри collector и проверяет сохранение disk/network semantics.

## 1.3.0

Основные изменения:

* корпоративная диагностика переведена на `collect → normalized inventory → probe → checks → output`;
* устранено дублирование `DNS / DOMAIN`;
* DC из Kerberos/LDAP/AD DC SRV выводятся по отдельности с TCP 88/389;
* CIFS, autofs, GVFS/FUSE и GIO объединены без дублей;
* добавлен явный `--probe-autofs`;
* mail-профиль проверяет DNS, TCP, TLS/STARTTLS, сертификаты и pre-auth capabilities;
* исправлена интерпретация CUPS journal;
* добавлены `--network-budget` и `--network-jobs`;
* сокращено число внешних процессов в TXT и NetworkManager-части;
* расширены performance/architecture regression tests.

Полная история изменений хранится в репозитории:

<https://github.com/NewMishka/arm\\_info/blob/main/CHANGELOG.md>

Release notes 1.3.0:

<https://github.com/NewMishka/arm\\_info/blob/main/docs/releases/v1.3.0.md>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://newmishka.gitbook.io/newmishka-docs/razrabotka/istoriya-izmenenii.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.