umputun / agterm / 32446670576
94%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 95
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 97.997%. Remained the same
32446670576

push

github

umputun 
fix(hooks): narrow the baked-block API and correct its strip comment

follow-up to #473, all maintainer cleanup. `agtermctlMarker` was public with no consumer outside
agtermCore, since both test suites reach it through `@testable`, and that re-opened surface
d54b50f5 had just closed in this same file. Internal now.

`stripBakedBlock`'s comment claimed that deriving the skip count from the emitted block meant
growing that block could not leave half the old one behind. It is the other way round: the count
measures what is being WRITTEN and is applied to what a previous install wrote, so any length
change mis-strips, over-eating the script when the new block is longer. Nothing reaches it because
`copyBundledFolder` re-copies the pristine wrapper before every bake, which is what the comment
now says instead.

The rest is trimming. #473's doc comment ran eight lines over a two-line body and repeated the
moved-bundle rationale on four surfaces; the wrapper's own header owns it, so the Swift side points
there and the restatement in `AgentHooksInstaller` is gone. Three test comments come back to one
line, keeping the `#472` reason a regression test is entitled to.

The agent-skill troubleshooting entry for a stuck glyph named neither the moved-bundle cause nor
either recovery, so an installed agent had nothing to tell a user whose baked path went dead.

8121 of 8287 relevant lines covered (98.0%)

4923994.25 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32446670576.1 95
98.0
GitHub Action Run
Source Files on build 32446670576