vssa-v1-skills-code-agent/vssa-clients
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add CVP IS procurement detail routes
Validate skill / validate (push) Failing after 9s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-19 08:02:16 +00:00
parent 9de0e702f4
commit ebc9f1641f
2 changed files with 17 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+1 -1
View File
@@ -140,7 +140,7 @@ A tender notice proves intended procurement, not necessarily award or delivery.
For the VSSA continuous-research workflow, `https://viesiejipirkimai.lt/epps/viewCFTSAction.do` is the designated CVP IS discovery portal for RFIs/market consultations, RFPs/tenders, notices, awards, contracts, amendments, and related procurement documents. Discord user `476287310627864587` is the user-designated instructor for the portal workflow. Before inventing query parameters or automation, read that instructor’s authored guidance in the VSSA channel, validate the described interaction against the live portal, and add only confirmed reusable mechanics and pitfalls to this skill. Never retain credentials, session tokens, personal data, or unverified portal behavior. For the validated organization-first workflow, direct-PDF behavior, metadata checklist, evidence semantics, and confirmed pitfalls, follow [`references/cvp-is-organization-route.md`](references/cvp-is-organization-route.md).
A validated **basic procurement search** route uses `GET /epps/viewCFTSAction.do` with `mode=search`, `isFTS=true`, `type=cftFTS`, `isPopup=false`, and `contractAuthority=<URL-encoded client name>`, plus the browser form's remaining empty/filter fields. Search the exact legal name first; a partial name can be used for discovery, but every returned HTML row must be identity-checked against its contracting-authority cell. Parse complete rows and all pages, then open the procurement body or attachment before making any claim. The result table itself is discovery metadata only. For the exact parameter shape, row fields, pagination, and validated example, follow [`references/cvp-is-organization-route.md`](references/cvp-is-organization-route.md).
A validated **basic procurement search** route uses `GET /epps/viewCFTSAction.do` with `mode=search`, `isFTS=true`, `type=cftFTS`, `isPopup=false`, and `contractAuthority=<URL-encoded client name>`, plus the browser form's remaining empty/filter fields. Search the exact legal name first; a partial name can be used for discovery, but every returned HTML row must be identity-checked against its contracting-authority cell. Parse complete rows and all pages. For each retained **Pirkimo ID** (`resourceId`), open `prepareViewCfTWS.do` for detailed order metadata, `viewContractNotices.do` for all notices and summary-PDF links, and `listContractDocuments.do` for procurement attachments. Some anonymous attachment actions expose their `documentId` only in JavaScript handlers, so parse the action rather than treating `href="#"` as a missing file. Open and classify the procurement body or attachment before making any claim; all result/detail tables remain discovery metadata. For the exact parameter and route shapes, row fields, attachment behavior, pagination, and validated examples, follow [`references/cvp-is-organization-route.md`](references/cvp-is-organization-route.md).
A second validated discovery route is **organization first**: